What does the red, yellow, green color model have to do with LabVIEW? Well the color model doesn’t but since I’ve been working on getting a project plan together for a new project in the LabVIEW team I thought I’d share a little information about red, yellow and green.
The creativity of the engineers in the LabVIEW team and also the ideas and needs of our customers seem unbounded at times. So inevitably any release of LabVIEW or a given project starts with a very long list of possibilities. As I discussed earlier, some ideas require some prototype work before we feel comfortable with what we need. An example of this would be something like the System Diagram that was shown at NI-Week this year.
Once we have an idea of what is needed the task of putting the project plan begins. This includes all the things you’d normally think of, budgeting, risk analysis, market analysis and of course feature and scope definition. It’s with feature and scope definition that “red, yellow, green” comes in. The importance of features are classified by color, you guessed it “red, yellow, green”.
Green – Required to release
Yellow – Optional to release
Red – NOT in release
Green features shouldn’t take much explanation. Yellow are features that we plan to work on but after the required green features are completed, and if we don’t get to them then we wouldn’t hold the release up for them. This makes a lot of sense as introducing features late in a release can negatively impact stability so having a bar set earlier on helps ensure consistency in planning and delivery.
Why call out Red features, things you aren’t even going to work on? Well it’s precisely because you aren’t going to work on them. Red classifications are used as a communication tool, to explicitly call out a feature for stakeholders that might have expected them or may have been a priority at one time but aren’t now.
On to making some more Red, Yellow, Green recommendations. Hope you had a good Turkey day.