Determine appropriate methods to monitor and communicate the status of a project
Scenario
You are in the 10th week of the XYZ Business Workflow project, and things haven’t quite gone according to plan. At the end of the requirements analysis phase, your team told you the following information:
Feature 2 (F2) development is more complex than initially thought. It will take at least 10 workweeks to complete.
Feature Customization 3 (C3) will take close to five workweeks.
The complete system testing will take a minimum of one and a half weeks due to the complexity of the systems involved.
You made some necessary resource and schedule adjustments in your plan and obtained stakeholder approval for the same.
However, due to delays in getting client approvals, UI design and development took one week more than estimated, which has now pushed all dependent tasks out by a week. Moreover, a resource availability issue has added three days to the Feature 1 development effort.
You are scheduled to present a project status report at the end of the week at a stakeholders’ meeting that will include the client’s representatives.
Directions
Project Status Report
Create a presentation for stakeholders describing relevant aspects of the current project status. Your presentation must include the following information:
Original and current project schedule
Current project status
Updated risk register
Any other relevant project information you believe the stakeholders need to know
You can use any project management software (PMS) tool to create and update the project schedule and status. However, remember to choose a tool that will help you complete all parts of the project, like the Gantt chart.
Specifically, your presentation must include the following rubric criteria:
General project information
List the project goal and objectives.
Include the team information.
Detail the initial schedule with milestones and end dates.
Current project status
Include a Gantt chart that shows the project’s progress and current schedule.
Update the risk register. If an issue has occurred, add the issue to the Issue Log. An updated risk register includes the following information:
Status of risks from the project planning phase, including whether and how they have affected the project plan and schedule so far
Any issues facing the team currently and how you are managing them
Any new potential risks and proposed mitigation
Project summary
Include the updated milestone and end dates.
List action items to ensure the project stays on track.
Use the information from the scenario to make reasonable assumptions as you complete these tasks. Be certain to explain your assumptions. Include any additional information, such as your comments and assumptions, in the slide notes.
