• Share
  • Email
  • Embed
  • Like
  • Private Content
An Introduction to Agility

An Introduction to Agility






Total Views
Views on SlideShare
Embed Views



5 Embeds 3,462

http://iicmagazine.pl 1748
http://itcrewblog.pl 1498
http://video-it.pl 193
url_unknown 22
http://translate.googleusercontent.com 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    An Introduction to Agility An Introduction to Agility Presentation Transcript

    • Martin Stenkilde, Rational Technical Executive, CEEAn Introduction to Agility © 2011 IBM Corporation
    • Building a smarter planetAgenda & Introduction Introduction & Objectives Why Agile? How? Key Aspect of Successful Agile Adoption Scalability Summary2 © 2011 IBM Corporation
    • Building a smarter planetAgile Motivation: CIO study 2011 Demand for IT Services “The economic downturn forced deep cuts in IT budgets. Now, as CIO’s plan for the recovery, they are facing unprecedented demand for IT services from the business. At the same time, organizations are still keeping spending tightly under control.” CIOUpdate.com August 3, 2010 http://www.cioupdate.com/budgets/article.php/3896646/How-to-Get-the-Budget-You-Need-in-2011.htm Executive Programs CIO Survey 18.0% 15.0% Increases in 15.9% CIO Budgets Over Previous Year, 1998-2009 (Worldwide) 16.0% 14.0% 12.0% 9.7% 10.1% 10.0% 8.0% 6.0% 4.0% 3.0% 3.2% 1.3% 2.5% 2.7% 2.0% 1.6% 0.0% 0.16% 0.0% 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 Source: Gartner Trend Line The Key: Improve delivery with the resources you have3 © 2011 IBM Corporation
    • Building a smarter planetAgile Motivation: Benefits of Being Agile4 © 2011 IBM Corporation
    • Building a smarter planetWhat Agile is NOT !!5 © 2011 IBM Corporation
    • Building a smarter planetAgile Principles Individuals Processes We value Interactions over and Tools Working Comprehensive Software Documentation Customer Contract Collaboration Negotiation Responding Following to Change a Plan6 Source: www.agilemanifesto.org © 2011 IBM Corporation
    • Building a smarter planetAgile principles1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.2. Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage.3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.4. Business people and developers must work together daily throughout the project.5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. (Continued…) Source: www.agilemanifesto.org/principles.html7 © 2011 IBM Corporation
    • Building a smarter planetAgile principles (continued)7. Working software is the primary measure of progress.8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.9. Continuous attention to technical excellence and good design enhances agility.10. Simplicity – the art of maximizing the amount of work not done – is essential.11. The best architectures, requirements, and designs emerge from self-organizing teams.12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Source: www.agilemanifesto.org/principles.html8 © 2011 IBM Corporation
    • Building a smarter planetWhat is agile?  Agile is a highly collaborative, evolutionary, quality focused approach to software development.  Agility gives you.. – Focus on collaboration – Focus on quality – Focus on working solutions – Agilists are generalizing specialists – Agile is based on practice, not theory9 © 2011 IBM Corporation
    • Building a smarter planet Agile Characteristics – Example, the family trip •Just enough planning • Time-boxed iterations • Velocity • Alternate Routes • Handling Surprises • Retrospective • Team work • Motivating the Team • Differing Stakeholder Goals • Workspace Considerations • Repeatable, Sustainable Iterations10 © 2011 IBM Corporation
    • Building a smarter planet Principles of Lean Software Development Eliminate Waste Build Quality In Defer Commitment Deliver Fast • 20-80 Rule • Foundation Disciplines Keep options open Queuing theory • JIT • Continuous Validation Focus on Learning Respect People Optimize the Whole Product & process • Teams • Systems thinking • Partners11 © 2011 IBM Corporation
    • Building a smarter planetAgile and Lean are complementary Agile – A philosophy that concentrates on delivering things that have value to a customer – Avoid things that have no value to the customer Deliver – Don’t believe in the “big detailed plan” value!!! Lean – Started as a management approach for streamlining production. – Avoid all waste – Get the customer involved at the earliest opportunity Avoid waste!!12 © 2011 IBM Corporation IBM Internal Use Only : With Thanks to Mary and Tom Poppendieck
    • Building a smarter planetAgile Practices13 © 2011 IBM Corporation
    • Building a smarter planetScrum 14Copyright 2009 IBM Corporation © 2011 IBM Corporation
    • Building a smarter planetAgile Modeling15 © 2011 IBM Corporation
    • Building a smarter planetKanban (Lean)16 © 2011 IBM Corporation
    • Building a smarter planetKey Aspects of Successful Agile Deployment People Methodology Tools17 © 2011 IBM Corporation
    • Building a smarter planetPeople Individual Creativity1 + 1 = 3 Consider: –Training –On-going mentoring and coaching –Culture Business stakeholder involvement18 © 2011 IBM Corporation
    • Building a smarter planetMethodology Decide for an agile methodology Good to start from small and let it grow with you Methodology should be tailored for your local needs Think about the model you work – one team, internal development – more teams, internal development – internal development, a lot of people working on bodyshopping – some internal, some external work – internally mainly requirements&testing, all the rest is subcontracted – ...19 © 2011 IBM Corporation
    • Building a smarter planetTools NO AGILITY WITH RIGID TOOLS Tools Should Enable Key Agile Practices Removing the Administration20 © 2011 IBM Corporation
    • Building a smarter planetHow to Start Right Establish a sprint heartbeat via short iterations Establish executive commitment and involvement Create a dedicated, cross-functional rollout team Focus on automation Provide radical transparency and over-communicate Leverage existing Agile training Get outside coaching early Prioritize build and test infrastructure early Be clear about what the Agile “rules” are Encourage peer-to-peer communication Think about tools to track progress Be inclusive Be patient and expect to make mistakes21 © 2011 IBM Corporation
    • Building a smarter planetIs Agile Measurable? ~ How Agile are we? http://jazz.net/blog/index.php/2011/01/26/what-is-your-agile-fitness22 © 2011 IBM Corporation
    • Building a smarter planetIs Agile Measurable? ~ How Agile are we?1. Value: Produce a consumable solution on a regular basis which provides value to stakeholders.2. Validation: Do continuous regression testing, and better yet take a Test-Driven Development (TDD) approach.3. Stakeholders: Work closely with their stakeholders, or a stakeholder proxy, ideally on a daily basis.4. Self-organization: Are self-organizing and work within an appropriate governance framework.5. Improvement: Regularly reflect on, and measure, how they work together and then act to improve on their findings in a timely manner. Source: Scaling Agile: An Executive Guide, ftp://public.dhe.ibm.com/common/ssi/sa/wh/n/raw14211usen/RAW14211USEN.PDF23 © 2011 IBM Corporation
    • Building a smarter planetCan Agility be Scaled? Team size Compliance requirement Under 10 1000’s of Critical, developers developers Low risk Audited Geographical distribution Domain Complexity Straight Intricate/ Co-located Global -forward Emerging Disciplined Enterprise discipline Agile Organization distribution Project Enterprise Delivery (outsourcing, partnerships) focus focus Collaborative Contractual Organizational complexity Technical complexity Flexible Rigid Heterogeneous, Homogenous Legacy24 © 2011 IBM Corporation
    • Building a smarter planetWhat is Disciplined Agile Delivery? Unified Process (UP) Extreme Disciplined Agile Programming (XP) Delivery (DAD) Agile Scrum Modeling DAD is a hybrid process framework adopt best practices and philosophies from several methodologies25 © 2011 IBM Corporation
    • Building a smarter planetThe Disciplined Agile Delivery (DAD) life cycle The Disciplined Agile Delivery (DAD) process framework is a people-first, hybrid agile approach to IT solution delivery. It has a risk-value lifecycle, is goal- driven, and is scaleable.26 © 2011 IBM Corporation
    • Building a smarter planetWhat is disciplined agile?Disciplined agile delivery is an evolutionary (iterative and incremental) approach that regularly produces high quality solutions in a cost-effective and timely manner via a risk and value driven lifecycle.It is performed in a highly collaborative, disciplined, and self- organizing manner within an appropriate governance framework, with active stakeholder participation to ensure that the team understands and addresses the changing needs of its stakeholders.Disciplined agile delivery teams provide repeatable results by adopting just the right amount of ceremony for the situation which they face. 27 © 2011 IBM Corporation
    • Building a smarter planetScaling Agility: Agile Scaling Model (ASM) Core Agile Development  Focus is on construction  Goal is to develop a high-quality system in an evolutionary, collaborative, and self-organizing manner  Value-driven lifecycle with regular production of working sw  Small, co-located team developing straightforward software Disciplined Agile Delivery  Extends agile development to address full system lifecycle  Risk and value-driven lifecycle  Self organization within an appropriate governance framework  Small, co-located team delivering a straightforward solution Agility at Scale  Disciplined agile delivery and one or more scaling factors28 © 2011 IBM Corporation
    • Building a smarter planetStay Agile What are the meeting points? How much Project Office could be involved? Is ITIL around, can we integrate it? Gantt Charts versus Agile Planning Think Business Business Operational Practice $0M $15M 0% Efficiency 100% 0% 100% Value Adoption29 © 2011 IBM Corporation
    • Building a smarter planetSummary: AGILE IS GREAT IF YOU... Focus on 3 Aspects – Methodology at the Right Scale – Tools Supporting Agility and Colaborating With the Rest of the World – People Getting Support and Motivation From the Mentors/Coaches Learn from Experienced and Utilize Mentoring/Coaching Understand Agile Adoption as a Project and Plan it Get Support of Your Stakeholders30 © 2011 IBM Corporation
    • Building a smarter planet31 © 2011 IBM Corporation
    • Building a smarter planet Visit our training courses and earn your PMI points: – RPV51 Introduction to Disciplined Agile Delivery – RP252 Advanced Disciplined Agile delivery32 © 2011 IBM Corporation