Please enable JavaScript.
Coggle requires JavaScript to display documents.
Information Technology Project Management - Coggle Diagram
Information Technology Project Management
The Project Life Cycle
-Maps the life of a project
-From beginning, through its middle, to its end
-to define, build, and deliver the product
Project Phases
Phase Exits, Stage Gates, Kill Points
-These are the phase-end review of key deliverables
-Allows the organization to evaluate performance and take immediate action to correct errors or problems
Fast Tracking
-Starting the next phase of a project before approval is obtained for the current phase
-To reduce the project schedule
-Risky and should only be done when the risk is acceptable
Define and Plan
Plan Project
Project Objectives
Controls
Resources
Define Project Goal
-The project goal should be focused on providing business value to the organization
-Provides a clear focus and drives the other phases of the project
-How will we know if this project is successful given the time, money, and resources invested?
Execute,Close and Evaluate
Execute Project Plan
-Progress must be documented and compared to the baseline plan
-Project performance must be communicated to all of the stakeholders
-Manage the project scope, schedule, budget, and people to ensure the project achieves its goal
Close and Evaluate Project
-Lessons learned and best practices documented and shared
-Final project report and presentation to the client
-Postmortem review
-Ensures that all of the work is completed as planned
PMBOK Guide
5 PMBOK Project Management Process
Groups
-Initiating
-Executing
-Closing
-Planning
-Monitoring and Controlling
The 10 Project Management Knowledge : Areas
:fountain_pen:Project integration management
:fountain_pen:Project scope management
:fountain_pen:Project time management
:fountain_pen:Project cost management
:fountain_pen:Project quality management
:fountain_pen:Project human resource management
:fountain_pen:Project communications management
:fountain_pen:Project risk management
:fountain_pen:Project procurement management
:fountain_pen:Project stakeholder management
THE PRINCE2
7 Processes
-Start Project
-Initiate Project
-Direct Project
-Control Stage
-Manage Product Delivery
-Manage Stage Boundaries
-Close Project
Themes(to aid project goal achievement)
-Business Case
-Organization
-Risk
-Quality
-Change
-Planning
-Progress
Principles
-Business Case Driven
-Product Focus
-Lessons Learned
-Manage the Stage
-Adapt to the Project
Manage by Exception only significant deviations from a budget or plan are brought to the attention of management.
-Accountability
Systems Development Life Cycle (SDLC)
-Planning
-Analysis
-Design
-Implementation
-Maintenance and Support
Implementing the SDLC
Defines all of the subphases and deliverables associated with the Execute and Control Project Management Life Cycle phase.
Number of Ways to implement the SDLC
-Waterfall
-Agile
Agile Systems Development
What is Agile?
-Emphasize working software to measure progress and rely heavily on face-to-face communication
-Condenses the SDLC into an iteration or sprint
-Umbrella term that includes a number of approaches or methods
-Users and developers work closely together to define and prioritize important (“must have”) features
4 theme/ categories
-Performance
-Customer
-Product
-Project Team
Manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items onthe right, we value the items on the left more.
Agile Methods: Extreme Programming (XP) and Scrum
XP
User requirements first documented as user stories
Document user stories in an object oriented model called a class diagram
Transfers the system in a series of versions called releases
Scrum
Three important roles:
Scrum master – similar to project manager
Product owner – represents the business side, ensures the most important features are included
Development team – responsible for delivering a quality product or system
Product backlog – team prioritizes features that need to be developed/delivered
Sprint – iterations lasting a few weeks (usually) and delivers a complete product
Daily scrum – short stand-up meeting
Introduction
A strategic-level plan for managing and controlling the project
Game plan for implementing project and product lifecycles
Recommends phases, processes, tools, and techniques for supporting an IT project
Flexible and include “best practices” learned from experiences over time.
A Learning Cycle
1) Understand & frame the problem.
2) Plan
3) Act
4) Reflect & learn
Each cycle provides the opportunity to
challenge framing assumptions, create new understanding & find radical solutions
Team Learning record
what we know (Facts)
What we think we know( Assumptions)
*What we don't know (Question to be Answered)
Action Plan
Who?
Does What?
By When?
