Agile Project Management
Agile
Developed for Software projects, but it is a
methodology that can be used on all Projects types
Agile is an umbrella term that is used to refer to
different types of iterative development
Scrum is the most common method of agile, there
are others such as extreme programming (XP), lean
development, and Kanban.
Agile vs. Traditional Project Management
Agile builds in increments vs. as a whole
Agile does planning throughout vs. done all at once
Agile delivers products over time vs. all at once
Customers sees value faster vs. at the end
Agile wants changes vs. discouraging changes
Agile Terms
Product Owner - Designated person that represents the customer on the project
Agile Project Manager/Scrum Master – Manages the agile project
Product Backlog - Project requirements from the stakeholders
Sprint Planning Meeting- Meeting done by the agile team to determine what features will be done in the next sprint
Sprint Backlog – Work the team selects to get done in the next sprint
Sprint/Iteration - A short iteration where the project teams work to complete the work in the sprint backlog, (1-4 weeks typical)
Daily Stand Up Meeting - A quick meeting each day to discuss project statuses, led by the Scrum Master. Usually 15 minutes
Sprint Review – An inspection done at the end of the sprint by the customers
Retrospective – Meeting done to determine what went wrong during the sprint and what when right. Lesson learned for the sprint.
Partial Completed Product - Customers Demo the product and provides feedback. This feedback adjust the next Sprint priorities
Release - Several Sprints worth of work directed to operations for possible rollout and testing
Agile Process
Product Sprint Sprint
Customers/Product Planning
Sprint/Iteration
Ownwer Backlog Backlog
Meeting
Potentially Sprint Sprint Review
Shippable Product REtrospective Meeting
Increment
Agile
Agile Benefits
Benefits where scope is unknown up front
Cost and Schedule fixed, Scope Varies
Customer involved throughout the life cycle
Greater Customer Interaction with all stakeholders
Constant Feedback is required to stay current and
successful
Greater Value up front
Change is welcomed by all stakeholders
Agile Integration Management
Concepts of integration management doesn’t change
Detailed planning and delivery of the product is delegated to the
team
Project Manager is more focus on building an environment that
accepts changes and more decision making by the team
Agile Scope Management
Agile methods spends less time on defining the scope early
More time is spent discovering what the requirements are through
prototypes
Scope is defined and redefined throughout the agile project
Agile Schedule Management
Since scope changes throughout the agile project, Schedule
estimates are difficult
Shorter development lifecycle
Agile Cost Management
Since scope changes throughout the agile project, cost estimates
are difficult
May not use detailed cost estimates due to lots of changes
Use a lightweight estimation method that can be done quick
Agile Quality Management
Should produce a high quality product through frequent
inspections by the customers.
Retrospectives done at the end of all Iterations will lead to
processes with fewer defects as the agile project progresses
Agile Resource Management
Build self-organizing teams with generalizing specialists
Collaboration with the team with will lead to solving problems
quicker and easier
Agile Communication Management
Due to frequent changes communications is key
Use lots of low-tech high-touch tools, such as a whiteboard vs.
software
Regular meeting(Daily Stand-up)
Use co-location
Agile Risk Management
Frequent changes leads to more uncertainty and risk
Use the frequent review by the customers to identify risk and
responses
Use cross-functional teams
Agile Procurement Management
Can be difficult due to the frequent changes in the scope
Should develop a risk procurement model where risk is shared
between the buyer and seller
Agile Stakeholders Management
Frequent changes require more active engagement and
participation with the stakeholders
Invite any stakeholder to project meeting and reviews
More engagement will lead to issues be resolved quickly and in the
interest of the customers
