Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Summary

Unknown macro: {multi-excerpt}
The Location Service description and assumptions have been filled out, and some questions identified. Issues remain on the modeling of types, hierarchy, and models for association ro other entities. Contracts and schemas have not been developed.

GREEN

- 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.

YELLOW

- 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.

RED

- 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.

It is important to keep this up to date. In general, it is better to raise flags early!

Risks

Describe each risk, estimate the likelihood (Low, Medium, High) and the severity of impact (Low, Medium, High), and then provide a mitigation plan

#

Description

Likelihood

Severity

Mitigation

1

We are going beyond what KSS is doing, and we may diverge from them. They are deferring this for now, so it will likely not be an issues for a while.

Low

Med

Meet with them soon and begin a governance process for Location modeling.

Known Issues

Status of Milestones

  • Complete initial design, specification - In Progress
  • No labels