Project Management Insights: Lessons in project quality
August 22, 2007 from Raven's Brain: Project Management
-
Lesson #1: Don't reward for shipping on schedule. Anyone can ship garbage. Base rewards on quality metrics.
-
Lesson #2: Don't reward heroes for their Herculean effort late in the project to fix problems that could have—and should have—been fixed by the same people much earlier in the lifecycle.
-
Lesson #3: If you expect to work your people inordinate hours, you might want to consider corporate-sponsored flu shots!
-
Lesson #4: Always include QA and other project team members in all reviews to get the most well-rounded input possible.
-
Lesson #5: It's easy to ignore documents that are sent by e-mail for approval. No response does not equal approval: No response means, "I didn't have time to read it."
-
Lesson #6: Don't start coding until the requirements are stable and understood, or else budget time for subsequent rework.
-
Lesson #7: Code isn't "complete" until it works. Good unit testing is part of the development effort, not an optional item to be jettisoned when the schedule is tight.
-
Lesson #8: Is your test team always grumpy? Maybe it has good reasons!
-
Lesson #9: To maximize team efficiency, the project plan must consider testing efficiency. This may determine feature implementation order.
-
Lesson #10: Buggy software takes longer to ship.
Read CIO Article: http://www.cio.com/article/112800/Quality_Doesn_rsquo_t_Just_Happen/3
Read Tanmay's Post: http://qualsys.wordpress.com/2007/08/06/lessons-in-project-quality/
posted by Raven Young at Raven's Brain under Project Management
Tags: Quality Management, Project Management, Software Testing, Technology Project Management

Comments
Got something to say?
[More Help]