Can anybody help me completing this paper?
Project Two Guidelines and Rubric.html
Competency
In this project, you will demonstrate your mastery of the following competency:
- COM-30168: Determine appropriate methods to monitor and communicate the status of a project
Scenario
You are in the tenth 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 that:
- Feature 2 (F2) development is more complex than thought initially. It will take at least 10 workweeks to be 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: original and current project schedule, current project status, updated risk register, and 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:
- General project information
- Project goal and objectives
- Team information
- Initial schedule with milestones and end dates
- Current project status
- Gantt chart that shows the project’s progress and current schedule
- Updated risk/issues register that shows:
- 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
- Updated milestone and end dates
- Action items to ensure the project stays on track
What to Submit
To complete this project, you must submit the following:
Project Status Report Create a presentation of 8 to 12 slides to share the project status report at a stakeholders’ meeting. The presentation should include the basic project information, current project status, updated risks and issues, and a project summary.
Supporting Materials
The following resources may help support your work on the project:
Document: XYZ Business Workflow Resource and Effort Estimates This document provides the initial resource and effort estimate for the project.
Project Two Rubric
| Criteria | Exemplary (100%) | Proficient (85%) | Needs Improvement (55%) | Not Evident (0%) | Value |
|---|---|---|---|---|---|
| General Project Information | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Includes all relevant project details, such as project objectives, team structure, and initial milestone and release dates, in a concise, informative manner | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include verbose, missing, or irrelevant information | Does not attempt criterion | 20 |
| Project Status | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Includes the current schedule with a well-laid-out Gantt chart showing the percent of work completed in each task; includes an updated risk register showing the status of each risk, whether a risk occurred, and how it was handled; outlines any issues affecting project | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include missing schedule breakdown; unclear Gantt chart; missing tasks or milestones; missing or incorrect progress tracking; missing or vague risks and issues descriptions; issues or changes in estimates and schedules not handled appropriately | Does not attempt criterion | 45 |
| Project Summary | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Provides clear and concise project summary with any changes in milestones and release dates highlighted and explained; includes at least two action items to resolve issues and/or help the project stay on track | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include missing or vague summary; missing or irrelevant action items | Does not attempt criterion | 20 |
| Articulation of Response | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Clearly conveys meaning with correct grammar, sentence structure, and spelling, demonstrating an understanding of audience and purpose | Shows progress toward proficiency, but with errors in grammar, sentence structure, and spelling, negatively impacting readability | Submission has critical errors in grammar, sentence structure, and spelling, preventing understanding of ideas | 15 |
| Total: | 100% |
course_documents/QSO 340 XYZ Business Workflow Resource and Effort Estimates.pdf
QSO 340 XYZ Business Workflow Resource and Effort Estimates Project: XYZ Business Workflow Expected Start Date: March 1st Expected End Date: December 15th Full-time resources:
Software architect—Michael Lee
Technical team lead—To be decided (TBD)
Software developers—TBD
Software testers—TBD UI design and development team—TBD
Part-time resources:
Julia Smith—Product Manager (ABC Workflow v3.0)
Ryan Hernandez—Team Lead (ABC Workflow v3.0) Effort Estimates:
Task Estimated efforts
(workweeks)
Requirements Analysis 1 UI design and development 3
Feature 1 Development 10 Feature 2 Development 8
Feature 3 Development 7 Feature Customization 1 6 Feature Customization 2 6
Feature Customization 3 4 Feature Customization 4 3
Feature Customization 5 1 Software System Testing 1