Is Scrum is Lean? | Lean Leaders
Contrary to popular belief elimination of waste is not a pillar nwolb of Lean. Still, the ability of noticing waste is essential for practitioners of lean management. This article is a brief summary of how the Scrum minimizes waste of the type of work in progress.
Like any other type of work that consumes resources, even though we do not know whether its effect will be applied by the customer. Moreover, such a partially constructed work may contain hidden defects that will not be identified until the work is completed and accepted by the user. Examples of software development: exhaustive analysis of requirements made at the beginning of the project, local changes in the code are not put into version control system functionality created on the so-called "branches of development," not merged with the code in the "production branch".
According to this key concept Scrum each team should be able to complete the cycle of a product able to be able to issue it. This means implementing all the measures necessary to ensure that the added functionality nwolb (product growth) are complete and sufficiently high quality. To assist the team scrumowy in designing adequate steps formed "The definition of Completion" (ang. Definition of Done DoD). DoD is a common, complete list of activities that must be performed in order to gain to be considered complete.
Quite often development team is not able to perform all activities from the list. These unimplemented often related to missing competences (eg testing nwolb of end-to-end, writing technical documentation, etc..) In accordance nwolb with the principles of Scrum team must complete all the steps, otherwise the work will not be considered complete. What in this situation can you do? We usually have the choice of two paths:
1) Pass all the work that we do, and which are not reflected in a pool of skills of the team to a specially appointed team or department. This approach, although relatively easy to implement nwolb is substantially major "genetic defect" would inevitably lead back towards the sequential processes nwolb (waterfall)
An interesting method of coping with this situation, especially when you want to go from the first to the second model suggested Craig Larman: Iteration of releases, during which members of the functional units (eg. Vertical testers or documentary team) are working shoulder to shoulder with members of the Scrum teams. It may seem that this is a typical "hardening sprint". Technically, yes - in fact different but the basic premise. It is no longer to complete what you have not managed to do but to create zespłom nwolb scrumowym conditions for the learning of new skills into practice.
From the point of view of the type of waste elimination work in progress, it is important to try to broaden the definition Completion team, even at the expense of the number of functionalities implemented during the sprint. Otherwise you can easily lead to a situation in which the efficient efforts of the development team (one that produces efficient "semi-finished" - for example, code that is not integrated and tested with the rest of the system) will fail, because the results of their work will begin to pile up in " magazine "departments pursuing the rest of the tasks of the full Definition Completion.
Event Venue Date Information Academy Scrum Master Agile and Scrum in IT Wroclaw 4-5.10.2014 Page Agile requirements Wroclaw 11.10.2014 Academy Scrum Master Plan and the requirements 25-26.10.2014 Wroclaw University of Scrum Master Page Facilitation and flashbacks 15-16.11.2014 nwolb Wroclaw Home Test Driven Development Academy of Wroclaw 22.11.2014 Scrum Master Working with the team and the organization Wroclaw 6-7.12.2014 Page Acceptance Test Driven Development Wroclaw 12.13.2014 OR FOR CONTINUOUSLY - Like us
2011-2014 Lean Leaders Let's change IT!
Contrary to popular belief elimination of waste is not a pillar nwolb of Lean. Still, the ability of noticing waste is essential for practitioners of lean management. This article is a brief summary of how the Scrum minimizes waste of the type of work in progress.
Like any other type of work that consumes resources, even though we do not know whether its effect will be applied by the customer. Moreover, such a partially constructed work may contain hidden defects that will not be identified until the work is completed and accepted by the user. Examples of software development: exhaustive analysis of requirements made at the beginning of the project, local changes in the code are not put into version control system functionality created on the so-called "branches of development," not merged with the code in the "production branch".
According to this key concept Scrum each team should be able to complete the cycle of a product able to be able to issue it. This means implementing all the measures necessary to ensure that the added functionality nwolb (product growth) are complete and sufficiently high quality. To assist the team scrumowy in designing adequate steps formed "The definition of Completion" (ang. Definition of Done DoD). DoD is a common, complete list of activities that must be performed in order to gain to be considered complete.
Quite often development team is not able to perform all activities from the list. These unimplemented often related to missing competences (eg testing nwolb of end-to-end, writing technical documentation, etc..) In accordance nwolb with the principles of Scrum team must complete all the steps, otherwise the work will not be considered complete. What in this situation can you do? We usually have the choice of two paths:
1) Pass all the work that we do, and which are not reflected in a pool of skills of the team to a specially appointed team or department. This approach, although relatively easy to implement nwolb is substantially major "genetic defect" would inevitably lead back towards the sequential processes nwolb (waterfall)
An interesting method of coping with this situation, especially when you want to go from the first to the second model suggested Craig Larman: Iteration of releases, during which members of the functional units (eg. Vertical testers or documentary team) are working shoulder to shoulder with members of the Scrum teams. It may seem that this is a typical "hardening sprint". Technically, yes - in fact different but the basic premise. It is no longer to complete what you have not managed to do but to create zespłom nwolb scrumowym conditions for the learning of new skills into practice.
From the point of view of the type of waste elimination work in progress, it is important to try to broaden the definition Completion team, even at the expense of the number of functionalities implemented during the sprint. Otherwise you can easily lead to a situation in which the efficient efforts of the development team (one that produces efficient "semi-finished" - for example, code that is not integrated and tested with the rest of the system) will fail, because the results of their work will begin to pile up in " magazine "departments pursuing the rest of the tasks of the full Definition Completion.
Event Venue Date Information Academy Scrum Master Agile and Scrum in IT Wroclaw 4-5.10.2014 Page Agile requirements Wroclaw 11.10.2014 Academy Scrum Master Plan and the requirements 25-26.10.2014 Wroclaw University of Scrum Master Page Facilitation and flashbacks 15-16.11.2014 nwolb Wroclaw Home Test Driven Development Academy of Wroclaw 22.11.2014 Scrum Master Working with the team and the organization Wroclaw 6-7.12.2014 Page Acceptance Test Driven Development Wroclaw 12.13.2014 OR FOR CONTINUOUSLY - Like us
2011-2014 Lean Leaders Let's change IT!
No comments:
Post a Comment