|
Creating Team Norms In their eagerness to embark on a new project, project teams sometimes overlook an essential aspect of their effort—building a relationship among team members, which will foster not just a successful project outcome, but also a satisfying work experience. Investing in relationship building is invariably less costly and time-consuming than recovering from the divisiveness and conflict that may result from its absence. And that's where team norms come in.
|
|
|
The Tyranny of the "To Do" List We create lists to help us prioritize tasks and stay on schedule. Sometimes those lists help us accomplish those tasks faster. Sometimes those lists simply chain us to an archaic way of doing things. Having a "To Do" list is a good thing if you don't let it prevent you from thinking outside the box. In this column, Elisabeth explains why the agenda items that don't make the list can often be some of the most important.
|
|
|
Get the Picture? Peter TerMaat tells the story of a failing project and a chart that influenced a $2 million decision.
|
|
|
The Product Champion: Making Sure that Customer, Team, and Business Needs Are Well Represented in the Development Process Having a close relationship with the customer is always a good idea. But with that relationship comes risks. Most projects could use a knight in shining armor to protect their product's future. Discover how a product champion can help your organization stay focused on the customer without losing sight of the big picture.
|
|
|
When Should You Start Project Overtime? Many managers believe that overtime, even extended overtime is a good thing, and will help a project make progress. However, most technical people who try to work more than two weeks of overtime make huge numbers of mistakes. Often, they don't realize the mistakes and have already wasted a lot of time and money.
|
|
|
Project Management Planning – Checklist, Template, Guidelines (Template) This checklist is a recommended guideline for the content of project management planing documentation
A project management planing document is applicable to any and all phases of a system / product life cycle. The PMP may be applied to any type of computer system, software application development, or computer related project, regardless of the scope, size, complexity, or criticality. The PMP is applicable to all forms of computer system product delivery media, including client/server, web-based, firmware, embedded systems code, programmable logic arrays, and software-in-silicon.
|
|
|
Give 'em the Business Miscommunication is at the heart of most software defects. Being knowledgeable about a company as a whole, and not just about the specs of a particular project, is just one more way to safeguard against failures. Read on as Elisabeth Hendrickson explains the importance of technical people staying informed about business strategies.
|
|
|
Show and Tell It's critical that you discover the defects before your customers do. Metrics give you plenty of data, but creating charts and graphs that properly showcase this data can be difficult. In this article, read about six techniques that can help make this task a lot easier.
|
|
|
The Fine Art of Scheduling Why is scheduling an art? If it were a science, every project would be delivered on time. Overruns have become so common that people have lost faith in schedules and view them as very malleable. In this article, Nick Jenkins explains how to prevent this in your project.
|
|
|
Ten Ways to Guarantee Project Failure Naomi Karten specializes in helping companies succeed in their projects. In this column, however, she gives tongue-in-cheek advice on how to make a project fail. Read on to see if these steps to failure are part of your organization's modus operandi.
|
|