Presentation is loading. Please wait.

Presentation is loading. Please wait.

SCRUM in a waterfall Thilo Fromm, DResearch GmbH.

Similar presentations


Presentation on theme: "SCRUM in a waterfall Thilo Fromm, DResearch GmbH."— Presentation transcript:

1 SCRUM in a waterfall Thilo Fromm, DResearch GmbH

2 Agenda The Waterfall Process General concept and DResearch's Implementation Agile Development A quick review Best of both worlds Making it all work together

3 Motivation Introduction of Agile Methods in a traditional Waterfall process environment Fast-changing requirements No appropriate procedure (rapid, reliable, documented)‏

4 Our Business Mobile DVRs for security applications Public Transport Sector Whole Products, Product Lines ISO

5 The Waterfall Process Traditional approach for systems design Big Design Up Front (BDUF)‏ Widespread use Certification friendly

6 The Waterfall Process Requirements System Design Implementation Verification Maintenance

7 Waterfall Process - DResearch System Design Implementation Verification Maintenance Requirements Lastenheft Pflichtenheft

8 Waterfall Process - DResearch Implementation Verification Maintenance System Design Design Specs Requirements Lastenheft Pflichtenheft

9 Waterfall Process - DResearch Verification Maintenance Implementation Functional Milestones Requirements System Design Lastenheft Pflichtenheft Design Specs

10 Waterfall Process - DResearch Maintenance Verification Requirements System Design Implementation Lastenheft Pflichtenheft Design Specs Functional Milestones Test Specs + Milestones, Bugfixing, Release Tests

11 Waterfall Process - DResearch Requirements System Design Verification Maintenance Lastenheft Pflichtenheft Design Specs Functional Milestones Feature Request, Change Request tracking Implementation Test Specs + Milestones, Bugfixing, Release Tests

12 DResearch roles and parties Project Lead Sales Product Manager Test Lab Reqirements Project Engineers Tenders, Customers

13 DResearch roles and parties Project Lead Product Manager Test Lab Reqirements Project Engineers Features Tasks Sales Tenders, Customers

14 DResearch roles and parties Project Lead Product Manager Test Lab Reqirements Release Project Engineers Features Tasks Sales Tenders, Customers

15 DResearch roles and parties Project Lead Product Manager Test Lab Reqirements Release Project Engineers Products Features Tasks Release Sales Tenders, Customers

16 Implementation - DResearch Milestone #1: ”Recording” Milestone #2: ”Configuration” Milestone #3: ”Live View” Milestone #4: ”Image Search”... Project Lead Project Engineers

17 Verification - DResearch Milestone #V1: Integration Test Milestone #V2: System Test Release Milestone #V3: Bugfixing... Release Project Lead Test Lab Project Engineers

18 Verification (contd.) - DResearch Milestone #V4: System Test II Milestone #V6: Release Test Milestone #V5: Bugfixing II... Release Project Lead Project Engineers Test Lab Product Manager

19 Waterfall PROs Structured, step-by-step approach ”You get what you ordered” Documented prior to development Long term plannable Cost, time, Features are fixed

20 Waterfall CONs Requires throughout Requirement / Design Customer communication issues ”Ivory Tower” designs Incredibly long round-trip times Development set for months Slow reaction to requirement / market changes Release when project ends No explicit rethinking, no reflection

21 SCRUM / Agile Methods Development phase centered approach Work in small steps Verify / test everything you do Design as you go Release early, release often ™

22 SCRUM / Agile Methods User Stories Feature #1... Feature #2... Feature #

23 SCRUM / Agile Methods User Stories Feature #1... Feature #2... Feature # Sprint Backlog F1: Task #1... F1: Task #2... F2: Task #1... F2: Task #2... F2: Task #3... F3: Task # Weeks

24 SCRUM / Agile Methods User Stories Feature #1... Feature #2... Feature # Sprint Backlog F1: Task #1... F1: Task #2... F2: Task #1... F2: Task #2... F2: Task #3... F3: Task # Daily F1: Task #1 => D #1 F2: Task #3 => D #2 F3: Task #1 => D # Weeks One Day

25 Agile PROs Highly flexible approach Optimize for TTM, cost, or personnel available as you go ”You get what you need most” Built-in rethinking, reflection

26 Agile CONs Global concept not part of the process Global design relies on Master and Owner Unbalanced end products ”Mad cow featuritia” Depends on Customer behaviour C. must be willing to participate in design C. must be available

27 Joining Methodologies Waterfall advantages Structured, plannable approach Big picture is communicated and documented Agile advantages Flexible in features, cost, TTM, personnel Focus on market value Early releases

28 Joining Methodologies Requirements Design

29 Joining Methodologies Lightweight Requirements Design Lastenheft Pflichtenheft

30 Joining Methodologies Lightweight Design Lastenheft Pflichtenheft Lightweight Requirements Design Specs (where necessary)‏

31 Joining Methodologies Lightweight Design Lastenheft Pflichtenheft Design Specs (where necessary)‏ Lightweight Requirements

32 Implementation / Verification Sprint #1 Lead, Engineers Product Manager

33 Implementation / Verification Sprint #1 Test #1Sprint #2 Release Test Lab Sprint #1 Lead, Engineers Product Manager

34 Implementation / Verification Sprint #1 Test #1Sprint #2 Sprint #3Test #2 Test #3Stabilisation Release Sprint #1 Test Lab Lead, Engineers Product Manager

35 Implementation / Verification Sprint #1 Test #1Sprint #2 Sprint #3Test #2 Test #3Stabilisation Release Release Test (?)‏ Test Lab Product Manager Release Lead, Engineers

36 Lessons learned Waterfall / Agile try to solve different problems Both are appropriate for their problem class Don't decide for one, take the best of both Eliminate deficiencies of both methods along the way ”If you think Agile / Waterfall will solve your problems, then you don't understand Agile / Waterfall, and you don't understand your problems.”

37 Q&A // Commitments ”The changes introduced enable coordinated response to customer requirements and enhance strategic marketing flexibility. We received Declarations of Satisfaction from several customers.” Peter Schüßler, Product Manager ”Due to the very positive experience we made by introducing Sprints into the Waterfall process we will continue to apply this novel model to this year's upcoming projects.” Frank Bauernöppel, Head of Product Development

38 Q&A // Commitments cont'd. ”From a Controller's perspective I still mourn the days where a project had time, cost and features set fix before development even started. Calculating and reporting progress was an easy and controller-friendly task back then.” However, introducting agile principles into DResearch processes enabled us to process projects wich featured rapidly changing requirements, varying feature priorities and time critical release constraints with much more customer satisfaction than the Waterfall method could provide. As for our motto being customer satisfaction, not controller's satisfaction, I cannot help but support the future use of Agile Principles at DResearch ;-)” Susanne Bärsch, Head of Testing / Controlling

39 Thanks!

40 © Copyright © This presentation is released under the terms of the GNU Free Documentation License, version 1.2, or later, as described in

41 List of Sources Title image: Purakaunui.jpg by James Dignan, © GNU FDL, from


Download ppt "SCRUM in a waterfall Thilo Fromm, DResearch GmbH."

Similar presentations


Ads by Google