Agile Project Management
PMI Metrolina PDD
Saturday September 27, 2014
UNCC Uptown
Mike Ryan
Objectives
What is Agile?
What is the Agile Manifesto?
What are the Principles of the Agile Manifesto?
What is Scrum?
What are the Foundations of Scrum?
How does Scrum work?
3/21/2016
Copyright: Mike Ryan
2
Sticky Notes ( 5 minutes)
Meet your tablemates by introducing
yourself.
Chat amongst your team. Discuss some
questions about Agile that your team would like
to have answered before we finish today.
Document your questions, one question per Post
it note.
Each team should read their most compelling
question.
Display your questions prominently at the front
of the room.
3/21/2016
Copyright: Mike Ryan
3
How have we done?
The Chaos Summary, a 2009 survey by the Standish
Group, indicated that only 32% of all projects
succeeded:
Failed
24%
Succeeded
32%
Challenged
44%
Source: The Standish Group
Succeeded ( delivered on time, on budget, with required features and functions )
Challenged ( late, over budget and/or with less than required features and functions )
Failed (cancelled prior to completion or delivered and never used)
3/21/2016
Copyright: Mike Ryan
32%
44%
24%
4
What is Agile?
Agile software development is a group of
software development methods in which
requirements and solutions evolve through
collaboration between self-organizing,
cross functional teams.
Source: Wikipedia
3/21/2016
Copyright: Mike Ryan
5
Agile Manifesto
Source: www.agilemanifesto.org
3/21/2016
Copyright: Mike Ryan
6
Agile Manifesto Principles
1.
2.
3.
4.
5.
Customer satisfaction by rapid delivery of useful software
Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than month
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be
trusted
6. Face-to-face conversation is the best form of communication (colocation)
7. Working software is the principal measure of progress
8. Sustainable development, able to maintain a constant pace
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work not done—is
essential
11. Self-organizing teams
12. Regular adaptation to changing circumstances
Source: www.agilemanifesto.org
3/21/2016
Copyright: Mike Ryan
7
Top 5 Agile Methodologies
1. Scrum
54%
2. Scrum/XP Hybrid 11%
3. Custom Hybrid
9%
4. Scrumban
7%
5. Kanban
4%
Key Takeaway: The Scrum methodology dominates.
Source: Version One State of Agile
3/21/2016
Copyright: Mike Ryan
8
Foundations of Scrum
Transparency
Inspection
Adaptation
3/21/2016
Copyright: Mike Ryan
9
Transparency
Transparency in Agile means all steps,
inputs, and outputs of the development
process are visible. An example of
transparency would be the burn down chart.
3/21/2016
Copyright: Mike Ryan
10
Inspection
Inspection provides an opportunity for
feedback on the product. A great example
of this is the Sprint demo.
3/21/2016
Copyright: Mike Ryan
11
Adaptation
Adaptation allows for making changes to
the processes or procedures. The Sprint
Retrospective is a great example of this.
3/21/2016
Copyright: Mike Ryan
12
Why Use/Be Agile?
Key Takeaway: Agile provides faster speed to market, more
readily allows for change, and satisfies the customer.
Source: VersionOne State of Agile Survey
3/21/2016
Copyright: Mike Ryan
13
The Penny Game
Instructions:
1. The game has three runs.
2. The workers job is to flip the pennies he/she receives as
fast as he/she can and then pass them on to next station.
3. The Department managers job is record how much time
their worker spends from the first to the last coin flipped.
4. The CEO takes total time from the first coin to the last.
3/21/2016
Copyright: Mike Ryan
14
The Ball Game
Instructions:
•
Everyone is part of a team.
•
Each ball must have “air time”
•
Balls cannot be passed to your direct neighbor to your immediate left or right.
•
Each ball must return to the same person who introduced it into the system.
Sequence of events:
Planning Session (2 minutes):
• Plan and design your process
• Provide estimate
Iteration 1 (2 minutes)
• Pass as many balls as possible
Perform a retrospective (2 minutes):
• Review your design and plan looking toward improving
Iteration 2 (2 minutes)
• Pass as many balls as possible
3/21/2016
Copyright: Mike Ryan
15
Does Agile Work?
Key Takeaway: It works
Key Takeaway: It can work.
Source: 2013 VersionOne State of Agile Survey
3/21/2016
Copyright: Mike Ryan
16
Project Management
Methodologies
Fixed
Features
Time
Budget
Value
Driven
Plan
Driven
Time Budget
Features
Estimated
Key Takeaway: Value driven approaches such as Agile
allow for adjusting the Features (scope), which Plan
Driven doesn’t easily allow.
3/21/2016
Copyright: Mike Ryan
17
Continual
Grooming
Key Takeaway: There are iterations at multiple points in the
framework.
Source: www.mountaingoatsoftware.com
3/21/2016
Copyright: Mike Ryan
18
The Roadmap
Key Takeaway: This is the long term plan for the product and
the Product Owner is the steward of the roadmap.
3/21/2016
Copyright: Mike Ryan
19
The Backlog
Key Takeaway: Stories which have not been completed and have
value to the customer. The backlog should be regularly prioritized,
groomed and include “acceptance criteria”. If a story is not properly
groomed it should not be pulled into sprint.
3/21/2016
Copyright: Mike Ryan
20
Sprint Planning
Key Takeaway: This is a planning session where you determine what is
to be pulled in from the backlog for the next sprint. If the story is not
properly groomed it should not be pulled into the sprint.
3/21/2016
Copyright: Mike Ryan
21
The Daily Scrum
Key Takeaway: This is a 15 minute stand up meeting where you
communicate what was done yesterday, what will be done today
and any impediments
3/21/2016
Copyright: Mike Ryan
22
Build High Value First
V
a
l
u
e
High Value
Low Complexity
1
2
High Value
High Complexity
Low Value
Low Complexity
3
4
Low Value
High Complexity
Complexity
Key Takeaway: Get the “low hanging fruit” first
3/21/2016
Copyright: Mike Ryan
23
Timeboxing
Who remembers “Parkinson’s Law”?
Sprints are a way of “timeboxing” and we
know that “timeboxing” works.
3/21/2016
Copyright: Mike Ryan
24
Burndown Charts
Burndown charts are valuable because
they graphically tell you how much you are
ahead or behind and anyone can
understand them.
Source: Wikipedia
3/21/2016
Copyright: Mike Ryan
25
Cumulative Flow
A Cumulative Flow diagram tells you how
much is Not Started, Started and Completed
Anything else it tells you?
3/21/2016
Copyright: Mike Ryan
26
Why do Agile projects fail?
Causes of Failure
5%
5%
5%
15%
6%
12%
6%
7%
8%
11%
9%
11%
None of our agile projects failed
Don’t know
Lack of experience with agile methods
lack of understanding of broader org change required
Company philosophy or culture at odds with agile values
External pressure for waterfall
New to agile; haven’t completed a project
Lack of mutual trust between business and development
Lack of cultural transition
Insufficient training
Unwillingness of team
Lack of Management support
Source: Version One State of Agile Survey
3/21/2016
Copyright: Mike Ryan
27
Some Pros and Cons of Agile
+
-
Quicker delivery of valuable
functionality
Highly flexible
Regular prioritization
Quicker feedback cycles and
bug identification
Fewer defects in final product
Effective where goals are
“ill defined” or evolving
Highly interactive and
collaborative
3/21/2016
Copyright: Mike Ryan
Hard to predict cost
Time consuming
Requires “culture change”
Requires significant
management support
Does not provide “instant
gratification”
Requires reinforcement not
to fall back to Waterfall.
Documentation may be
incomplete
28
Let’s Finish Up
Let’s check out those Sticky notes and
answer any questions we have not covered.
3/21/2016
Copyright: Mike Ryan
29
Contact Information
Mike Ryan
mikeryan722@hotmail.com
980-267-4509
3/21/2016
Copyright: Mike Ryan
30