The past five years, Agilean been helping a large stake in line Kanban Lean transformation. From floor to deepen into a comprehensive, quantified improvement from the grassroots to enabling the bank currently signage usage has reached 90%, as the leading domestic level. In this process, we will lean thinking and Kanban methods through a more organic, forming a research and development to help companies quickly improve performance improvement system FLEET (performance improvement Lean thinking framework, Framework of Lean Efficacy Enhancement Thinking). I will combine ground experience, all-round FLEET explained.
The following is a FLEET of the six core ideas:
- See : the greatest enemy of efficient knowledge work, knowledge work is invisible processes and outcomes. First of all to make use of Kanban visualization, construction site management;
- Rectification : As knowledge work "invisible" process is likely to cause congestion work. Preferably need to establish mechanisms to reduce work in parallel, focus can be maintained to enhance flow efficiency;
- Fine : After rectification, if the particles are too large demand, the demand can not be fast flows. This would further reduce the particle size needs to accelerate the flow, improve the quality of feedback velocity;
- Lubrication : demand delivery of low quality will result in rework, increased demand for the degree of parallelism that produce "friction" between each other. Strengthening needs clarification, quality activities and other quality forward, can reduce the friction between the demand to ease the process of resistance;
- Small batches : regular demand will be selected, will be clarified, such as the transfer of the bulk version of events, it will slow down the rate of flow from end to end, resulting in waiting. Batch should be minimized to reduce the waiting time;
- Cost reduction : the transaction cost is the fundamental reason for the existence of bulk. Through the promotion of automated regression testing, automated deployment and other activities, reduce transaction costs and make it possible to reduce bulk.
See: construction management site for managers
Managers typically will have a working knowledge of anxiety, the more people, the easier pipes anxiety. In a number of reasons, the lack of effective visual management tools is the most important. See of unclear, the more hesitant, the birth of anxiety. Into anxiety managers, often using more rigorous management tools, but also cause more under cover and concealment, invisible work status is further enhanced, thus forming a vicious cycle.
• Stanley McChrystal (former commander of the US Special Operations Command) book "enabling" a book, the authors propose a good idea: "eyes fixed, his hands let go." Eyes glued to be able to do, dare to let go of his hands. FLEET of a core idea - Kanban for knowledge work with visualization, is the ability to "see" is to be given to managers. After Kanban well-designed, it can provide important site for the R & D management team managers . Below is my counseling in 2014, an innovative research and development projects billboards, the project completed the process from 0-1 of an innovative financial APP within four months. "Visualization" practice biggest challenge lies in the practical work of the team to sort out and modeling of the value stream.
Rectification: need to establish a preferred mechanism
See below and answer: Intuitively, you think this is what place?
In any other city this course, participants are often considered to be the train station; students living in Beijing but at a glance, this is the Bronze or Xi'erqi subway station. Rectification measures outside the iron railings of the station subway system - although some allow individuals to walk the road, have become more wait, but to ensure the overall (each individual) spend less time waiting.
In the case of long-term is not visible, most R & D team in high parallel overload state , which is characterized by sustained interrupted, massively parallel. Studies have shown that the flow efficiency of software development is usually only 1% to 5% . At a very low flow efficiency of the development process, priority must be introduced demand mechanism, namely priority selection. The following chart billboards, for example, "development" column before the "Select" Queue (red box), pent-up demand will remain outside the R & D system, to avoid further exacerbating the blocking process, the development process to ensure rapid optimization.
小团队比较容易建立需求优选机制。对大型组织而言，建立需求优选机制的主要挑战，在于如何有效平衡各业务方的诉求。我们在实践中发现，部落制是解决这个问题的有效方式。将研发组织和业务组织拉通（可采用虚拟方式），将研发资源合理分入不同部落、面向不同业务方，然后在部落内建立合适的需求优选机制。
P.S. 流动效率、部落制等话题均较复杂，未来我们将专文详述。
细粒：需求拆分加速流动
需求优选机制运行起来后，下一个改进点是减小需求颗粒度，将需求拆分成更小的可验收可测试单元。规模过大的单元，不利于透明其执行过程中的等待、阻塞和风险。对于大型组织，我们建议采用需求、系统任务、个人任务的三级体系，系统任务控制在10人天，个人任务拆至2-3人天。
下图为之前提到的创新项目快速启动现场（研发正式开始前的启动环节，通常为2-3天）。业务和IT共同拆出350多个粗粒度用户故事，据此制定了迭代计划和关联系统计划，完成看板建模，形成风险应对方案。团队在其后的三个月里完成6个迭代，项目准时上线，产品内容、功能和质量都获得了高度认可，在当年赢取了国内若干重要银行奖项。
润滑：降低需求摩擦
需求颗粒度减小后，通过降低需求彼此之间的摩擦，可以让研发过程流动更加顺畅。什么是需求摩擦？看图——
这段对话熟悉吗？对不少研发同学来说，本来正在做A需求，中间被叫去评审B需求，过会儿又要修改C需求的缺陷，需求之间就产生了摩擦。有很多方法可以降低需求之间的摩擦：
- 实例化需求，提升需求初始质量；
- 产品经理制度，专人负责与业务澄清需求；
- 需求研发双迭代，需求澄清迭代和研发迭代并行，澄清迭代的输出是研发迭代的输入；
- 建立开发自冒烟制度、代码评审制度，提升初始移交质量，减少测试摩擦。
小批：尽一切可能减小批量
加速流动的一个有效方法是减小批量。「批量」指在某些环节中多件事情一起处理，比如多个需求一起澄清，多个设计一起评审，多个功能一起上线，这些都是批量。批量必然导致一些需求等待另一些需求，减慢端到端的需求流动速度。
After the batch is reduced, demand more quickly flow from development to testing and UAT link as soon as possible to generate feedback on the quality . As shown above, by reducing the volume, the original three months to complete the 600 demand, has now become every two weeks to complete the 100 demand, lead times shortened to 1/6 of the original, greatly accelerate the speed of delivery. Therefore, we should be looking for every possible opportunity to reduce bulk. For example, IT and business teams are not in a workplace when the agreement meets weekly to clarify requirements; if a centralized office at the workplace, to clarify the needs of a lot easier, eliminating the bulk Zhoucheng Qing caused the club.
Cost reduction: to reach the optimal solution with reasonable quantities
Destroy all volume, single-piece flow, minimize wasteful wait, this is an ideal state. In reality, because of transaction costs, to form a reasonable batch size, we have to seek is the optimal solution .
Transaction costs refer to the additional additional costs in the process of doing one thing, you need to pay. For example, demand clarification to book conference rooms, to coordinate the participants time; release to regression testing, to review, to stay up all night made version, this is transaction costs.
The higher the transaction costs, people tend to form larger batches. In order to reduce bulk, often need to reduce transaction costs. Automated regression testing, automated deployment, reduce unreasonable flow system, these are means of reducing transaction costs.
FLEET is set to help companies quickly locate problems, and promote the optimization and improvement of the initial frame of mind, the goal is for companies to quickly bring about improvements. We will FLEET cross-checked with the previous practical experience, a lean performance improvement practice system, it has helped many large organizations achieve a 'optimization sprint, speed increase quality "targets.