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

Version 1 Next »

Scheduler Service Home

Boilerplate structure and text below

Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page.

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.

Summary

The Scheduler Service has been stubbed with the new templates. We have just begun to define what this will be. The Contract Description page for this service has not yet been added.

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!

Boilerplate structure and text below

Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page.

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

Cannot get the automated WSDL extraction tools working

Low

High

Test tools soon, work with KSS team to resolve problems. If need be, rework our templates until this works

Known Issues

Status of Milestones

  • No labels