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 10 Current »

Status

Summary

The Contact Service basics (Description and Assumptions) have been worked out well, and largely align to the KSS models for the same information. The contract and schemas remain to be developed.

Current Status Guidelines

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

The KSS model for Contact Usage seems like more than we need, and there is risk of divergence due to the difference in requirements.

Medium

Medium

We need to talk to the KSS team about how central this is, and how we can ignore it without violating the model.

Known Issues

Status of Milestones

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