2. Project
• Organized and elaborated set of work efforts
• Limited by time and resources with a defined
beginning and ending
3. Project Life Cycle
• Initiating: high level planning and starting the
project
• Planning: detailed planning
• Executing: implementing the detailed plan
• Closing: ending the project
4. Project Management Institute (PMI)
• PMI determines the standards of project
management
• The name of the standard of project
management is PMBOK.
• PMBOK: Project Management Body of
Knowledge
• In PMBOK, project is defined as “a temporary
endeavor undertaken to create a unique
product, service, or result.”
5. Project Management Body of Knowledge (PMBOK)
9 Knowledge Areas
• Project Scope Management
• Project Time Management
• Project Cost Management
• Project Quality
• Project Human Resource Management
• Project Communications Management
• Project Risk
• Project Procurement Management
• Project Integration Management
6. Agile Project Management (Agile PM)
• A style of software development that
concentrates on adaptive and exploratory,
rather than anticipatory and prescriptive
management.
• Project is implemented in iterations.
• Detailed plan is made for nearby iterations.
• Attention is moved from planning to
execution.
7. Agile Areas of Project Management
• Agile Scope Management
– Scope is defined broadly and controlled
• Agile Time Management
– Schedule is flexible
• Agile Cost Management
– Costs are estimated after iterations
• Agile Risk Management
– Higher risk aspects are completed first
• Agile Quality Management
– Quality is assessed after iterations
8. Traditional PM versus Agile PM
• Traditional PM concentrates on detailed planning
of the entire project.
– Agile PM does short plans.
• Traditional PM requires high predictability for the
success.
– Agile PM is exploratory, and is also suitable for less-
predictable projects. Agile PM is incremental and
iterative.
• Traditional PM gathers customer requirements at
the beginning.
– Agile PM focuses on collaboration with customer and
gathers requirements continuously.
9. Planning and Tracking an Agile Project
• Backlog is prioritized with gross estimates.
• Team velocity is estimated.
• Iterations are created.
• Next iteratations are planned in detail.
• Completed tasks are tracked.
• Backlog is updated, prioritized after iterations.
• Estimates are recalculated.