That's very nice to see the problems . That said, the aim is to solve the !
Then, those problems identified and visible to everyone, are they treated?
1. REMINDER
Remember : the team realizes that to learn, grow and become more effective, it must systematically solve the problems it faces .
So
Then, those problems identified and visible to everyone, are they treated?
1. REMINDER
Remember : the team realizes that to learn, grow and become more effective, it must systematically solve the problems it faces .
So
- is developed systematic detection of problems;
- it shows the problems for making visible ;
- it solves problems in a structured .
This attitude and approach are described in a preceding note .
2. Is it practical É ?
To ensure that these fine principles became practices, we 's show an indicator showing the number of solved problems (lower bars) and the number of unresolved problems ( the top of the bars) . This indicator is updated every iteration (see photo above) .
3. IS IT EFFECTIVE?
It's fine to put in place new practices - does it still there is a return on investment ... And there you have recognize that it is difficult to measure the impact of systematic problem-solving.
Difficult is not impossible: burndown chart- curve and non-quality show gains in productivity and quality of this approach.
particular, the curve non-quality revealed severe reductions in non-quality corresponding to sites set up in response to a problem raised. Then, the ranges after a fall of this curve shows that the remedial action "punch" was effectively transformed into continuous practice. Since
burndown chart- does not suffer from an increase or a stagnation of the "remaining to be done" is that the resolution of the problem has contributed positively to development.
4. SIDE EFFECT
We noticed another beneficial side effect of this approach. This is a very large increase standardization.
Indeed, solving a problem usually results in:
2. Is it practical É ?
To ensure that these fine principles became practices, we 's show an indicator showing the number of solved problems (lower bars) and the number of unresolved problems ( the top of the bars) . This indicator is updated every iteration (see photo above) .
3. IS IT EFFECTIVE?
It's fine to put in place new practices - does it still there is a return on investment ... And there you have recognize that it is difficult to measure the impact of systematic problem-solving.
Difficult is not impossible: burndown chart- curve and non-quality show gains in productivity and quality of this approach.
particular, the curve non-quality revealed severe reductions in non-quality corresponding to sites set up in response to a problem raised. Then, the ranges after a fall of this curve shows that the remedial action "punch" was effectively transformed into continuous practice. Since
burndown chart- does not suffer from an increase or a stagnation of the "remaining to be done" is that the resolution of the problem has contributed positively to development.
4. SIDE EFFECT
We noticed another beneficial side effect of this approach. This is a very large increase standardization.
Indeed, solving a problem usually results in:
- a measure against automated ( scripted build in in the commit, ...) ;
- a cons manual measurement described by a small textual procedure;
- improve an existing process.
Thus, we found that our wiki has enriched many small pragmatic procedures. This is the formalization of the best ways to make this point for this project. This is a standard lightweight, scalable, shared by team members.
I thought that standardization was a formal step, heavy and slow down evolution. I am now convinced otherwise.
I thought that standardization was a formal step, heavy and slow down evolution. I am now convinced otherwise.