Introduction to Lean & Agile Work
Download as PPTX, PDF2 likes5,108 views
The document provides an overview of lean and agile methodologies, emphasizing the importance of collaboration, frequent delivery, and responsiveness to change in software development. It outlines the Agile Manifesto's values and principles, as well as Lean principles which focus on eliminating waste and empowering teams. Additionally, it addresses common myths associated with agile practices.
Introduction to Lean & Agile Work
- 2. Introduction to Lean & Agile Work Ellen Grove egrove@agilepartnership.com
- 5. Agile is a highly collaborative project delivery method that has smallfunctional releases which are delivered frequently egrove@agilepartnership.com
- 6. The Agile Manifesto That is, while there is value in the items on the right, we value the items on the left more. http://www.agilemanifesto.org Individuals and interactions Working software Customer collaboration Responding to change Processes and tools Comprehensive documentation Contract negotiation Following a plan over over over over We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- 7. 12 Agile Principles 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 behaviour accordingly. 1. 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 customer's 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. egrove@agilepartnership.com
- 8. 7 Lean Principles 1. Eliminate Waste 2. Amplify Learning 3. Delay Commitment 4. Deliver Fast 5. Empower People 6. Build Integrity In 7. See the Whole Eliminate Waste Value Stream Mapping Feedback Iterations Synchronization Set-based Development Options Thinking Last Responsible Moment Decision Making Pull Systems Queue Theory Cost of Delay Perceived Integrity Conceptual Integrity Refactoring Testing Self Determination Motivation Leadership Expertise Measurements Contracts egrove@agilepartership.com
- 11. Agile Myths: It’s a ‘silver bullet’ It’s easy to do It’s all about the tools On an Agile project there’s no: Planning, budgets, documentations, modeling, design….. “I can see how it would work on other projects, but it will never work here!” …what else? Pandy Corona [CC-BY-SA-3.0 (www.creativecommons.org/licenses/by-sa/3.0) or GFDL via Wikimedia Commons egrove@agilepartnership.com
Editor's Notes
- #7: These are the Agile Values. This is a culture change. You will need to revisit this manifesto MANY times.
- #12: What Agile Development isn’t?Resistant to ChangeChanges are going to happen, so figure out a way to deal with them!Agile is based on learning as you go, which is what happens in reality anywayNo modeling and no documentation:Focuses on modeling just when it’s requiredFocuses on just the documentation that is requireIf the client stipulates that full system documentation is required, then do it! Create User Stories for it, estimate them and schedule just like anything else.Easy to do:Agile development requires constant workThe whole team must be on board – even one resistant person can impair the processIt takes people out of their comfort zones – the development process is visible and accountable, and people can’t hide behind an 8-month development cycle“I can see how it would work, but it will never work here!”I’ll defer comment until the Review at the end