Home
>
Articles
>
I am always intrigued to hear about projects that are consistent in terms of reporting their "stop light" status--and the consistency turns out to be the use of Code Yellow to report project status. Not that I am averse to this sunny color, but the notion that it can be used as a shield for self-defense against the closet monsters is something that I desist to nurture and promote.
Considerations regarding the usage of Code Yellow
- Code Yellow cannot be an "automatic project state" by default. Project progress and status needs to be reported against an established and agreed upon baseline. While not all projects (and project managers) might use formal processes like Earned Value Management, the reality is that you need at least one baseline and an agreed-upon process to track and report against the baseline.
Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Exclusively disclosing the powerful capabilities included in Microsoft Project 2010 and Microsoft Enterprise Project Management (EPM) Solutions while providing real world guidance on how Microsoft Project 2007 and Microsoft EPM Solutions are helping customers today with project and portfolio management to save money, enhance efficiency and prepare for future growth. Register Today!
Use WorkLenz PPM to Manage Agile Software Development
We invite you to download Métier’s latest white paper, Agile Software Development with WorkLenz, to learn how you can use WorkLenz to manage agile within your organization.
| "I'm glad I did it, partly because it was worth it, but mostly because I shall never have to do it again." |
| - Mark Twain |
|
sponsors
