Code Yellow


Home  >  Articles  > 
Code Yellow

Sainath Nagarajan, PMP, SCPM

November 30, 2005







<A TARGET="_blank" HREF="http://www.gantthead.com/clickCount.cfm?ID=243479"><IMG SRC="/flash/build_336x2804.gif" BORDER=0></A>
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
    "Selecting the Right Requirements Management Tool – Or Maybe None Whatsoever" – Get your free copy of this independent report by Forrester Research, compliments of MKS.

    There is a balance between monitoring and blocking web use in the workplace. IT Managers need to determine the best way to deal with employee internet access while keeping the overall good of the business a priority. Download this whitepaper to help make an informed decision about your own web monitoring requirements

    PMO hit the wall yet? Join us for a private "gantthead PMO Management Package" seminar just for your company to see a PMO Content Asset solution for your PMO. Stop setting up PMO content assets from scratch. Schedule your 30 minute Executive Overview - at a time convenient for you.



    Some editors are failed writers, but so are most writers.
    - T. S. Eliot