doing agile in a waterfall world? without breaking your neck
DESCRIPTION
Although many of us want to use only agile practices, we often work alongside teams with strong waterfall traditions. If you’ve had trouble finding ways for your agile ideas to co-exist peacefully with traditional lifecycles, this session is for you. Jared Richardson describes key integration points between waterfall and agile teams, and demonstrates the best ways to work together-or to perform clean hand-offs, if necessary. He shows how to use adaptive planning while still providing accurate progress status to traditional PMO counterparts. Jared reviews popular agile practices and discusses how they best function in a hybrid environment. Together, you and Jared will build a common vocabulary, examine two project models-one traditional and one agile, and then combine them in a hybrid that keeps the best of both worlds. Leave knowing how to link a traditional project's large, coarse-grained goals to an individual story in a short iteration-without breaking your neck on waterfall!TRANSCRIPT
AT2 Concurrent Session 11/8/2012 10:15 AM
"Doing Agile in a Waterfall World? Without Breaking Your Neck"
Presented by:
Jared Richardson RoleModel Software
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073 888‐268‐8770 ∙ 904‐278‐0524 ∙ [email protected] ∙ www.sqe.com
Jared Richardson RoleModel Software
Principal consultant and a member of the core team at RoleModel Software, Jared Richardson works with other software craftsmen to build excellent custom software. He sold his first software program in 1991 and has been immersed in software ever since. Jared has authored and coauthored a number of books, including the best selling Ship It! A Practical Guide to Successful Software Projects and Career 2.0: Take Control of Your Life. He is a frequent speaker at software conferences and a thought leader in the agile space. Jared lives with his wife and children in North Carolina where they recently, quite by accident, became backyard chicken farmers. He's on the web at AgileArtisans.com and RoleModelSoftware.com.
Doing Agile in a Waterfall World
Without Breaking Your Neck
by Jared RichardsonNovember 2012
1
Crossroad
flickr.com/photos/nkphillips/2865781749/
2
Trust
flickr.com/photos/thomashawk/2218275363
Roadmap
flickr.com/photos/dotbenjamin/2862947932
Today'sRoadmap
Project goalsAgile practicesIn context
4
Shared Goals
Lower defectsFaster releasesSustainable processScalable processControl
5
5
Success!
Everybody wants to succeedDifferent ideas
6
6
Trust
flickr.com/photos/thomashawk/221827536
7
Agile Practices
Project feedback cyclesTeam feedback cyclesDeveloper's feedback cycle
8
8
Agile Practices
Project feedback cyclesTeam feedback cyclesDeveloper's feedback cycle
9
9
Sprint
Iteration(ship eventor usableproduct)
Vision/Initiatives/Customers
Retrospective
Demo
Planning Meeting
ProductOwner
DailyMeetings Daily
Meetings
10
11
Iteration(ship eventor usableproduct)
Workflow
11
Waterfall Phases
12
Funding Ramp up CloseRequirements Coding Testing
12
Slow Feedback
13
Ship event(beta? alpha?)
6 to 24 month project
13
Hybrid
14
14
Hybrid Approach
15
Funding Ramp up CloseAgile Execution
15
To Succeed
Understand the differences
Have clean boundaries
Communicate frequently
16
16
Product Owners
Dual roleSubject matter expertsCard owner
flickr.com/photos/ekai/3804302829/
17
Product Owners
~Project managerBreaking down workCollaboratingDev Team"Customers"
flickr.com/photos/ekai/3804302829/
18
Translate from big picture to a daily task?
19
19
Travel Time Quiz
New York to LA?Home to work?Closest bathroom?
20
20
EpicsValue Story Cards Product owners create Story Cards Scrum Teams create Task Cards Teams work in iterations
21
Two Cards
3x5 cardValue Story Card
22
22
3x5 Card
As a <role>
I want <feature>
So that <motivation>
23
23
3x5 Card (back)
Done?
Acceptance criteria
24
24
Motivations
Work in smaller unitsEasier to estimateEasier to completeEasier to understandAgreed on goals
25
25
Value Story Card
Same as the 3x5Larger scaleAttach $$
26
26
Two Value Story Cards
27
27
As a divisionWe want faster loan approvals
So that we can increase closings by 10%
28
28
As a divisionWe want safer loan approvalsSo that we can lower defaults
by 10%
29
29
Who Decides?
Upper level managementNow have traceability
Accountability is a 2 way street
30
31
Value Story Card
Story Card Story Card Story Card
Task Card Task Card Task Card
31
Clear Vision
Requirements are traceableBeyond mission statements
Translation
32
32
Within a Traditional Org?
33
33
Cards
Write your own"How do these look?"
Want to make a friend?
34
34
A Tool
Start conversations
35
35
36
Short Iterations?Short iterations within the team
Deliver outside the team infrequentlyNot ideal
Invite "outsiders" to key demosSend screen captures
Actively solicit feedback
36
Agile Practices
Project feedback cyclesTeam feedback cyclesDeveloper's feedback cycle
37
37
Small Teams
5 to 8Includes dev and QAPairing or reviewsKnowledge sharingDaily meetings
flickr.com/photos/bohane/282439297
38
Hard Stop Iterations
1 to 4 weeksFixed lengthTeam commitmentSmaller estimatesMore granular workHard stopMore finish lines
flickr.com/photos/donkeyhotey/6503264653
39
Clear Results
40
Done or not done?17 cards accepted
3 done17% success rate
40
41
0
8
15
23
30
Sprint 1 Sprint 2 Sprint 3 Sprint 4
Accepted Completed
1 Month or 1 Year?
41
Work done?Stand Ups
DailyAnswer 3 (or 4) questions
flickr.com/photos/improveit/1470213987
Problems?Plan to do?(Problems you'll cause)
42
Tech Leads Know
They hear every dayMoraleStuck?BehindBatting 1,000!
43
43
Within a Traditional Org?
44
44
Smaller Teams
Organize your own groupSmall, self-organizing teams
Set and respect short iterations
45
45
Big Visible ChartsYour cubeThe hallwayStart conversations
46
0
8
15
23
30
Sprint 1 Sprint 2 Sprint 3 Sprint 446
Information radiators
47
47
Agile Practices
Project feedback cyclesTeam feedback cyclesDeveloper's feedback cycle
48
48
Continuous Integration
49
Watch Code
Build product
Run tests
Publish results
49
Test AutomationFast feedbackAccurateTest firstBlitzkriegDefect Driven
50
50
Test Automation
Defect Driven TestingFind a bug, add a testTargeted test creation
51
Developer's Day
52
Grab a card
Write code & tests
Run all tests
Check them in
52
Within a Traditional Org?
53
53
Test Automation
Step 1Write integration testsUse other team's code
Defect driven
54
54
Continuous Integration
Step 2Share results
Offer to help setup CIShare expertiseShare hardware
55
55
Rapid Feedback is Addictive
56
56
Trust
flickr.com/photos/thomashawk/22182753657
Everyone Wants to Win
58
http://flickr.com/photos/paginafea/2789561488/
58
Recognize differencesClear demarcations
Set expectationsGive new techniques a chance
Keep what works
59
59
You Drive the Change
Bring ideas
Be patient
Change the game
flickr.com/photos/vodcars/4132650949
60
61
We turn innovative ideas into reality
62