Digital Project Management Discussion – Description
Project: From Methodology to Execution
Write a Project Scope
Success CriteriaSpecifications
Describe the business objectives
The submission describes the business objectives for Yosemite and for The Stefano Shop in three to four sentences.
Identify the milestones or deliverables
The submission includes at least 3 project milestones and deliverables.
List resources
The submission answers the following question:
What resources as the project manager do you have to complete the project?
Do a Cost-Benefit Analysis
The submission:
Lists the Cost-Benefit formula.
Identifies and uses the appropriate data from the Project Scenario section.
States what ratio the formula resulted in and whether it indicates a positive or negative investment.
Identify the scope’s schedule
The submission indicates the minimum and the maximum number of weeks required to complete the project.
Choose and justify a methodology for this project scenario
In four to five sentences, the submission:
Proposes a methodology (Waterfall or Agile) for organizing the project.
Explains why this methodology was chosen over the other.
Plan meetings with stakeholders
The submission answers the following question:
What kind of meetings will you have with stakeholders and how often?
The submission ties the rationale of the meeting cadence with the project methodology.
Identify Your Stakeholders and Team
Success CriteriaSpecifications
Conduct a stakeholder analysis
The submission classifies the influence level and the amount of authoritative power of each stakeholder as either “high” or “low”.
The submission explains how the stakeholder might affect the project negatively or positively and adds possible ideas for engaging them in the Assumptions and Risks column.
The assumptions reference the profiles in The Cast of Characters section in Step 1.
Anticipate task assignment by creating a RACI Chart
Assign a RACI classification for each stakeholder in each task.
Make a Project Plan
Success CriteriaSpecifications
Model a project plan based on the project methodology
The final project plan will meet the following specifications:
Be a snapshot of the planning phase of the project
Include deliverables
Include tasks
Tasks will have assignees
Deliverables/tasks will have a start and end date
Waterfall submissions should:
Include a completed Gantt Chart Template with the following components: a. Phases b. Tasks c. Assignee d. Dates and duration e. Highlighted dates for each task
Include additional tasks related to stakeholder engagement, team management, and closure activities.
Agile submissions should:
Include a URL to a Scrum board on Trello with the following components: a. The columns are based on Scrum phases. b. Include relevant tasks that occur in the initial and end phases of a Sprint. c. Tasks are labeled according to the Sprint/Priority it belongs to (e.g. Sprint 1, Sprint 2… P1, P2…).
Analyze Risk and Select Response Strategy
Success CriteriaSpecifications
Analyze the impact of a risk
For the two risk scenarios, the submission:
Answers the question “how might this risk affect the project?”
Covers at least 3 different critical points of risk, including but not limited to scope, cost, schedule, quality, stakeholder relationships, etc.
And, in four to five sentences, lists what aspects of the project are impacted by the risk and explains why.
Select an appropriate Risk Response Strategy
The submission identifies an appropriate Risk Response Strategy and explains how it would be applied to the resolution in four to five sentences.
Plan Knowledge Share and Report Project Status
Success CriteriaSpecifications
Identify key documentation needs
The submission:
Lists the documentation tasks in the table
Includes the assignee and the schedule for each task
Explains why it is important to document this task
Includes documentation tasks in the project plan created in Step 4
Has at least one documentation task for each feature of the Yosemite project
Each team must be assigned at least one documentation task
At least one piece of documentation is created for the Stefano’s
The project manager is assigned to write at least one piece of documentation
Create a Status Report for key stakeholders
Part One The status report must be in the timeline as an added task.
The submission explains the following:
Where in your timeline did you schedule or add the task for creating and sending a status report?
How do you plan to communicate the report to stakeholders, and how often?
Part Two The submission includes two status reports based on the Status Report Template.
The date for each report matches the project plan in Section 4:
The date of the first Status Report is the date when the Vendor Manager was scheduled to begin the “Input Inventory Data” task.
The date of the second Status Report can fall in the middle of the Engineering team building the recommendation engine.
The following Status Report sections -summary, highlights/blockers, and health check- should then coincide with the project plan’s timeline.
Suggestions to Make Your Project Stand Out
To go above and beyond, create a project plan in the other methodology. For example, if you completed the final project with a Waterfall Gantt Chart, now create an Agile Scrum Board. Then fill out the Standout Submission Template with the lessons learned from creating the two project plans. Upon completion, export the template as a PDF and include it in the Final Project zip (compressed) folder of all final materials.
The post Digital Project Management Discussion first appeared on .
