Doing Agile in a Waterfall World? Without Breaking Your Neck
Upcoming SlideShare
Loading in...5
×
 

Doing Agile in a Waterfall World? Without Breaking Your Neck

on

  • 201 views

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 ...

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!

Statistics

Views

Total Views
201
Views on SlideShare
197
Embed Views
4

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 4

http://www.stickyminds.com 3
http://beta.stickyminds.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Doing Agile in a Waterfall World? Without Breaking Your Neck Doing Agile in a Waterfall World? Without Breaking Your Neck Document 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 ∙ sqeinfo@sqe.com ∙ 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 Richardson November 2012 1
    • Crossroad flickr.com/photos/nkphillips/2865781749/ 2
    • Trust flickr.com/photos/thomashawk/221827536 3
    • Today's Roadmap Roadmap Project goals Agile practices In context flickr.com/photos/dotbenjamin/2862947932 4
    • Shared Goals Lower defects Faster releases Sustainable process Scalable process Control 5 5
    • Success! Everybody wants to succeed Different ideas 6 6
    • Trust flickr.com/photos/thomashawk/221827536 7
    • Agile Practices Project feedback cycles Team feedback cycles Developer's feedback cycle 8 8
    • Agile Practices Project feedback cycles Team feedback cycles Developer's feedback cycle 9 9
    • Vision/ Initiatives/ Customers Product Owner Retrospective Planning Meeting Demo Iteration (ship event or usable product) Sprint Daily Meetings Daily Meetings 10
    • Workflow Iteration (ship event or usable product) 11 11
    • Waterfall Phases Funding Ramp up Requirements Coding Testing Close 12 12
    • Slow Feedback Ship event (beta? alpha?) 6 to 24 month project 13 13
    • Hybrid 14 14
    • Hybrid Approach Funding Ramp up Agile Execution Close 15 15
    • To Succeed Understand the differences Have clean boundaries Communicate frequently 16 16
    • Product Owners Dual role Subject matter experts Card owner flickr.com/photos/ekai/3804302829/ 17
    • Product Owners ~Project manager Breaking down work Collaborating Dev 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
    • Epics Value Story Cards Product owners create Story Cards Scrum Teams create Task Cards Teams work in iterations 21
    • Two Cards 3x5 card Value 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 units Easier to estimate Easier to complete Easier to understand Agreed on goals 25 25
    • Value Story Card Same as the 3x5 Larger scale Attach $$ 26 26
    • Two Value Story Cards 27 27
    • As a division We want faster loan approvals So that we can increase closings by 10% 28 28
    • As a division We want safer loan approvals So that we can lower defaults by 10% 29 29
    • Who Decides? Upper level management Now have traceability Accountability is a 2 way street 30
    • Value Story Card Story Card Task Card Story Card Task Card Story Card Task Card 31 31
    • Clear Vision Requirements are traceable Beyond 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
    • Short Iterations? Short iterations within the team Deliver outside the team infrequently Not ideal Invite "outsiders" to key demos Send screen captures Actively solicit feedback 36 36
    • Agile Practices Project feedback cycles Team feedback cycles Developer's feedback cycle 37 37
    • Small Teams 5 to 8 Includes dev and QA Pairing or reviews Knowledge sharing Daily meetings flickr.com/photos/bohane/282439297 38
    • Hard Stop Iterations 1 to 4 weeks Fixed length Team commitment Smaller estimates More granular work Hard stop More finish lines flickr.com/photos/donkeyhotey/6503264653 39
    • Clear Results Done or not done? 17 cards accepted 3 done 17% success rate 40 40
    • 1 Month or 1 Year? 30 23 15 8 0 Sprint 1 Sprint 2 Accepted Sprint 3 Sprint 4 Completed 41 41
    • Stand Ups Work done? Problems? Plan to do? (Problems you'll cause) Daily Answer 3 (or 4) questions flickr.com/photos/improveit/1470213987 42
    • Tech Leads Know They hear every day Morale Stuck? Behind Batting 1,000! 43 43
    • Within a Traditional Org? 44 44
    • Smaller Teams Organize your own group Small, self-organizing teams Set and respect short iterations 45 45
    • Big Visible Charts Your cube The hallway Start conversations 30 23 15 8 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 46 46
    • Information radiators 47 47
    • Agile Practices Project feedback cycles Team feedback cycles Developer's feedback cycle 48 48
    • Continuous Integration Watch Code Publish results Build product Run tests 49 49
    • Test Automation Fast feedback Accurate Test first Blitzkrieg Defect Driven 50 50
    • Test Automation Defect Driven Testing Find a bug, add a test Targeted test creation 51
    • Developer's Day Grab a card Write code & tests Check them in Run all tests 52 52
    • Within a Traditional Org? 53 53
    • Test Automation Step 1 Write integration tests Use other team's code Defect driven 54 54
    • Continuous Integration Step 2 Share results Offer to help setup CI Share expertise Share hardware 55 55
    • Rapid Feedback is Addictive 56 56
    • Trust flickr.com/photos/thomashawk/221827536 57
    • Everyone Wants to Win htt p:/ /fli ck r.c om /ph oto s/p ag ina fea /27 89 56 14 88 58 / 58
    • Recognize differences Clear demarcations Set expectations Give 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