Post on 20-Aug-2015
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
1
Brian BoelsterliCREOSS Business Solutions
September, 2010
Agile for Business Advantage
Part 1 of 2
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
2
Agenda
•Audience Survey
•Agile Primer
•Agile Benefits
•Agile Challenges
•Summary
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
3
Audience Survey
•Three questions:
1. What software development methodology are you using now?
2. Are you considering moving to Agile method in the future?
3. Why? or why not?
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
4
Agile Primer
http://etutorials.org/Microsoft+Products/Agile+Project+Management+with+Scrum/Chapter+1+Backdrop+The+Science+of+Scrum/Empirical+Process+Control/
Defined Process Control
Empirical Process ControlPredictive/Serial Adaptive/Evolutionary
Requires that every piece of work be completely understood. Given a well-defined set of inputs, the same outputs are generated every time. A defined process can be started and allowed to run until completion, with the same results every time.
Provides and exercises control through transparency,
frequent inspection and adaptation for processes that
are imperfectly defined and generate unpredictable and
unrepeatable outputs.
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
5
Agile Primer“When the process is too complicated for the defined approach, the empirical approach is the appropriate choice”
B.A. Ogunnaike and W.H Ray, Process Dynamics, Modeling and Control
“In the long run, making successful products the first time using empirical process control turns out to be much cheaper than reworking unsuccessful products using defined process control.”
Ken Schwaber, Agile Project Management with Scrum
Empirical Process ControlAdaptive/Evolutionary
Provides and exercises control through transparency,
frequent inspection and adaptation for processes that
are imperfectly defined and generate unpredictable and
unrepeatable outputs.
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
6
Agile Primer
•On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground and of course, to eat. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened
Individuals and interactions over processes and toolsWorking software over comprehensive
documentationCustomer collaboration over contract negotiation
Responding to change over following a plan
The Agile Manifesto
Wow! This was almost 10 years ago!
http://agilemanifesto.org
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
7
Agile PrimerPrinciples of the Agile Manifesto
http://agilemanifesto.org/principles.html
• Highest priority is to satisfy the customer through early and continuous delivery..
• Welcome changing requirements ...
• Deliver working software frequently ...with a preference to the shorter timescale.
• Business people and developers ...work together daily...
• Build projects around motivated individuals ...support they need and trust them to get the job done...
• ............more.....
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
8
Agile Primer
1-Transparency
2-Inspection
3-Adaptation
Empirical
Process Control
Adaptive
Provides and exercises control through transparency,
frequent inspection and adaptation for processes that
are imperfectly defined and generate unpredictable and
unrepeatable outputs.
Principles of the Agile Manifesto
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
9
Agile Primer
• John’s team: Waterfall
• Sequential (Analysis, Design, Construction, Test, Maintenance)
• Documentation centric and contract oriented
• Fragile to change
• “...Some of the things that we learn invalidate our design and we must backtrack.” David Parnas, in A Rational Design Process: How and Why to Fake It
•Sally’s team: Agile
•Adaptive, collaborative, iterative, incremental, architecturally-driven
•Cross-functional teams, highly interactive
•Adaptation, Transparency, Inspection
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
11
Agile Primer•AGILE Methods/Approaches
•Scrum - Ken Schwaber/Jeff Sutherland - focused on agile project management
•Extreme Programming - Kent Beck - focused on agile engineering
•Lean - Mary and Tom Poppendieck - focused on “lean” subculture concepts and Kanban
•Dynamic Systems Method Development- DSDM Consortium/UK - focused on RAD and agile project management
•Others (i.e., Crystal / FDD / RUP / EUP)http://agile.dzone.com/articles/software-development-methodolo
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
12
Agile benefits• Recent SURVEY conducted...
• 1: QSMA (Michael Mah 2008) (http://www.qsma.com/index.shtml)
• Comparison of 26 agile projects to a database of 7500 primarily traditional projects
• 2: David Rico (2008) (http://davidfrico.com/)
• Survey of 51 published academic and research papers
• 3: VersionOne (2008)(www.versionone.com)
• Opt-in online survey of over 3k individuals
• 4: Dr. Dobb’s Journal (2008) (http://www.drdobbs.com)
• Opt-in online survey of over 642 individuals conducted by Scott Amblerhttp://www.succeedingwithagile.com/resources/reported-benefits-of-agile-2
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
13
Agile benefits•Productivity
•Cost
• Job satisfaction
•Time to market
•Quality
•Stakeholder satisfaction
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
14
Benefit: Higher Productivity• Dr. Dobb’s:
• 82% productivity increase
• VersionOne:
• Significantly improved (23% of those surveyed)
• Improved (50% of those surveyed)
More productive
(16% of those
surveyed)
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
15
Benefit: Lower Cost
Rico’s Literature SurveyOther surveyed results
Development Cost
DDJ VersionOne
Improved 32% 30%
Significantly Improved
5% 8%
Lowest Reported Improvement
MedianHighest
Reported Improvement
Productivity 14% 88% 384%
Cost 10% 26% 70%
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
16
Benefit: Increased job Satisfaction •40% of Salesforce.com employees enjoying jobs (BEFORE
adopting Scrum)
•86% of Salesforce.com employees enjoying jobs (15 months AFTER adopting Scrum)
•92% would recommend Agile to others
•Note: According to a University of Calgary research report, 2/3 less overtime in Agile ecosystems
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
17
Benefit: Faster time to market
•VersionOne Study
•65% improvement
•Another 23% significant improvement
•Michael Mah Study
•37% faster568% more value delivered in the
first year of being agile.
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
18
Benefit: Higher quality• Rico Study
• 10% improvement (minimum)
• 63% improvement(median)
• Company trying Agile (Scrum):: ePlan Services
• 70% reduction of defect per 1,000 lines of code (after 9 months)
• Dr. Dobb’s Study
• Somewhat Higher satisfaction (47% of those surveyed)
• Much higher satisfaction (31% of those surveyed)
• VersionOne Study
• 44% improvement
• 24% significant improvement
• Defects
• 10% reduction (84% of those surveyed)
• 25% reduction (30% of those surveyed)
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
19
Benefit: Improved stakeholder satisfaction•Dr. Dobb’s
Study
•Somewhat higher (47% of those surveyed)
•Much higher (31% of those surveyed)
VersionOne Study
ImprovedSignificantly
Improved
Enhanced ability to manage changing priorities
41% 51%
Improved project visibility 42% 41%
Improved alignment of IT and business goals
39% 27%
Reduced project risk 48% 17%
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
20
Agile benefits•Higher Productivity
•Lower cost
• Improved job satisfaction
•Faster time to market
•Higher quality
• Improved stakeholder satisfaction
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
21
Agile challenges• Business/IT Alignment
• Adoption
• Rigor
• Integrating Agile
• Velocity
• Sustainability
Part 2 of 2 presentation will do a deep dive in this....
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
22
Summary• Audience Survey
• We learned about each other and our experiences with Agile
• Agile Primer
• We reviewed Empirical Process Control (transparency, Inspection, adaptation), Agile Manifesto and its principles and how these tie back to Empirical
• Agile Benefits
• We learned about benefits of agile such as higher productivity, lower costs, improved engagement and job satisfaction, faster time to market, higher productivity and stakeholder satisfaction
• Agile Challenges
• We discussed some of the challenges that come with Agile initiatives such as adoption, aligning business imperative with technology objective, rigor (or lack thereof), time management/meeting structures, geographic constraints and training
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
23
Sources• Mike Cohn, Reported Benefits of Agile Development, 2008
• Ambler, Scott. 2008a. Agile adoption rate survey, February. http://www.ambysoft.com/surveys/agileFebruary2008.html.
• Cohn, Mike. 2009. Succeeding with Agile: Software development using Scrum. Addison-Wesley.
• Greene, Steve, and Chris Fry. 2008. Year of living dangerously: How Salesforce.com delivered extraordinary results through a “big bang” enterprise agile revolution. Session presented at Scrum Gathering, Stockholm. http://www.slideshare.net/sgreene/scrum-gathering-2008-stockholm-salesforcecom-presentation.
• Mah, Michael. 2008. How agile projects measure up, and what this means to you. Cutter Consortium Agile Product & Project Management Executive Report 9 (9).
• Mann, Chris, and Frank Maurer. 2005. A case study on the impact of Scrum on overtime and customer satisfaction. In Proceedings of the Agile Development Conference, 70–79. IEEE Computer Society.
• Rico, David F. 2008. What is the ROI of agile vs. traditional methods? An analysis of extreme programming, test-driven development, pair programming, and Scrum (using real options). A downloadable spreadsheet from David Rico’s personal website. http://davidfrico.com/agile-benefits.xls.
• VersionOne. 2008. The state of agile development: Third annual survey. Posted as a downloadable PDF in the Library of White Papers on the VersionOne website. http://www.versionone.com/pdf/3rdAnnualStateOfAgile_FullDataReport.pdf.
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
24
Take aways...•Ask us about our assessment process
•Stay for the afternoon session today we will cover challenges and techniques for addressing these challenges
•ADC and MKS familiar tooling support for implementing Agile with MKS Integrity ALM offering
Copyright 2010, Creoss, LLC. All Rights Reserved. Unauthorized Duplication Prohibited
25
Teaming
•Here is how we are partnered...
•CREOSS Business Solutions - Agile Adoption expertise
•Visit us at www.creoss.com
•Visit our blog at www.agileunplugged.com
•ADC - MKS solutions for CA 2E and CA Plex
•Visit us at www.adcaustin.com