The Dancing Agile Elephant

1,984 views
1,899 views

Published on

Sue Mckinney's March 11 presentation in Agile Austin

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,984
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
75
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • The Dancing Agile Elephant

    1. 1. “ The Dancing Agile Elephant” Sue McKinney Vice President, Development Transformation IBM Software Group [email_address] <ul><ul><li>IBM Software Group’s Transition to Agile and Lean Development </li></ul></ul>
    2. 2. Agenda… 1 Software Group Dynamics 2 The “How” 3 Sustainability 4 Summary
    3. 3. Software Group Dynamics
    4. 4. Business and Operational Dynamics <ul><li>Innovating the business to differentiate and capture new value </li></ul><ul><li>Heighten responsiveness and closer linkage to our customers </li></ul><ul><li>Improve Time to Value </li></ul><ul><li>Better workload management </li></ul><ul><li>Improve Quality </li></ul><ul><li>Improve project development cycle times </li></ul><ul><li>Improve predictability on schedule </li></ul><ul><li>Making better use of resources to be more productive </li></ul>
    5. 5. A Global Team of IBM Software Group Developers Canada Toronto,Ottawa Montreal, Victoria Edinburgh London / Staines Milton Keynes Haifa Rehovot China Beijing Shanghai Yamato Taiwan Paris Pornichet Beaverton Kirkland Seattle Foster City San Francisco SVL/San Jose Almaden Agoura Hills Irving El Segundo Costa Mesa Las Vegas Andover Bedford, MA Bedford, NH Lexington Westborough Westford Cambridge Cork Dublin Galway India Bangalore Pune Hyderabad Gurgaon Cairo Rome Gold Coast Sydney Canberra Fairfax Raleigh Charlotte Lexington, KY Atlanta Boca Raton Tampa Perth Krakow Warsaw Sao Paulo Malaysia Delft Stockholm Pittsburgh Poughkeepsie Somers Rochester, MN Boulder Denver Lenexa, KA Tucson Phoenix Austin Dallas Boeblingen Hursley Warwick York Southbury New York City Princeton US Canada Latin America EMEA AP Total 11,000 3,500 100 3,900 6,600 25,100
    6. 6. Software Group Acquisition Milestones
    7. 7. WATERFALL <ul><li>Waterfall development </li></ul><ul><ul><li>Rigid, late feedback, slow reaction to market changes </li></ul></ul><ul><li>Iterative development </li></ul><ul><ul><li>Customized RUP, community source and component reuse, emphasis on consumability </li></ul></ul>1980’s 1990’s Present Rigid Continuous Learning and Adaptive Planning <ul><li>Agile / Lean development </li></ul><ul><ul><li>Global reach, SOA, agile practices, outside-in development, tools and not rules </li></ul></ul>IBM Software Development Transformation AGILE ITERATIVE
    8. 8. Diversity and Complexity Requires Teams to be More Effective and Adaptive <ul><li>New project </li></ul><ul><li>Small team </li></ul><ul><li>Simple application </li></ul><ul><li>Co-located </li></ul><ul><li>Minimal need for documentation </li></ul><ul><li>Maturing projects </li></ul><ul><li>Multi-platform </li></ul><ul><li>Growing in complexity </li></ul><ul><li>Remote or offshore work </li></ul><ul><li>Greater need for coordination & handoffs </li></ul><ul><li>Mature projects </li></ul><ul><li>Complex, multi-platform applications </li></ul><ul><li>Distributed teams </li></ul><ul><li>Need for scalability, reproducibility, and traceability </li></ul>Organizational Drivers Team Size Geographical Distribution Organizational Distribution Entrenched process, people, policy Technical and Regulatory Drivers Compliance Governance Application complexity Agility at Scale “ Incremental to deal with uncertainty” “ Process to deal with complexity”
    9. 9. The “How” Do not attempt this at home. All stunts performed by semi-professional SWG executives. No animals were used in this experiment.
    10. 10. Things to Consider before getting Started <ul><li>Management Support </li></ul><ul><li>Strong and Experienced Leader(s) </li></ul><ul><li>Picking the right project as a proof point </li></ul><ul><li>Providing the right education, tooling and governance </li></ul><ul><li>Ability to allow change to occur </li></ul><ul><li>Keep it Simple </li></ul>
    11. 11. Manifesto for Agile Software Development “ 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.” See www.agilealliance.org
    12. 12. 2007 Agile Deployment Approach <ul><li>Short, Time-boxed Iterations with Stakeholder Feedback </li></ul>
    13. 13. Short, Time-boxed Iterations Create …….. <ul><li>Automatic Constraints </li></ul>Transparency Find Defects Earlier Being More Responsive
    14. 14. Constraints Cause Us To …….. Eliminate Waste Optimize and Become More Effective
    15. 15. Stakeholder Feedback Causes Us…….. <ul><li>To Focus on the Essentials </li></ul>
    16. 16. Sametime Development Approach… <ul><li>Agile Process </li></ul><ul><ul><li>Employed frequent / short code iterations; published builds for regular consumption </li></ul></ul><ul><ul><li>Organized around features crews for increased code sharing and reviews </li></ul></ul><ul><ul><li>Employed use of light-weight UI specs and implementations outlines </li></ul></ul><ul><li>Closed gap between developers and end users </li></ul><ul><ul><li>Combined Teams from across WPLC, CIO Office and Research </li></ul></ul><ul><ul><li>Used TAP program for posting weekly builds; </li></ul></ul><ul><ul><li>Fostered community of contribution and collaboration; Inspired expanded participation from over 40,000 IBM’ers; plus energized product developers! </li></ul></ul><ul><ul><li>Produced public beta (multiple builds) for over 100+ external customers; led to increased product acceptance and accelerated roll outs </li></ul></ul><ul><li>Engineering practices </li></ul><ul><ul><li>Continuous prototyping of code deliverables </li></ul></ul><ul><ul><li>Frequent code reviews; automated static code analysis </li></ul></ul><ul><ul><li>Aggressively eliminated unnecessary work! </li></ul></ul>
    17. 17. Sustainability
    18. 18. Best Practices for Distributed Development <ul><li>Architecture Blueprint </li></ul><ul><li>Outside-in Development </li></ul><ul><li>Agile / Lean approaches </li></ul><ul><li>Modeling and Componentization </li></ul><ul><li>Fostering Communities and sharing Best Practices </li></ul><ul><li>Discipline, adaptive development approaches </li></ul><ul><li>Continuous stakeholder feedback to understand changing needs </li></ul><ul><li>Time-boxed iterations </li></ul><ul><li>Eliminate waste, increase visibility </li></ul><ul><li>Tools, not Rules </li></ul><ul><li>Community source </li></ul><ul><li>Shared asset repository </li></ul><ul><li>Best practices </li></ul><ul><li>Common components </li></ul><ul><li>Clearing House for dependency management </li></ul><ul><li>Educate, Enable and Empower </li></ul><ul><li>Lightweight central governance mechanisms </li></ul><ul><li>Development Steering Committee </li></ul><ul><li>Architectural Board </li></ul><ul><li>Culture of sharing and reuse </li></ul><ul><li>Developer Web site </li></ul><ul><li>Centralized development services </li></ul>Sound Development Governance Principles Enable for Success Execute Agile / Lean for Productivity Guiding Principles for Software Development + + =
    19. 19. Educate, Enable and Empower <ul><li>“Disciplined Agile” Workshops : </li></ul><ul><ul><li>150 workshops completed </li></ul></ul><ul><ul><li>Over 7,000 attendees </li></ul></ul><ul><li>Workshop has also been videotaped </li></ul>Existing On-line Resources Coaches Available Questions Answered Main Wiki Case Studies Contacts and Collateral:
    20. 20. Summary
    21. 21. In Summary …… <ul><li>Challenges </li></ul><ul><ul><li>Very geographically dispersed teams with different approaches to building software </li></ul></ul><ul><ul><li>Many projects, often large teams </li></ul></ul><ul><ul><li>Innovating the business to differentiate and capture new value. </li></ul></ul><ul><ul><li>Making better use of resources to be more productive. </li></ul></ul><ul><ul><li>Avoiding the trough of disillusionment </li></ul></ul><ul><li>Solution Approaches </li></ul><ul><ul><li>Continuously transform development using new techniques, and tools </li></ul></ul><ul><ul><li>Enable and empower teams </li></ul></ul><ul><ul><li>Collaborate more effectively at larger scales, both internally and externally and share knowledge, assets and best practices </li></ul></ul>
    22. 22. Sue McKinney [email_address] Thank You! Acknowledgement and Thanks to: Mary and Tom Poppendieck Pollyanna Pixton

    ×