|
|
|
|
 | |  |
| So, the next order of business is to color code the projects so senior management doesnt have to read anything. We can say GREEN is GO | |
 | |  |
|
 |
| | |
| Um... I dont think I would go that far. Software's hard. Anything can happen. Dont want people to assume we are GO | |
| | |
|
|
|
|
|
|
|
| | |
| Fair point. What if we say GREEN means 'Based on what we know at this second, project will be done, but there could be significant work left to do and open issues to resolve' | |
| | |
|
|
| | |
| To be safe, I'd change the 'will be' to 'could be' | |
| | |
|
|
|
|
|
|
|
| | |
| Will do! I think we're done here. We can meet tomorrow to discuss yellow. | |
| | |
|
|
|
|
