• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

big bang delivery to continual value delivery

  • 956 views
Uploaded on

Recent years has seen an emerging new standard in software delivery, with Gartner claiming that over 80% of software development uses some form of agile methodology. Starting by understanding the …

Recent years has seen an emerging new standard in software delivery, with Gartner claiming that over 80% of software development uses some form of agile methodology. Starting by understanding the mega-trends underlying this shift, from the commoditization of software changes, to the proliferation of development frameworks, to the increasing influence the customers of software have on the development lifecycle, we’ll consider the fundamental differences between a long big bang delivery lifecycle and a short incremental value delivery lifecycle, and its impact on information systems, security and controls.

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
956
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
17
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. big bang delivery tocontinual value delivery http://hubblesite.org/news/2009/25
  • 2. emergence of waterfall overshadowed by IIDagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 3. First description ofIterative Development(1968) Brian Randell& F.W. Zurcher“The basic approachrecognizes the futility ofseparating design,evaluation, anddocumentationprocesses in software-system design”agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 4. Iterative & incremental development has a richhistory since the 1950s•1950s - X-15 Hypersonic jet was a milestone 1950s project applying IID•1960s - Project Mercury, the first human spaceflight program in the US•1972 - IBM FSD (Federal Systems Division) working on 1 million+ lines of code for US Trident command system•1977 - FSD incorporated the Trident IID approach with over 2500 engineers as an alternative to waterfallagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 5. Adoption of waterfall driven by Federal mandate•Winston Royce (1970) “Managing the Development of Large Software Systems” became poster child for waterfall•1985 - DoD-Std-2167 - establishes waterfall as the mandatory process for software delivery (by accident)•1994 - Mil-Std-498 - permits both waterfall and IID•2000 - DoD 5000.2 IID is identified as the preferred software delivery approachagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 6. experiencing big bang vs. incremental value deliveryagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 7. Instead of yoga... the Ball Point Game!RULES OF THE GAME...‘Produce’ as many balls as possible in the time allowed › To ‘deliver’ a ball, every person must touch the ball › When you pass the ball, it must have air time › You cannot pass the ball to your neighbour on the right or left › One person has to introduce the balls into the system and the balls have to return to this person in order to be counted e am Gagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
  • 8. First, a big bang approach...RULES OF THE GAME...› To ‘deliver’ a ball, every person ROUND 1 must touch the ball › 3 mins - plan how› When you pass the ball, it must you will work have air time together to ‘deliver’› You cannot pass the ball to your neighbour on the right or left as many balls as you› One person has to introduce the can balls into the system and the balls › 3 mins - execution! have to return to this person in order to be counted e am Gagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
  • 9. Second, an incremental delivery approach...RULES OF THE GAME... ROUND 2› To ‘deliver’ a ball, every person › 1 min - plan how you must touch the ball will work together to› When you pass the ball, it must have air time ‘deliver’ as many› You cannot pass the ball to your balls as you can neighbour on the right or left › 1 min - execution!› One person has to introduce the balls into the system and the balls › rinse & repeat 3 have to return to this person in times order to be counted e am Gagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
  • 10. “At the University of California at Irvine, ...they just planted grass... they waited a year and looked at where adapting vs. defining people had made paths in the grass and built the side walks there.”agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 11. shifting sandsagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 12. Software lines in FORD vehicles over the past 5 years 10 10 7.5 6 x4 5 4.5 3.4 2.8 2.4 2.5 0 2005 2006 2007 2008 2009 2010 Software complexity in FORD vehicles Growing Software quadrupled in 5 years Complexityagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 13. F-22 Raptor 1.7 F-35 Joint Strike 5.7 x1 0 Boeing 787 Dreamliner 6.5 S-Class Daimler 98.6 Compared software complexity growth in Growing Software aerospace and automotive Complexityagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 14. New programming languages and versions released 110 104 88 66 x 10 50 44 41 25 22 11 12 0 1954-1959 1960-1964 1965-1974 1975-1984 1985-1994 1995-2004 Language types and versions released per Increasing Complexity in decade, taken from O’Reilly’s ProgrammingTechnology Environments Language Timeline agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 15. years13.5 3 m on th s 1915 1939 1972 1976 1983 1994 1998 2000 2002 2004 Deepa Chandrasekaran, Gerard J. Tellis - Marshall School of Business, University of Southern California, Los Angeles, California Due to globalization effects, and other economical changes, the time to market over Time to Market time decreased significantlyagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 16. cynefin frameworkagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 17. Complex Complicated Probe Sense Sense Analyze Respond Respond Emergent Good
  • 18.   Practices Disorder Chaotic Simple Act Sense Sense Categorize Respond Respond Novel Best
  • 19.   Practicesagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 20. http://cognitive-edge.comagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 21. http://www.thehubble.net/2011/11/21/noses-for-hire-a-new-kind-of-help/agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 22. unordered problem domains require sensingand probing, not good or best practices http://www.flickr.com/photos/marine_corps/
  • 23. takeawaysagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 24. How do you audit fora capability likecreativity or agility?Role of governance moves fromprogram management (planning)1. Build and assess capability2. Focus on outcomesagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.
  • 25. “Coming together is a beginning. Keeping together is progress. Working together is success.” Henry Ford thank you dave.sharrock@agile42.com skype: dave.sharrock twitter: @davesharrock slides: slideshare.net/davesharrockagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.