Slide 1
Slide 1 text
Agile Doesn't
Have to Stink
Justin Carmony - OpenWest 2015
@JustinCarmony
Slide 2
Slide 2 text
• Director of Development
@ Deseret Digital Media
• Utah PHP Usergroup
President
• I Make (and Break)
Web Stuff (~10 years)
• @JustinCarmony
[email protected]
Hi • Director of Development
@ Deseret Digital Media
• Utah PHP Usergroup
President
• I Make (and Break)
Web Stuff (~10 years)
• @JustinCarmony
[email protected]
Slide 3
Slide 3 text
This
Presentation
• Slides Posted Online
• Feel free to ask on-topic
question during presentation
• Q&A Session At the End
• Feel free to ask me any
questions afterwards
Slide 4
Slide 4 text
• You’ve Heard of Agile
• You Know the Basic Structure
of Scrum
• You’ve tried to do Agile in
some fashion with some team.
Assumptions for this Presentation
Planning
Estimation
2 Week Sprint
Daily Standups
Review & Retrospectives
Slide 5
Slide 5 text
Let’s Take a Poll
Developers? Product Owners? Project Managers?
Scrum Master? Management?
Slide 6
Slide 6 text
I’m A Developer
Slide 7
Slide 7 text
Lets Get This
Out of The Way
Slide 8
Slide 8 text
Agile Sucks!
Slide 9
Slide 9 text
Yes
Slide 10
Slide 10 text
Yes
, It Can
Slide 11
Slide 11 text
Yes, It Can
But It Doesn’t Have To!
Slide 12
Slide 12 text
Lets Talk About
Why
Slide 13
Slide 13 text
ag·ile [aj-uhl, -ahyl]
quick and well-coordinated in movement; lithe: an
agile leap.
active; lively: an agile person.
marked by an ability to think quickly; mentally acute
or aware: She's 95 and still very agile.
1.
2.
3.
Slide 14
Slide 14 text
ag·ile [aj-uhl, -ahyl]
quick and well-coordinated in movement; lithe: an
agile leap.
active; lively: an agile person.
marked by an ability to think quickly; mentally acute
or aware: She's 95 and still very agile.
1.
2.
3.
4. A marketing word for any Development Tool,
Training, or Processes recently released.
Slide 15
Slide 15 text
Terrible Word
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
Who uses Agile Processes?
Slide 19
Slide 19 text
We’re Agile!
Slide 20
Slide 20 text
What does Agile Mean?
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
Actually…
Welll…
Uhhh….
I guess…
Hmm…
Derp…
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
Story Time
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
Project Manager
Work List
Developers
Tickets
Guessing
Hours
Team Meeting
Slide 29
Slide 29 text
Project Manager
Work List
Developers
Tickets
Guessing
Hours
Team Meeting
Product Owner + Scrum Master
Backlog
Scrum Team
Stories
Estimating
Story Points
Sprint Planning
Slide 30
Slide 30 text
No content
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
It Was Frustrating
Slide 34
Slide 34 text
Why Agile?
Slide 35
Slide 35 text
Our Team is More Efficient!
We Do Agile Because…
We Make a Better Product!
We Release On Schedule!
Slide 36
Slide 36 text
Our Team is More Efficient!
We Do Agile Because…
We Make a Better Product!
We Release On Schedule!
Slide 37
Slide 37 text
Fundamentally
Agile is About…
Slide 38
Slide 38 text
Better Decisions
Slide 39
Slide 39 text
Agile Is Not
Just a Process
Slide 40
Slide 40 text
Agile is a Decision
Making Framework
Slide 41
Slide 41 text
Quick Agile Test
Slide 42
Slide 42 text
Have You Changed How You Make
Decisions?
Slide 43
Slide 43 text
• Have you changed how make decisions about:
• What you work on “Today”
• Features, Bugs, & Priorities
• Releases & Deadlines
• Planning for the Future
Decision Making
Slide 44
Slide 44 text
Re-learning Agile
Slide 45
Slide 45 text
Reality In; Decisions Out
R.I.D.O
Slide 46
Slide 46 text
Reality
Slide 47
Slide 47 text
Week 1 Week 2 Week 3 Week 4 Week 5
Week 6 Week 7 Week 8 Week 9 Week 10
Time
Progress
Slide 48
Slide 48 text
Week 1 Week 2 Week 3 Week 4 Week 5
Week 6 Week 7 Week 8 Week 9 Week 10
Time
Work Finished
Slide 49
Slide 49 text
Week 1 Week 2 Week 3 Week 4 Week 5
Week 6 Week 7 Week 8 Week 9 Week 10
Time
Work Finished
Slide 50
Slide 50 text
Week 1 Week 2 Week 3 Week 4 Week 5
Week 6 Week 7 Week 8 Week 9 Week 10
Time
Work Finished
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
Insanity!
Slide 53
Slide 53 text
Goal:
Honest Assessment
of Reality
Slide 54
Slide 54 text
What is Reality?
Things we can Control Things we cannot Control
The Past
Deadlines
Features
Bugs
Feature Scope
Sick & Personal Leave
Work Emergencies
How Long Things Take
???
What To Code
Etc, etc, etc
What to Fix
Actions for Right Now
Re-evaluate Scope
Etc, etc, etc
Etc, etc, etc
Slide 55
Slide 55 text
Decisions
Slide 56
Slide 56 text
Make Decisions that
Manage Risk
Slide 57
Slide 57 text
Complexity
Critical
Slide 58
Slide 58 text
Complexity
Critical
Slide 59
Slide 59 text
Complexity
Critical
Slide 60
Slide 60 text
Complexity
Critical
Slide 61
Slide 61 text
Complexity
Critical
Slide 62
Slide 62 text
Improving Parts
of your Process
Slide 63
Slide 63 text
Team Roles
Slide 64
Slide 64 text
Project
Manager
Owns the Process
Owns the Product
Owns Development
Slide 65
Slide 65 text
Project
Manager
Owns the Process
Owns the Product
Owns Development
Hard to assess reality for all 3 things
Slide 66
Slide 66 text
Scrum
Master
Owns the Process
Owns the Product
Owns Development
Product
Owner
Dev
Lead
Slide 67
Slide 67 text
Scrum
Master
Product
Owner
Dev
Lead
Reality Decisions
Slide 68
Slide 68 text
Share Common Goal
Individual Responsibilities
Slide 69
Slide 69 text
Meetings
Slide 70
Slide 70 text
Meetings Suck!
Slide 71
Slide 71 text
Keep Them Simple!
Keep Them Short!
Slide 72
Slide 72 text
Review
Retro
Estimation
Planning
2.5 Hours
Slide 73
Slide 73 text
Retrospectives
Slide 74
Slide 74 text
MOST IMPORTANT
PART OF OUR PROCESS!
Slide 75
Slide 75 text
1.What went well?
2.What do we want to Change?
3.How are we going to Change It?
Retrospectives
Reality In
Decisions Out
Slide 76
Slide 76 text
Document It!
Slide 77
Slide 77 text
• Added 0 point option to Pivotal for for simple tasks that were falling
in the cracks before.
• More consistent with standups. Starting & ending on time.
• Gathered good feedback from stakeholders
• Having a UI that we can demonstrate with helps communicate to
stakeholders
What Went Well
Slide 78
Slide 78 text
Disrupted several times by AdOps “Emergencies” that could have been
avoided with early communication.
What To Change & How
Problem
Solution
Designate point person (product manager) for all requests to come
through. Proactively coordinate with AdOps before Sprints start.
Slide 79
Slide 79 text
Pivotal & GitHub Notifications are being too noisy in the HipChat Room.
What To Change & How
Problem
Solution
Create new HipChat room for All Notifications and only post critical
notifications in the main room.
Slide 80
Slide 80 text
With Remote Developers visit, we didn’t have enough on boarding work
for new Junior Dev.
What To Change & How
Problem
Solution
Tag “easy” items regularly to have a clean backlog of on boarding tasks.
Slide 81
Slide 81 text
Several DN stories planned had CMS dependencies that weren’t
finished
What To Change & How
Problem
Solution
Use “dependency” label in both DN & CMS backlogs
Review CMS backlog before finalizing each sprint plan
Slide 82
Slide 82 text
Review Your
Retrospective Items!
Slide 83
Slide 83 text
• Safe Communication Environment
• Focus on the Future
• Look for Small, Manageable Changes
• Focus on You before Others - “What can I improve”
Making Retrospectives Effective
Slide 84
Slide 84 text
Estimation
Slide 85
Slide 85 text
It’s Not Precise!
It’s Not Accurate!
Slide 86
Slide 86 text
No content
Slide 87
Slide 87 text
No content
Slide 88
Slide 88 text
No content
Slide 89
Slide 89 text
No content
Slide 90
Slide 90 text
No content
Slide 91
Slide 91 text
Releasing
Slide 92
Slide 92 text
Complexity
Critical
Slide 93
Slide 93 text
Complexity
Critical
Slide 94
Slide 94 text
No content
Slide 95
Slide 95 text
• Don’t Over Analyze for perfect Precision!
• Focus on Identifying Complexities.
• Opportunity for Product Owners & Devs to clear up Ambiguity and
define a more clear scope.
• You will get better over time. There will always be stories that will be
greatly over or under estimated.
Estimation
Reality In Decisions Out
Slide 96
Slide 96 text
No content
Slide 97
Slide 97 text
Planning
Slide 98
Slide 98 text
• Planning goes smoothly when:
• You Product Backlog / Icebox is Well Defined
• Broken into manageable stories & estimated
• End of planning ensure:
• Goals are set and stories are prioritized
• Everyone knows what they will be doing next
Planning
Slide 99
Slide 99 text
Stand Ups
Slide 100
Slide 100 text
• Focus on the spirit of the meeting, not the rules.
• Make sure to identify three areas:
• What happened Previous Day
• What they will work on Today
• Anything Blocking.
• Opportunity for Decisions! Keep an eye on Goals!
Making Stand Ups Effective
Reality In
Decisions Out
Reality In
Slide 101
Slide 101 text
Final Thoughts
Slide 102
Slide 102 text
Everyone Has a Process
Slide 103
Slide 103 text
Be Strategic About It
Slide 104
Slide 104 text
Spirit Over the Rule
Slide 105
Slide 105 text
Always Look for
Ways to Improve
Slide 106
Slide 106 text
Questions?
Slide 107
Slide 107 text
Thank You
Twitter: @JustinCarmony
Email: [email protected]
Web: justincarmony.com
Please Leave Feedback: https://joind.in/10884