What dance do you do when your project is Yellow? #PMOT

It seems that everyone is pretty comfortable when it comes to the definition of a project that is either green and red.

Green – everything is going well, on track for schedule, scope, and budget.

Red – serious problems that need stakeholder help to resolve. Probably unable to materially meet schedule, scope, and/or budget.

But Yellow?

Yellow seems to be the colour in the middle where there is a wide range of status and actions.

To some, any amount over budget turns the project yellow. Some only turn it yellow after the schedule, scope, or budget overages exceed 5%.

To some, a yellow project requires an action plan. Some turn it yellow to indicate that it is being watched, but that no actions are required.

Which is correct?

I would suggest that depends on the culture of the project, team, and client. But I do tend to see two types of yellow dances that occur on projects.

The Yellow Dances

Using using the dance metaphor, I am proposing that the two partners in the dance are the project and the project status. The dance that they do reflect the interactions that occur during the lifetime of the project.

The Green Waltz – I use the Green Waltz dance to refer to the more formal behaviour of the project and project status. In this dance, the project and project status relationship is quite formal. The status is usually communicated via status reports. Much of the focus of the project is to do whatever it takes to turn the yellow project back into green as quickly as possible. As a result, this dance is very quick as the change request tempo can become very up tempo. During the course of the dance, the yellow/green transitions(change requests) can come at a furious pace.

Pros – Any exceptions to the plan are highlighted.

Cons – The project may be green at the end and people may think it is fine, but there may have been numerous change requests that only give the appearance of everything being fine. The status does not represent the holistic status, only the current point in time status of current plan against current actuals.

The Yellow Tango – Unlike the Green Waltz, the Yellow Tango is less about seeking to become green and more about understanding the rhythm of your partner and reacting. The Yellow Tango embraces yellow and does not try to guide it back to green. The dance understands that both partners lead the dance at certain times, and tries not to force it back to green without good reason. The Yellow Tango is a slower dance, without the up tempo of numerous change requests. But if a change request is required it usually is a larger, sudden movement and change in the dance.

Pros – the status holistically communicates the status of the entire project, not just at that point in time.

Cons – The reduced formality can result in delayed escalation of issues until they become large enough. This may be an issue depending on the dance hall you are in. 🙂 Some dances halls are ok with these exaggerated movements, some not so much.


Both dances are appropriate and neither are right or wrong. Many times, the dance will be stipulated by the client/dance hall.

My personal preference is for the Yellow Tango as I feel it does communicate the overall status as opposed to just a point in time. As with the Tango though, it is a more involved and complex dance. I think it does required a more educated client and team. I also find the  Yellow Tango better for Agile projects when things are just bigger or more complex without added scope. The Yellow Tango more honestly recognizes that we don’t know everything up front and we will manage the items together in clear, open, and honest communication.

Author: Terry Bunio

Terry Bunio is passionate about his work as the Manager of the Project Management Office at the University of Manitoba. Terry oversees the governance on Information Technology projects to make sure the most important projects are being worked on in a consistent and effective way. Terry also provides leadership on the customized Project Methodology that is followed. The Project Methodology is a equal mix of Prince2, Agile, Traditional, and Business Value. Terry strives to bring Brutal Visibility, Eliminating Information islands, Right Sizing Documentation, Promoting Collaboration and Role-Based Non-Consensus, and short Feedback Loops to Minimize Inventory to the Agile Project Management Office. As a fan of pragmatic Agile, Terry always tries to determine if we can deliver value as soon as possible through iterations. As a practical Project Manager, Terry is known to challenge assumptions and strive to strike the balance between the theoretical and real world approaches for both Traditional and Agile approaches. Terry is a fan of AWE (Agile With Estimates), the Green Bay Packers, Winnipeg Jets, and asking why?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.