<<Project Name>>

Team Lead Project Progress Report

 

 

<<Sub-heading>>

 

 

Directions for using template:

Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within <<Begin text here>> with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used.

 

Some templates have four levels of headings.  They are not indented, but can be differentiated by font type and size:

You may elect to indent sections for readability.

 

Distribution

Name

Position

 

 

 

 

 

 

 

 

 

Document Properties

Item

Details

Document Title

Team Lead Project Progress Report

Author

<<Author>>, <<Author Position>>

For Week Ending

<< dd-month-yyyy >>

Today’s Date

<< dd-month-yyyy >>

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ó 2002 Microsoft Corporation. All rights reserved.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.

 



 

Table of Contents

Team Lead Project Progress Report 2

Activity Summary. 2

Open Action Items. 2

Issues and Opportunities. 2

Team Project Schedule Update. 3

 

 

 


 

Team Lead Project Progress Report

[Description The Team Lead Project Progress Report summarizes your team’s progress on this project, including variance and impact on project delivery (schedule, cost, and scope). Depending on your project’s communication plan, you may want to prepare and distribute this report weekly.

 

Justification: This report communicates project status, progress, and important issues to the Project Manager, Project Sponsor, or Stakeholders. If you are the Team Lead on a large project, your status information will likely go to the Project Manager. If you are the Project Manager, your status information will likely go to your Project Sponsor or others.]

 

Activity Summary

[Description: This section summarizes the work completed by the team for the reporting period.

 

Justification: This section highlights (avoid exhaustive detail) work completed.]

 

The following is a brief summary of the major team activities and accomplishments for the week:

 

·                Activity 1

·                Activity 2

·                Activity 3

 

Open Action Items

[Description: This section summarizes “open” action items scheduled for completion within the reporting period.

 

Justification: This section ensures tracking and reporting of items that have not been completed.]

 

The following is a summary of the action items that are open at the time of this report:

 

·                Action Item 1

·                Action Item 2

·                Action Item 3

 

Issues and Opportunities

[Description: This section lists issues that affect the project and highlights project-related opportunities.

 

Justification: Issues and Opportunities address open action items and communicate project variances or impact on project delivery. Whether or not a variance creates an impact depends on project priorities and expectations.)

 

Issues for Escalation are highly likely to impact schedule or quality: events happening now or in the immediate future that will jeopardize the project. Note: Schedule variance on tasks not on the Critical Path may not pose a problem as long as you do not use up all your slack on those tasks.]

 

The following are the top issues that affect the completion of the team’s assignments. They are listed in order, starting with the item that has the greatest possible impact on our work.

 

·         Issues for Escalation (also referred to as Red or High)

·         Potential Issues (also referred to as Yellow or Medium)

 

The following are opportunities to enhance the project’s efforts:

 

·         Opportunities (also referred to as Green) 

 

 

Team Project Schedule Update

[Description: The Team Project Schedule Update provides a detailed report of changes to schedule status.

 

Justification: This section updates the status of tasks, or work packages, being performed by sub-teams or individuals on a project (development team, test team, etc.). These will become part of the master project schedule.

 

For optimum efficiency, enter task names as they appear on the master schedule. 

If you are using Microsoft® Project, Microsoft® Excel, or other tool to track tasks, simply insert a link to those files.]

 

The following is a list of the work packages (or tasks) my team worked on in the last week:


 

 



 

 

 

 

 

Work packages assigned this week

Complete?

Hours worked

Estimated hours remaining

Estimated
completion date

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

I have updated the project schedule for all activities in the above work packages or tasks:

  Yes

  No