Downloaded 50 times
Uploaded byDr. Tathagat Varma
How Fast Can You Deliver An Idea?
The document discusses the advantages of agile methodologies in business, emphasizing rapid iteration and responsiveness to market demands, contrasting this with traditional manufacturing timelines. It outlines the historical evolution of agile and lean practices, highlighting their impact on productivity and project management efficiency. Key insights include the importance of small teams, continuous deployment, and iterative processes as means to achieve higher ROI and better user experiences.
More Related Content
Similar to How Fast Can You Deliver An Idea?
How Fast Can You Deliver An Idea?
- 1. Tathagat Varma http://managewell.net Picture courtesy: http://fm99.com/wp-content/blogs.dir/2/files/2012/12/speed-of-light-620x400.jpg
- 2. Ticket Prices: $2,119- $13,120 69,700 seats => $157m ticket sales TVC $3.8m-$4m for 30s spot 164m viewers - Most Watched in US History Potential worldwide audience of 1 Billion viewers Kickoff 6:30pm EST
- 8. The Speed ofBusiness…
- 9. 6,000 stores, $14.4B in Opened first Net profits opening one a 2012, +17 store in 1975 $2.7B day % y-o-y Agile in Business Conference (c)
- 10. • creativity, qualitydesign • Give customers what they • Every store in the world and rapid turnaround to want receives new models twice adjust to changing market • Get it to them faster than a week demands -- has…generated anyone else • Product reaches European an excellent public stores in 24-36 hours and response to our retailers' rest of the world within 48 collections.” hours. Since 1970s! Design Rules Logistics Agile in Business Conference (c)
- 11. Agile in BusinessConference (c)
- 12. The difference… • Conventionalmanufacturing teams gather requirements, design the solution, build the solution, test the solution, then deliver the solution. In automotive companies, the design portion alone takes 3 to 12 years, and then the vehicle design is built for 5 to 14 years. • WIKISPEED follows the model of Agile software teams…We iterate the entire car every 7 days, meaning that every 7 days we reevaluate each part of the car and reinvent the highest- priority aspects, instead of waiting 8 to 26 years to upgrade.
- 13. Scrum: Clearly Agile: Reducing defined team costs to make roles and changes responsibilities TDD: start with XP: Pairing and failing tests Swarming and develop solutions Lean Software The OOP: contract- Design: Use Wikispeed first less stuff development Process
- 14. Agile in BusinessConference (c) http://www.wikispeed.com/press
- 15. • On ‘gooddays’, Flickr releases a new version every half an hour (Jun 20, 2005) • IMVU pushes a revision of code to the website every nine minutes (Feb 10, 2009) • The other day we passed product release number 25,000 for WordPress. That means we’ve averaged about 16 product releases a day, every day for the last four and a half years! (May 19, 2010) • A new version of Google Chrome now due every six weeks (Jul 22, 2010) • Facebook does code push twice a day (Aug 4, 2012)
- 16. Mister…how soon canyou deliver…???
- 17. 5MB Hard Drive being loadedonto plane via forklift, circa 1956.* *Source not verified
- 18.
- 19.
- 21. What problem arewe trying to solve?
- 22.
- 23.
- 24. What is themost important part in these two machines? “The Brakes!!!” They let you go faster…
- 25.
- 26. Advent of Agileand Lean Methodologies • 1970: Royce critiques Waterfall and offers improvement ideas • 1986: Barry Boehm proposes Spiral Model • 1971: Harlan Mills proposes Incremental Development • 1987: Cleanroom Software engineering • 1991: Sashimi Overlapping Waterfall Model • 1992: Crystal family of methodologies • 1994: DSDM • 1995: Scrum • 1996: Rational Unified Process framework • 1997: Feature Driven Development • 1999: Extreme Programming Explained • 2001: Agile Manifesto is born • 2003: Lean Software Development • 2005: PM Declaration of Interdependence • 2006: Behavior Driven Development • 2007: Kanban-based software engineering • 2008: Lean Startup • 2009: Scrumban • 20xx: Something new !?! (hopefully )
- 29.
- 30. Traditional vs. AgileProject Management Lifecycle http://leadinganswers.typepad.com/leading_answers/2006/09/planning_is_too.html
- 31. Agile Planning Onion Strategy Portfolio Product Release Iteration Daily
- 32.
- 33. Why work withsmall tasks? http://agilescrum.foundationtraining.nl/img/slide-horizon.jpg
- 34. Iterative Estimation Spiral Iterative http://www.sandywalsh.com/2011/04/iterations-and-time-boxing-are-mostly.html
- 37. What is agilereally all about? • Empowered individuals • Collaboration Motivated • Democratic decision-making Individuals and transparency Self- • Shorter feedback cycle organizing x-functional • Manage changing priorities Teams • Increased productivity Agile Businesses • Higher ROI • Faster time to market • Better User Experience
- 38. feedback loop inagile lifecycles
- 39. from daily buildsto project
- 40.
- 41.
- 42. Feedback Loops inTraditional Techniques vs. Agile Techniques
- 43. Agile Development Value Proposition http://www.versionone.com/Agile101/Agile_Benefits.asp
- 44.
- 45.
- 46. are small teamsmore productive? http://drewcrawfordapps.com/2.0/the-agility-of-small-teams/
- 47. does colocation impactteam performance? http://sloanreview.mit.edu/the-magazine/2009-summer/50412/how-to-manage-virtual-teams/
- 48. is small batchsize faster? http://www.andrejkoelewijn.com/wp/2011/06/30/is-team-productivity-a-responsibility-of-the-product-owner/
- 49.
- 50.
- 51. Agile in BusinessConference (c) http://www.slideshare.net/agiledays/linda-rising-the-power-of-an-agile-mindset
- 52. Agile in BusinessConference (c) http://www.slideshare.net/agiledays/linda-rising-the-power-of-an-agile-mindset
- 53. Agile in BusinessConference (c)
- 54. Basics remain thesame!
- 55. What are welearning? • Software development „value stream‟ is highly „inefficient‟ • Lean principles can help identify „wastes‟ • Agile principles can help iterate faster • Kanban allows developing smaller batch size • Continuous Deployment helps deploy small changes periodically • Lean Startup principles help learn faster
- 56. References • http://www.capgemini.com/technology- blog/2011/06/paving-path-scrum-adoption-product-people/ • http://www.sandywalsh.com/2011/04/iterations-and-time- boxing-are-mostly.html • http://www.slideshare.net/jezhumble/adopting-continuous- delivery • http://www.wired.com/underwire/2013/02/oreo-twitter- super-bowl/ • http://www.startuplessonslearned.com/2009/06/why- continuous-deployment.html • http://blog.assembla.com/assemblablog/tabid/12618/bid/92 411/Continuous-Delivery-vs-Continuous-Deployment-vs- Continuous-Integration-Wait-huh.aspx • http://www.slideshare.net/jallspaw/10-deploys-per-day-dev- and-ops-cooperation-at-flickr
- 57. Agile in Healthcare •http://www.cprime.com/blog/2012/07/16/agile-development-in- healthcare-technology-industry/ • https://www.informationweek.com/development/tools/ge- healthcare-goes-agile/228500164 • https://www.ibm.com/developerworks/mydeveloperworks/blogs/c 914709e-8097-4537-92ef- 8982fc416138/entry/agile_in_healthcare_is_possible?lang=en • http://www.softserveinc.com/content/cs/distributed-agile-practice- for-the-healthcare-solution/ • https://ronrammage.wordpress.com/2010/11/06/agile-medical- device-software-development/ • http://www.rallydev.com/toolkits/high-assurance-environments- toolkit • http://www.techwell.com/2012/12/how-agile-impacts-healthcare • http://www.cprime.com/blog/2012/07/16/agile-development-in- healthcare-technology-industry/
- 58.