Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 3 - Coggle Diagram
CHAPTER 3
Knowledge Area Mapping
Project Integration Management
Project Scope Management
Project Time Management
Project Cost Management
Project Quality Management
Projects Human Resources Management
Project Communication Management
Project Risk Management
Project Procorement Management
Project Stakeholder Management
Project Management Process Groups
A process is a series of actions directed toward a particular result
The project management process groups include
initiating processes
planning processes
executing processes
monitoring and controlling processes
closing processes
Developing an IT Project Management Methodology
Many organizations develop their own project management methodologies, especially for IT projects
A methodology describes how things should be done; a standard describes what should be done
Case Study: JWD Consulting’s Project Management Intranet Site (Predictive Approach)
This case study provides an example of what’s involved in initiating, planning, executing, controlling, and closing an IT project
Project Pre-initiation
good practice to lay the groundwork for a project before it officially starts
Project Initiation
recognizing and starting a new project or project phase
Project Charters and Kick-off Meetings
Charters are normally short and include key project information and stakeholder signatures
Project Planning
to guide execution
Project Executing
Usually takes the most time and resources to perform project execution
Project Monitoring and Controlling
Involves measuring progress toward project objectives, monitoring deviation from the plan, and taking correction actions
Project Closing
Involves gaining stakeholder and customer acceptance of the final products and services
Case Study 2: JWD Consulting’s Project Management Intranet Site (Agile Approach)
demonstrates a more agile approach to managing the same project
Scrum Roles
Product owner
Scrum Master
Scrum team or development team
Scrum Artifacts
Product backlog
Sprint backlog
Burndown chart
Scrum Ceremonies
Daily Scrum: A short meeting for the development team to share progress and challenges and plan work for the day
Planning
Descriptions of work are identified in the product and sprint backlogs, more detailed work documented in technical stories, estimate a velocity or capacity for each sprint; release roadmap often used for schedule
Executing
Produce several releases of software
Communications different because the project team meets every morning, physically or virtually
Monitoring and Controlling
Names of key reviews are the daily Scrum and the sprint review
Closing
The retrospective is similar to a lessons-learned report, but it focuses on a shorter period of time