INTRO TO AGILE PRESENTED BY
AGENDA Introduction Agile Overview Why Agile? Agile Principles and Framework Overview Agile Benefits Questions
INTRODUCTION Steve Davis 18 years working with software development and implementation teams from Fortune 50 to startup. 7+ years working with software development teams and executives implementing Agile practices Certified Scrum Practitioner
WHY AGILE? IT Project Success Failed Challenged Succeeded 2009 24% 44% 32% 2006 2004 19% 15% 46% 51% 35% 34% Average Cost Overrun = 45% Average Time Overrun = 63% Average Missed Functionality = 33% Source: The Standish Group, 2004, 2006, 2009
WHY AGILE? Traditional project management methods are rooted in Construction and Manufacturing. Consistent Projects Proven Methods Tangible & Immediate results Software is different: Schedule Timetable for creating the deliverables Scope Feature/functionality deliverables for the project Inconsistent projects Volatility in technology and market conditions Inherently intangible - No value realized until complete Cost People, materials, and equipment used to create the deliverables
WHY AGILE? 1. Manage rapidly changing priorities 2. Increase Productivity 3. Improve Quality 4. Accelerate time to market VersionOne/AgileAlliance Survey, August 2006
PARADIGM CHANGE Features Fixed Date Cost Traditional Agile Date Cost Flexible Features
AGILE IS A philosophy about software development A collection of processes and practices that uphold that philosophy An increasingly mainstreamed and proven framework for repeatably and predictably delivering working and valuable software projects
AGILE MANIFESTO We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
AGILE PRINCIPLES Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
AGILE PRINCIPLES Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from selforganizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Incremental and Iterative AGILE APPROACH Continuous planning - always accurate, varying levels of precision Evolving requirements over time through constant collaboration with the customer/market Realizing business value by frequently delivering working software - The right features at the right time. Team-based Cross-functional teams, empowered to make the decisions required to get the job done. Succeed or fail as a team. Respect for team commitments drive individual accountability. Predictable, Repeatable, Sustainable and Transparent Consistent, collaborative communication Technical excellence (TDD, Continuous Integration) Continuous improvement through regular inspection and adaptation
5 LEVELS OF AGILE PLANNING Plans are useless... Planning is indispensable - Eisenhower Vision Roadmap Release Iteration Daily Yearly by the Customer Unit Semiannually by the Customer Unit Quarterly by the Customer and Developer Units Bi-weekly or monthly by the Developer Unit Daily by the Developer Unit
PROCESS OVERVIEW Vision Prioritization Estimating Product Backlog Product Themes Velocity Roadmap Release Plan Release Plan Collaborating Details Iteration Iteration Plans Iteration Plans Plans Requirements Customer Developer Daily Dai;y Daily Daily Daily
AGILE BENEFITS
AGILE BENEFITS 33% 67% 67% of organizations find that Agile has improved the frequency of their product releases. May 2009 - Forrester Research 74% of organizations report that Agile practices have resulted in increased productivity. 2008 State of Agile - VersionOne 26% 74% 66% 34% 66% of organizations have found reductions in cost greater or equal to 10% 2008 State of Agile - VersionOne 83% 17% 57% of organizations report improvements in execution capabilities due to increased company wide collaboration. May 2009 - Forrester Research 57% 43% 83% of organizations attribute improved transparency and project level visibility to their Agile practices 2008 State of Agile - VersionOne
ABOUT DAVISBASE A leading, national provider of Agile training and coaching services. Since 2007, over 200 classes taught to over 3000 people nationwide. Training, coaching and consulting work for over 50 Fortune 500 Clients. Experienced; in the trenches doing what we teach Extensive experience with all aspects of software development and project lifecycle across multiple industries and verticals. Every title and role from Developer, QA, Project Manager through Sr. Leadership. Average of 12+ years of applied IT Leadership experience.
THANK YOU QUESTIONS steve@davisbase.org