Recently, I have been reading "Gold Mine", a book about lean, which tells about various Kanban and process sorting. I can't help but think of some scrum processes, A lot of Knowledge gives me more thoughts.
The process in lean is based on Kanban to pull the production at the front. At the same time, it controls the production cycle and pace at the front to ensure the reduction of In-process products, thus reducing the inventory in production, it also reduces costs. So what if I put this idea into scrum?
Previously, when performing scrum R & D, the process was similar
One consequence of doing so is that the previous results are constantly generated, resulting in a large backlog of tasks in the middle. Generally, the tasks are under pressure in the test area, resulting in a large number of R & D results, however, there are a lot of Results waiting for the test, that is, there are a lot of unfinished tasks. These large backlog of tasks lead to a lot of test pressure, but also lead to a high cost for the entire production process, at the same time, there are very few things to accomplish in a certain period of time.
If we change our mindset to stimulate production, will it make the situation better?
The subsequent production capabilities determine the previous production, that is, the subsequent production, to pull the previous production, so that the entire R & D cycle is relatively fixed and predictable. At the same time, you can determine the number of R & D personnel based on the subsequent production capacity. If you need to speed up the process due to time pressure and other reasons, you need to make adjustments later, that is, the dynamic deployment of personnel, R & D personnel testing or transfer to testing personnel, etc., to ensure the cycle of the overall process and control quality.
When boosting production, you can control the quality of each link. If the quality is not up to standard, can you return it? Can I detect problems in time? These are to be tested.