You're Slipping | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Executive Report > Features
Your software project is not going to meet schedule. Maybe requirements have taken longer; perhaps in the middle of implementation, the team uncovered something requiring redesign; maybe developers haven’t met one milestone yet and you’re worried about the test time. What do you do?
When software projects begin slipping, they’re talking to you, the project leader. The first slip is a whisper: “Your expectation is not matching my reality. Listen. I can tell you my reality.” If you ignore the first slip, the second slip is a murmur: “Things aren’t quite right. Don’t you want to know what’s going on?” By the third slip, the project says: “Knock-knock. Are you there? Don’t you want to know what’s going on?” At the fourth slip, the project yells: “Hey, you! You didn’t listen when you could act. Now you’ll have to pay.”
Early Project Slips
The first slip is the initial indication that something is wrong. Don’t think you can make up time. You can’t. Use the first slip to evaluate what’s going on versus what you’d like to have going on. When you hit the third or fourth slip, you’ve lost the schedule battle.
As an observant project manager, when you detect an early schedule slip, you have several options, all related to the project quality requirements and project constraints common to every project: With an early slip, you can change all, or a combination of these: 1) change the ship date or feature set, 2) allow different defect levels, 3) increase project cost, 4) add more people, or 5) change the work environment.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement