"1. The project has launched without senior buy-in
2. No detailed project plan exists
3. Meetings have been scheduled without concern for team member availability
4. Users have had little (to no) early involvement
5. The project targets the minimum specs
6. Testing is an afterthought
7. No recovery plan is in place in the event of failure
8. Expert recommendations have been rebuffed without testing outcomes
9. The go-live date is a weekend or holiday
10. Expectations have not been set
11. Skimp on training"
http://www.itnews.com/it-management/59664/11-signs-your-it-project-doomed?page=0,3
We are about to launch a new application and I have four years experience in software development or planning and I also faced with very similar problems. Only the clear and honest communication can resolve the conflicts for failure.
2. No detailed project plan exists
3. Meetings have been scheduled without concern for team member availability
4. Users have had little (to no) early involvement
5. The project targets the minimum specs
6. Testing is an afterthought
7. No recovery plan is in place in the event of failure
8. Expert recommendations have been rebuffed without testing outcomes
9. The go-live date is a weekend or holiday
10. Expectations have not been set
11. Skimp on training"
http://www.itnews.com/it-management/59664/11-signs-your-it-project-doomed?page=0,3
We are about to launch a new application and I have four years experience in software development or planning and I also faced with very similar problems. Only the clear and honest communication can resolve the conflicts for failure.
Nincsenek megjegyzések:
Megjegyzés küldése