GREEN:  Project on schedule with no gating issues. 

AMBER:  Significant issues with interim deliverable(s), possible Interim deliverable slips. However, final deliverable(s) is/are still achievable with proper attention/involvement.

RED:  Serious issues.  Unlikely to make final deliverable

MIS Status Amplifications:
Amplification on status for MIS Integration Test Leads and Release Leads: 

GREEN:

· All of the project deliverable items will be accomplished in accordance to the current plan. 
· Scheduled deliverables include: the Preliminary or Final Integration Test Plan, Order Entry or Traffic matrices, Feeds, and or any milestones on the release schedule.  A Green Status also indicates a MIS recommendation for the project to be included in this Production release.
· If a recovery plan is being worked, then that plan is on schedule, at least one deliverable has been accomplished on this plan, and all subsequent deliverables are current against the plan.
· All known issues are actively being worked by the integration team according to an agreed to plan.  In a GREEN status, expect that there will be issues, however, these issues will have a resolution plan in place that does not affect project milestones.  Note: Gating means any “gates” in the testing activity or process that would prevent successful completion of the testing and project recommendation for release to production.
· For the release, all projects are reporting no significant issues with achieving implementation in the release.  All, or almost, all projects are reporting a GREEN status.

AMBER: 

· Significant issues with requirements or interim integration test deliverables, possible interim deliverable slips. 
· This project status is used when issues that affect the delivery schedule arise.  Significant software issues, schedule problems, and test case definition/requirements are good examples of things that cause non-GREEN status.  AMBER is used for problems, which cause (or can cause) interim deliverables to be missed.  If the final deliverable date is not in jeopardy, that is, a recovery plan is in place, the project should be AMBER and not RED.
· A contingency plan has been put in place and agreed to by all affected parties to ensure final deliverable is still achievable with proper attention/involvement.  However, no interim deliverable has been made according to the new plan.
· For the Release, most projects are reporting GREEN status with a small percentage of  AMBER and/or RED projects being reported.  Issues are being worked and reported appropriately to the Release Lead however the recovery plans have not yet met deliverables. 
· RED and AMBER are purposefully open to interpretation because of the complexity of projects and possible number of factors involved.  Each test lead should consult with the manager and the release lead to ensure full agreement within MIS 

RED:

· Serious integration test issues. Unlikely to make the implementation date under the current schedule and current requirements.
· A project’s status will remain as RED until a plan is put in place to meet all deliverables and meet the implementation date.  If all of the systems reschedule their implementation dates, the project could return to an AMBER or GREEN condition.  If some of the systems implement while others do not, an out-of-sync condition can cause the project to remain RED even though the recovery plan is agreed to by all parties.  In this case, a number of production problems could arise while testing continues.  If the project is placed on a new schedule and no milestones have occurred or been met, the project should probably remain in RED status until the recovery plan is met.
· A status of RED does not mean that the product will not implement.
· Requirement testing is failing.
· There is no set number of test cases or requirements that determine the RED status.  The interpretation is left to the integration test lead to work with the project team, including the MIS manager and release lead.  Until MIS assigns weighting factors to each requirement and a minimum percentage is set, the requirements justification for a non-GREEN status is left to the integration team.  If the project team is considering dropping/adding/modifying requirements, a change request needs to be brought to the Baseline Review Board.
· For the Release, a large percentage of the projects in the release are reporting AMBER and RED status.  A significant project that is reporting a RED status may cause the release to go RED.
· RED and AMBER are purposefully open to interpretation because of the complexity of projects and possible number of factors involved.  Each test lead should consult with the manager and the release lead to ensure full agreement within MIS.