Status Reporting Templete - Ejemplo Documento

Status Reporting Templete

1. Status Reporting Sample Status Template and Instructions

2. ‹#› (Team) Status for Week Ending (Date) Milestone ID Description Date Status Not Started Complete Green Yellow Red Major Activities- Next 2 Weeks New Risks, Issues, or Change Requests Escalations and Decisions Needed Accomplishments- Last 2 Weeks Status Template

3. Using the Status Reporting Template 1 Ensure Team Name and week ending date are correct Enter accomplishments and plans. Note: these should be discussed primarily in the context of milestones. An excess of items unrelated to planned milestones could indicate: Incomplete planning Scope creep Lack of focus Suboptimal prioritization Milestone ID & date match values on program workplan. Status is determined as described on the right. List items as indicated in the column headers. Leave blank if not applicable. Ensure items entered here are also completed on any applicable program logs, i.e. Risk Log, Issues Log, Decisions Log. 2 3 4 Status Guidelines Blue= Completed milestone Green= confident the milestone will be completed on or before date Yellow= on-time milestone completion is at risk Red= milestone will not be completed on or before date

4. Sample Status Reporting Process Status reporting assumes Friday as the week ending date. If you expect significant changes to status late Friday afternoon or over a weekend, contact IMO to request a status reporting extension for that week. Status reports should be available in your team’s Status Reports folder on the program sharing site by noon each Friday. Status report files should be saved using the convention Team Abbreviation_Date_Status. For example the Accounting team would save a status report for September 14, 2018 as follows: “ACTG_Sept14 2018_Status” Please save each week’s status report as a new file, so as to maintain an archive of previous week’s reports.