Agile Software Development Scrum Vs Lean


Published on

Published in: Education, Technology, Business
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile Software Development Scrum Vs Lean

  1. 1. Scrum vs Lean Abdul Wahid
  2. 2. Scrum <ul><li>The term for a strategy in the rugby game that means ‘getting out-of play ball back into the game’ with team work </li></ul><ul><li>Management methodology by Schwaber and Beedle, 2001 </li></ul><ul><li>Assumes that development process is unpredictable and complex, requiring flexibility and responsive to change </li></ul><ul><li>Characteristics: </li></ul><ul><ul><li>Self-organizing teams </li></ul></ul><ul><ul><li>Product progresses in a series of month-long “sprints” </li></ul></ul><ul><ul><li>Requirements are captured as items in a list of “product backlog” </li></ul></ul><ul><ul><li>No specific engineering practices prescribed </li></ul></ul>
  3. 3. Lean Software Development <ul><li>Derived from the Lean Manufacturing (Toyota) </li></ul><ul><li>Focuses much more on the project management aspects of software development </li></ul><ul><li>Specifically targeting the cost and ROI attributes of a project </li></ul>
  4. 4. Lean Principles <ul><li>Create nothing but value/ Eliminate Waste </li></ul><ul><li>Build Quality In </li></ul><ul><ul><li>Automate as much as possible </li></ul></ul><ul><li>Create Knowledge </li></ul><ul><ul><li>Work with business people </li></ul></ul><ul><li>Defer Commitment </li></ul><ul><ul><li>Decide as late as possible </li></ul></ul><ul><li>Deliver Fast </li></ul><ul><li>Respect People </li></ul><ul><li>Optimize the Whole </li></ul><ul><ul><li>optimizes the whole value stream, from the time it receives an order to address a customer need until software is deployed and the need is addressed </li></ul></ul>
  5. 5. Apples to Oranges?
  6. 6. Apples to Oranges? <ul><li>Comparing Scrum to Lean - Not Quite Apples to Oranges (alshall) </li></ul><ul><li>Lean and Scrum are both about improving the software development capabilities of an organization </li></ul><ul><li>Scrum and Lean are mindset </li></ul><ul><li>They have different approaches and they work effectively in different situations. </li></ul><ul><li>Scrum starts at the team while Lean starts at the process. </li></ul><ul><li>Lean Software Development provides much more specific hints how to perform tasks and a set of engineering practices, while Scrum restricts itself to a basic framework of project management practice </li></ul>
  7. 7. Comparison with respect to different aspects
  8. 8. Scrum vs Lean <ul><li>Procedures </li></ul><ul><ul><li>Scrum has few, but well defined meetings, roles, artifacts Lean consists of practises and more general advices – all starting with the value stream </li></ul></ul><ul><li>Team and Responsibilities </li></ul><ul><ul><li>In Scrum the team is self organized and as a team responsible for the results. The results are presented to the Product Owner in Sprint reviews who accepts them and represents the business responsibility to the outside world. </li></ul></ul><ul><ul><li>Lean also puts much emphasis on developing a team and its initiative and involvement, but there exists also an aspect of leadership – at Toyota in the role of the chief engineer. The chief engineer or champion is ultimately responsible for the results, breaks deadlocks and ensures the results are produced in time. </li></ul></ul>
  9. 9. Scrum vs Lean <ul><li>Values </li></ul><ul><ul><li>Respect </li></ul></ul><ul><ul><li>People are not resources </li></ul></ul><ul><li>Engineering practices </li></ul><ul><ul><li>Scrum does not contain statements about engineering practices, so it is easy to add the Lean engineering practices </li></ul></ul>
  10. 10. Scrum vs Lean <ul><li>Knowledge Building </li></ul><ul><ul><li>Scrum has a widely-used practice of retrospectives in teams. While the retrospective was not part of the original definition of Scrum, it is impossible to imagine today’s Scrum practice without retrospectives. The retrospective is in some sense where teams’ learning takes place. Scrum contains no institutionalized form of spreading knowledge in an organization. </li></ul></ul><ul><ul><li>Lean addresses knowledge building in two ways: </li></ul></ul><ul><ul><ul><li>first, it combines the areas decision making and knowledge building </li></ul></ul></ul><ul><ul><ul><li>Second, Lean has means to follow up on acquired knowledge: </li></ul></ul></ul><ul><li>Iterations / Sprints / Timeboxes </li></ul><ul><ul><li>Scrum work is done in fixed length iterations called Sprints. </li></ul></ul><ul><ul><li>Lean is less specific on time boxes. It has a system called Kanban which ist similar to a product backlog. </li></ul></ul>
  11. 11. Conclusion <ul><li>While Scrum and Lean concentrate on different aspects, they both have their main focus on creating value and share fundamental values. </li></ul><ul><li>Scrum does not prescribe a specific process, it is a framework which can be extended to a process and many of the Lean principles can be used in doing so where Scrum does not contain a definition. </li></ul>
  12. 12. Lean References <ul><li>“ Lean Software Development: An Agile Toolkit “ by Mary Poppendieck and Tom Poppendieck </li></ul><ul><li>Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series) </li></ul><ul><li>“ Implementing Lean Software Development: From Concept to Cash” by Mary Poppendieck and Tom Poppendieck </li></ul><ul><li> </li></ul><ul><li>“ Agile Software Development with Scrum” by Kent Schwaber and Martin Beedle </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.