Status
This should collect together both a summary status that is excerpted into the home page, as well as some breakdown for more detailed understanding of where the development stands. Suggested sections are specified below, but this will need refinement as we proceed.
...
| Excerpt |
|---|
| Div |
|---|
| style | background-color:#aaffaa |
|---|
| | The New Authentication Service description templates are well sketched out, and we are on track to resolve the outstanding template issues. |
|
Guidelines:...
| style | background-color:#aaffaa |
|---|
...
If the current work is essentially on track, with only minor schedule slip that you have high confidence will not impact dependent tasks, use the green status
| Div |
|---|
| style | background-color:#ffff99 |
|---|
|
If the current work is slipping, with moderate schedule slip that will impact dependent tasks, and that threatens the current milestones by up to something like 25%, use the yellow status. Yellow status merits regular monitoring at a team level. |
| Div |
|---|
| style | background-color:#ffaaaa |
|---|
|
If the current work is blocked, with major schedule slip that impacts dependent tasks, or for which a major issue has arisen that threatens delivery of the service, use the red status. Red status merits review at a leadership level. |
...
| Insert excerpt |
|---|
| Current Status Guidelines |
|---|
| Current Status Guidelines |
|---|
|
|
Risks
Describe each risk, estimate the likelihood (Low, Medium, High) and the severity of impact (Low, Medium, High), and then provide a mitigation plan
...