• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile meets waterfall
 

Agile meets waterfall

on

  • 924 views

Rakuten Technology Conference 2011. ...

Rakuten Technology Conference 2011.
By David Ramos and Ilya Solovyev(LinkShare Corporation)

In today's high tech world, the complexity of projects continues to increase rapidly. Many technical organizations continuously ask themselves – what can we do to ensure the highest level of quality within a time-boxed project? When a project faces unforeseen challenges, there's an increased need for creative solutions and a higher level of teamwork. This presentation explores the coexistence of the agile and waterfall methodologies. This may be taboo in the traditional project management organization, however we have proven that it works.

Statistics

Views

Total Views
924
Views on SlideShare
924
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

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

    Agile meets waterfall Agile meets waterfall Presentation Transcript

    • Agile Meets Waterfall Presenters: David Ramos Ilya SolovyevCopyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 0
    • Project ObjectiveTo enable Linkshare to collect and pay VATVAT (Value Added Tax) exclusive to the commissions that Publishers earn, which will enable Linkshare to compete effectively for Publishers in the U.K and European markets. Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 1
    • Project ChallengesComplexity Changes required on 5 production systems Limited legacy documentation Large volume of semi-documented exceptionsTime to Market Compressed project schedule to meet same year revenue targetResources Availability Competing projects Limited number of Subject Matter Experts Steep learning curve to ramp additional resourcesLessons learned from a previousrelated project High volume of bugs Limited test cases and test rounds Inadequate testing environment Limited test data Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 2
    • Solution to Challenges: Agile Meets Waterfall Q2 2011 Q3 2011 Q4 2011Inception Requirements Design Code Test Regression UAT Deploy Close Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 3
    • Project ApproachKey Agile Principles Key Waterfall Principles Large BatchesSmall Batches Typical delivery schedule is two or three times a year.Functionality is developed in short iterations of 1-4 weeks, andreleased into production frequently, as often as weekly.Responding To Change Baseline and Change ControlAcknowledge uncertainty, and adapt to both external (market) Typically constrain, or even completely eliminate anyand internal changes, by modifying plans and approach. Use significant change other than dropping features. Work to initialengineering principles to make code base easy to modify. plans, even when they are proven to be invalid.Iteration & Continuous ImprovementRetrospectives at the end of each iteration allows teams to Lessons Learned at the Endreflect, learn and continually improve by continually adapting. Negative feedback is rarely if ever given, and often too late to avoid significant project consequences.Small, Integrated Teams Silo Teams with HandoffsSmall team size and complementary overlap in skill sets Staff works in functional oriented groups, throwingsimplifies communications, allows everyone to see the big documentation and code over the wall.picture, creates self discipline and provide flexibility. All or NothingFocus on Highest Value First Tight coupling, and a bias toward building out the internals inAlign project, product and team visions a breadth first fashion, means that nothing can be delivered inby prioritizing by business needs, and using well-architectured isolation, even if it’s valuable.code, to deliver better quality products faster and cheaper. Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 4
    • Team StructureRole Agile WaterfallProduct OwnerProject ManagerTechnicalFunctionalManagerRequirementsManagerTechnical LeadSoftwareDevelopersQA LeadQA Engineers Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 5
    • Development Approach• Agile for Development and Test • Daily ½ hour meeting • Three 1-week sprints• Assignments to sprint backlog tasks • Dependent on developer’s expertise• The team was self-organized • Found the best architecture and code design approaches during weekly sprints Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 6
    • Test Approach• Test development first – from unit testing to demo• Test Environment LinkShare Wiki – 60% performance improvement• Test Data• Created WIKI page – result of existing unit tests• Sprint QA testing Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 7
    • Project OutcomesLargest Related Code Release since Q4 2010 – Code Reviews – Early Testing + Testing with Recent Data – Multiple Rounds of UAT Lessons Out Box Team Project Learned Thinking Work Success Post Release Bugs Pre Release Bugs Days to First Invoice 111 329 29 4 26 2 Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 8
    • Agile ChallengesBacklog• It can grow to a size where it’s difficult to groom or prioritize in any reasonable amount of timeDocumentation• It often gets out prioritizedStaffing• Some resist to co-locate• Estimating complex stories can be difficult to less experienced team members. Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 9
    • ConclusionAgile + Waterfall – Can co-exist – Helps produce the highest quality product – Helps achieve milestones and adhere to timelines Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 10
    • Next Steps• 2012 Product Roadmap• Adapt this new approach to complex and time sensitive projects• Example: Global SAP Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 11
    • Next Steps – Global SAP Rollout 2012 • Multiple Concurrent ProjectsCurrently Underway • 2 Week Dev Sprints Agile • Quick response to change • Waterfall UAT and Regression Legacy System Integration Phase 1 LinkShare Rollout Global SAP Waterfall • Single Waterfall Project • Strict Change Control • All or Nothing Copyright 2011 LinkShare Corporation. All rights reserved. CONFIDENTIAL: FOR INTERNAL DISTRIBUTION ONLY 12