Antecedent Review
We talked on a life cycle, including predictive, Iterative, incremental, agile: 1 based on agile iterative, agile based on 2 increments.
Also mentioned, according to the status of the team, project case select the appropriate development model, in order to ensure the ultimate goal of the project time, cost, quality controlled!
| method | characteristic | action | Deliver | Goal / outcome |
|---|---|---|---|---|
| Predictive | fixed | Throughout the project execution time | single | Management costs increase |
| Iterative | Variety | Repeat until the correct | single | Correct and effective |
| Incremental | Variety | To perform a given increment | Frequent Partial | speed |
| Agility | Variety | Repeat until the correct | Frequent Partial | The maximum customer benefit |
WIP (manufactured by number):
First proposed by Toyota, and achieved good results. If the Internet industry-oriented enterprises, will be more understanding of the role of WIP limit on the production of enterprises. Again, this pattern also applies to the IT sector.
In agile development, WIP limit determines the maximum amount of work workflow in each case can be subsisting. Limit the amount of work in progress can be more easily recognizable team workflow inefficiencies. Before the situation becomes worse, a bottleneck in the team continuous delivery channels is very easy to discern.
By focusing on smaller granularity of a task / time box, to submit "complete" number, WIP limit allows obstacles and bottlenecks obvious. When there is a clear indication of the existing work encounter a problem, the team can focus on understanding as soon as possible blocking problems, implement and solve.
For chestnut: the highway will holiday traffic, when resources are scarce intensive, can cause mass flow type drops, the number of WIP limit team system, focusing on the completion of this secondary story / time box ( smaller size). Intently completed products, WIP limit to encourage a "complete" culture and agility advocated core idea coincide.
- a reference Tencent
WIP limit
during work (WIP), also known as "the product" means has started but not yet completed work is seen as a waste of lean in. Inventory also belong to waste, because it will incur costs in the purchase, storage and maintenance. One way to reduce inventory is to reduce system bottlenecks by removing WIP. Agile advocates to limit WIP by completing all the features before developing new features WIP limit. WIP iteration limit is equivalent to do, all the features should be completed during the iterative review.
From a list of seven software waste Papen Dick's see, WIP itself a waste, excessive WIP will have some problems, including:
- WIP occupied before acceptance of project funds but can not fully allow customers to obtain return on investment. This means no investment gains.
- WIP hides the bottleneck work process. Including slowing the entire work flow (or productivity) and cover operating efficiency.
- WIP risk of rework, since the former are likely to change product acceptance. If WIP lot, then there will be a lot of waste when needed changes or expensive rework.
- In view of these problems, agile methods put forward to limit WIP. In agility, the conventional approach has WIP limit of two, to help reduce the risk of project funds outstanding, rework and waste.
1, limit the number of: using a panel to limit the number of jobs in the system and help ensure that there is no limit WIP overdose. Kanban panel by showing at any given time of the current work should be carried out to the limit WIP.
2, the size limit: limit the size of kanban panel, only the selected task to be able to put the workpiece. Agile teams using Kanban limit WIP Panel tool to identify and remove bottlenecks, to improve process efficiency.
Never Kanban limit WIP panel can see a lot of WIP, also means that the project team are busy working, but can not distinguish between tasks that are idle, Where is the bottleneck. WIP limit where obstacles can show us.
WIP is used to do the work item between man and balanced, the purpose of limiting WIP is to optimize the throughput of work, rather than optimize resource utilization. And by adjusting the value of WIP is considered out. Limit WIP helps us identify bottlenecks in the process, and to maximize productivity, vehicles like the city to implement some of the odd and even numbers limit line, can make traffic more smoothly by restricting vehicles on the road by the
Book The True Story, the so-called "工欲善其事必先利其器" agile team to excessive, that will take some time, as determined according to the length of their own team situation.
Factors quick implementation of:
Scrum coach of professionalism, emotional intelligence, control, logical thinking and planning strategy execution, business familiarity, IT professional indication of reserve, and other departments limited powers;
intention of team members as well as knowledge base for quick mode;
- External support (companies, customers, etc.);
- We are willing to sacrifice that servant, mentor type, coaching; each role hard work and sweat to pay many times more than the crew.
- In Christianity, the pastor, preacher, servant of the practices of the learning team leader uses, as well as in agility, the requirements for agile coaching, project managers, technical managers / executives, both from IT professional range or EQ, responsibility heart and other aspects have higher requirements.
The first factor extension application:
1. To promote people to play Agile projects, the company acquires high-level support, only top-down presumption can be more effective.
2. One of the "good image, good temperament, sweet voice," This is a recruitment company clerk or assistant of the basic requirements, and the "high emotional intelligence, good at dealing with sudden situation, hard and soft means" is also agile coach to be necessary conditions , advantage is keen to find a poor team climate, identify the causes and effects of the rapid elimination of smooth team ability. Imagine, a hot-tempered coach, the team will only make people jittery, its agility in members of the resistance can be imagined, this can not help but say, "" high-profile work, low-key life, "there will be unexpected results oh.
3 .-ranging expertise, IT industry, the rapid development of technology is also used in projects of many languages, non-purely a language we do slash youth, do our best to expand their knowledge, the advantage is firefighters made the team, any job can do the job or guide members in order to gain trust and dependence team members.
4. logical thinking and planning strategy execution, seen some articles were taken out of context, agility do not need programs that promote freedom. The so-called freedom means the freedom of the limited space. Plans, strategies, early in the project execution, agile coach has made adequate preparations, but steady advance to members in accordance with policies and programs, and through constant spying, feedback to adjust their plans. Besides execution, I always had an idea "Dingsi it," any project or task to be this way, people are inert, and let go only through proper and rigorous results-oriented acquiring only will ensure that the project / product quality and progress.
5. limited powers means that the person in charge in the department, there are rewards and punishments power, financial dimensions of power. Imagine a team not reward merit, there have been no penalty team cohesion and combat effectiveness will be high. Financial dimension refers to regulate the atmosphere, the material basis needed to resolve the contradiction, do not expect the team atmosphere right time and space white teeth convince team members and resolve conflicts.
The second factor extension application:
1. subjective awareness of team members, whether the enterprise as a platform, is willing to together and enterprise development. Will is not clear, there is no power. Too much between the lives hand to mouth, but also advise you not to waste time on such a person; make limited resources to tilt a willing group of people, otherwise it is not fair to everyone, but also to a waste of resources!
2. The members of the development model of understanding and a willingness to try new degree of knowledge. Lack of understanding is not terrible, the late professional guidance can be. If members fear change due to expansion caused by new knowledge, and thus refuse to change, we recommend that refer to the first.
Article factor extension application:
External support can come from internal executives, customers, cross-functional departments; a gang of three men to do more with less, not much go into details.
Factors fourth extension application:
The top priority, the core idea of agile. As for how to do, the use of which to pay, it is recommended everyone to search for executive-level recruitment requirements on job sites, one by one in control, the lack of effort to make up.
Constituent elements of agile teams:
1.3-9 people, is the degree of understanding may be;
2. centralized office, face to face;
3.100% of full-time members;
4. The self-management team members;
The pair programming;
6. A cross-functional team members for deployment of resources, receive feedback, act as a role of bridge or ties;
7.T type of experts that can guide research and development team members down, up to guide / recommendations top decision-makers from the costs, benefits and other aspects;
8. Product Owner, this is very important, "scapegoat Man" is a must, a joke ha, fact is ~;
9. resolutely eliminate information silos, to achieve the flow of information, better agility before pushing up.
Long-winded so much, send us a word of advice "before any action, strategy first and then move to results-oriented. SWOT analysis can be used, so that confidence thirty-three analysis."