Agile Comes to You (Mironov, Bellevue)

1,815 views

Published on

Rich Mironov's keynote for one-day agile workshop. Intro to agile development and agile organizations, tools, impact on whole organization, product management and product planning. Co-sponsored by AccuRev, Coverity, Electric Cloud, Enthiosys, Rally and Agile Journal.

Published in: Technology, Economy & Finance
1 Comment
4 Likes
Statistics
Notes
  • Hi,

    Is there any way by which I can download this presentation? I know Presentation Transcript is available at the bottom but need those meaningful images and graphs from presentation as well. I would appreciate if you could mail this presentation at hareshkarkar@yahoo.co.in.

    Thanks,
    Haresh
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,815
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
0
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide
  • Include “continuous integration” and transparency and surfacing deadwood.
  • Agile Comes to You (Mironov, Bellevue)

    1. 1. Agile Comes To You<br />Presented by AccuRev, Coverity, Enthiosys, Electric Cloud, Rally and Agile Journal<br />July 28, 2009<br />Bellevue, WA<br />
    2. 2. Agenda <br />8:45 AM Welcome: Cliff Utstein, AccuRev<br />9:00 AM Keynote: Rich Mironov, Enthiosys<br />9:45 AM Coverity: &quot;Managing Software Quality in Agile Environments&quot;<br />10:15 AM Break<br />10:30 AM Rally: &quot;Case Study: Customizing Agile Tools for Project Success&quot; <br />11:00 AM AccuRev: &quot;Automating Agile software development processes&quot;<br />11:30 AM Break<br />11:45 AM Electric Cloud: &quot;Optimizing Your Development, Build and Release Processes&quot;<br />12:15 PM Lunch and Vendor Demonstrations<br />1:30-2PM Raffle<br />
    3. 3. About Rich Mironov<br />CMO at Enthiosys, agile product mgmt consultancy<br />Business models/pricing, roadmaps<br />Agile transformation and Interim product exec<br />Innovation Games® and customer needs<br />Chair of Agile 2009 PM/PO stage<br />Repeat offender at software prod mgmt<br />Tandem, Sybase, four start-ups<br />“The Art of Product Management” and monthly agile product blog<br />
    4. 4. What is Agile?<br />Umbrella term describing sets of software project management and engineering methods/practices<br />Incremental, iterative and collaborative, rather than distinct stages <br />More frequent delivery of smaller, valuable increments<br />Building quality in, not adding it at the end<br />Goal of potentially shippable at every iteration<br />Active user involvement (or customer proxy)<br />Agile teams must be empowered and self-motivating<br />
    5. 5. Discussions about Agile…<br />Part philosophy and religion<br />Part process, tools, techniques, methods<br />Part organizational design<br />
    6. 6. Agile is an Umbrella<br />agile methods<br />Scrum<br />Extreme Programming (XP)<br />Agile Project Management Framework (APM)<br />Crystal Methods<br />Dynamic Systems Development Model (DSDM)<br />Rational Unified Process (RUP)<br />Feature Driven Development (FDD)<br />Lean Development<br />Rapid Application Development (RAD)<br />…<br />
    7. 7. Lean Roots<br />Roots in Toyota Production System<br />“Create a continuous process flow to bring problems to the surface”<br />“Level out the workload”<br />“Build a culture of stopping to fix problems, to get quality right the first time”<br />“Become a learning organization through relentless reflection and continuous improvement”<br />Source: Liker, Jeffrey (2004). &quot;The 14 Principles Of The Toyota Way: An Executive Summary of the Culture Behind TPS&quot;.<br />
    8. 8. The Agile Manifesto (2001)<br />We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: <br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation <br />Customer collaboration over contract negotiation<br />Responding to change over following a plan <br />That is, while there is value in the items on the right, we value the items on the left more. <br />www.agilemanifesto.org<br />
    9. 9. 12 Agile Principles<br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. <br />Welcome changing requirements, even late in development. Agile processes harness change for the customer&apos;s competitive advantage. <br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale. <br />Business people and developers must work together daily throughout the project. <br />
    10. 10. 12 Agile Principles<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. <br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. <br />Working software is the primary measure of progress. <br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. <br />
    11. 11. 12 Agile Principles<br />Continuous attention to technical excellence and good design enhances agility. <br />Simplicity - the art of maximizing the amount of work not done - is essential. <br />The best architectures, requirements and designs emerge from self-organizing teams. <br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
    12. 12. Requirements<br />Design<br />Coding and <br />unit test<br />System integration & QA<br />Operation and maintenance<br />Waterfall: Linear, Cascading<br />
    13. 13. Agile (Scrum) Model<br />Plan out 1-4 weeks work<br />Meet daily<br />Create product needs <br />Review product<br />Strategic planning<br />Improve process<br />After: Gabrielle Benefield<br />
    14. 14. Fixed Vs. Variable<br />Waterfall<br />Agile<br />Fixed<br />Requirements<br />Time<br />Resources<br />Value<br />Driven<br />Plan <br />Driven<br />Estimated<br />Features<br />Time<br />Resources<br />The Plan creates cost/schedule estimates<br />Release themes and feature intent drive estimates<br />
    15. 15. Planning Time Horizons<br />many years<br />Exec<br />Strategy<br />years<br />Portfolio<br />many mons<br />PM<br />Product<br />2-9 mon<br />Release<br />Dev<br />Team<br />Sprint<br />2 wk<br />Daily<br />
    16. 16. State of Agile Today<br />Most companies early in agile adoption cycle<br />Pockets of pioneers<br />Often distributed teams<br />Some examples of fully scaled-up divisions<br />Highlights need for portfolio-level planning<br />Data from VersionOne<br />
    17. 17. Business Benefits of Agile<br />Shorter development cycles<br />Strategic flexibility<br />Deeper connection and alignment with markets<br />Improved team morale<br />Greater profitability<br />But requires investment, leadership and patience<br />
    18. 18. Agile Transformation<br />Agile is about changing the way people work<br />Not just the tools they use<br />Not just units of work or development sequence<br />Organizational change takes time<br />A successful 300-person Eng team took 18+ months<br />Executives need to drive organizational issues and expectations<br />Let teams handle their own details<br />Plan for outside experts, coaches, instructors<br />Some of your team won’t fit with Agile<br />
    19. 19. 3 Legs of the Agile Stool<br />Management<br />Product & Project<br />Corporate<br />Structure & Culture<br />Engineering<br />Quantity & Quality<br />
    20. 20. Staffing & Resources Allocation<br />Executive’s key tasks: build teams, set priorities<br />Agile wants stable teams, fewer projects/person<br />5-7 core technical members (dev, QA, Ops)<br />Strong intra-team leadership (product, program, requirements) may be shared<br />Pool of technical experts (architect, UI)<br />At your company, how many projects is each developer assigned to? Each architect?<br />
    21. 21. Engineering Resource Pool<br />Developers<br />QA<br />Prod<br />Mgmt<br />SW<br />Arch<br />Sec<br />Arch<br />Pgm<br />Mgmt<br />UI/<br />UXD<br />Dev Tools / Release Eng <br />docs<br />TechOps<br />Product owner<br />Fully dedicated<br />Scrum master<br />Partlydedicated<br />Resource allocation is strategic<br />
    22. 22. Whole Product Team<br />Most Agilists focus here<br />
    23. 23. The Broader Organization<br />Agile reaches well beyond development teams<br />Dramatic reshaping of product management<br />Product Owner is integral to team, but part of PM<br />Intensive real-time PO role demands more PM staffing<br />Strong impact on Marketing, Sales, Support<br />More, faster product deliveries stresses field/channels<br />Marketing uses personas/stories to position value<br />Roadmap flexibility changes Sales behaviors<br />Opportunity for more customer transparency<br />Growing interest in applying Agile to other functions<br />
    24. 24. Executive Product/Program Mgmt<br />As business leaders, we must provide:<br />High-level product priorities<br />Clear, current, actionable roadmaps<br />Moderately stable over time<br />Don’t confuse flexibility with anarchy<br />Broad and deep market input versus “top-of-mind”<br />Planned, strategic, representative<br />Program management tools and reporting<br />Infrastructure: backlogs, velocity, remote teams…<br />New kinds of contention<br />
    25. 25. Take-Aways<br />The best software organizations using Agile to improve results and internal satisfaction<br />Blends methodology, skills, tooling, coaching and company-wide collaborative attitude<br />Transformation takes time and resources<br />Most impact on Engineering and Product Management<br />Keep management attention on roadmap, strategic priorities, high-level goals and metrics<br />Empower teams to find their way to success<br />

    ×