This session will have something for everyone. For the person new to Agile Development, this will provide a basic knowledge to distinguish Agile development from traditional Waterfall development. For those that have some knowledge, this will provide some practical examples and stories about what is happening in the “real world”.
We are in tough financial times, and are being ask to do more than ever with less people. Faster, better, and cheaper is the new mantra for organizations. Companies that will survive and endure for the long haul are looking for different and better ways to deliver software and are discovering Agile development as a possible answer. How do you get started with Agile practices? What are some lessons learned that I can watch out for as we get started? What will Agile fix
and what will it expose? In this session, these questions and others will be answered.
We will also explore how Agile development came to be and provide a foundational knowledge of the common practices including the Scrum framework and Extreme Programming (XP).
5. "If you keep on doing what you've always done… you'll keep on getting what you've always got."
6.
7.
8.
9.
10.
11.
12.
13. Empirical Process Control “ It is typical to adopt the defined (theoretical) modeling approach when the underlying mechanisms by which a process operates are reasonably well understood. When the process is too complicated for the defined approach, the empirical approach is the appropriate choice.” Process Dynamics, Modeling and Control , Ogunnaike and Ray, Oxford University Press, 1992 Empirical Process Control uses Inspection and Adaptation
15. Why Agile? Constraints Estimates Features Schedule Cost Plan Driven The Plan creates cost/schedule estimates Waterfall Source: Michelle Sliger in “Relating PMBOK Practices to Agile Practices” The Vision creates feature estimates Schedule Cost Features Value / Vision Driven Agile
30. Product Engineering – Then & Now Collaboration Innovation Releases Feedback Customers Process Architecture Culture Testing Tools
31.
32. 1/4 Of Enterprises Currently Use Agile Processes, And Nearly 1/2 Of Remaining Are Aware Of Agile Source: Enterprise And SMB Software Survey, North America And Europe, Q3 2007 Base: 1,017 North American and European enterprises “ How familiar are you with Agile software development processes?”
33. Agile Adoption Increased 53% Year-Over-Year Between 2006 And 2007 *Source: Business Technographics ® November 2005 North American And European Enterprise Software And Services Survey † Source: Business Technographics September 2006 North American And European Enterprise Software Survey ‡ Source: Enterprise And SMB Software Survey, North America And Europe, Q3 2007 *Base: 911 North American and European enterprises † Base: 1,057 North American and European enterprises ‡ Base: 1,002 North American and European enterprises “ How familiar are you with Agile software development processes?”
34. Industries Using Agile Practices Source: Enterprise And SMB Software Survey, North America And Europe, Q3 2007 Base: 1,017 North American and European enterprises (percentages may not total 100 due to rounding) “ How familiar are you with Agile software development processes?”
35.
36. Delivering Value Early With Less Risk Traditional vs. Agile Software Delivery Traditional Scrum Risk Project Run Rate Cumulative Value Risk Cumulative Value Project Run Rate Halt project when desired value is reached Start with high-risk, high-value items to drive down risk and maximize ROI
41. Agile Is Pervasive Change Old Organization New Organization Centralized Distributed Unified perspective Diversified perspective Declared meaning Emergent meaning Analytical Creative Analysis leads to action Learning by doing Certain Uncertain Strategy concept Local action Authoritative Participative Authoritative; Hierarchical Shared Leadership