Antecedent review, we learned that on a background of agile origin, declarations, principles; above also made preliminary comb. Today we begin to uncover the second layer of "life cycle" agile mystery. Reference to "life cycle" Detailed everyone certainly no stranger to IT is true that languages: C, C ++, C #, JAVA and so will have its own life cycle, everyone also play a thief slipped. Now today, life cycle development do not speak the language, the agile life cycle.
Mentioned agile project life cycle, from the first traditional talking about. Whether we are accustomed to do first program (research needs) -> Document Analysis -> OK Requirements -> Design (prototype) -> OK -> Encoding -> test -> implementation of delivery -> Normandy D-Day (beginning of a nightmare); or such is the demand -> design -> implementation -> Normandy D-day to reproduce.
See here, do not be surprised, why I repeat mention Normandy D-Day, many in the film, which is portrayed as the heroic action by the world famous. But I want to say is, IT sector do not advocate such heroic and tragic. We do not promote personal independence war, focus on teamwork and customer cooperation + + = continuous flexible policies have output quality.
Team takes many forms, all kinds of people, there are a variety of embodiments, we want to summarize the characteristics of a successful project / failure to form an effective team management. Here, could not help but say: "Do not fear failure, failure to face, from which extracted for team members to learn, something right experience and methods change.
We can see from the above, I mentioned two methods can be summarized to "predictive life cycle", what is the predictive life cycle? This is a traditional method, and ASP as old, that is a lot of planning in advance, and then once performed continuously until the end of the project code. In this process, there will be no commercial or function of delivery. This method is effective, there are drawbacks. Here we talk about malpractice, imagine such a scenario, under Group A Division IT, A day received instructions and do a OA system. OK, department heads began to take the "Analysis -> Design -> Create -> test -> delivery" such a process. Logically there is no problem, but only in the IT department to deliver A moment before we know the function of the software. During this process A I have been thinking, what these people are doing? It is not lazy? Progress can not know, then, bonuses, KPI how to count? Head of IT personnel in the unstable atmosphere, to apply for funding or time A lively atmosphere, A agree? A beginning is often the IT department of the very trust, the lower the confidence in the future, naturally all kinds of benefits will gradually decrease. Team members will feel squeezed by ruthless, department heads also very wronged, long, low efficiency, low morale, staff mobility. We have talked about the festival team the most important, the brain drain product quality is often a big discount. The final two results, one person in charge to resign; 2. serious product does not meet expectations, the latter constantly changes, people complaining, time dragged on, the project ended in abortion .....
Iterative Life Cycle: This method allows for feedback unfinished work to change and modify work methods, project high complexity and frequent changes applied in this way, nature "waterfall \ Predictive life cycle" is also suitable for this ways. Advantage of feedback - change, schedule control, quality can be controlled. I believe that many companies in this way.
Based on the first way, we change the next story; A small successor predecessor leader, responsible for project development. A small pit based on past stepped on, decided to use regularly delivered to the headquarters, even if the software is not complete, but also delivery.
A small we take a look at how it is done, each time the delivery will be reported in the area where the group:
1. This periodic update something.
2. What are the participants.
3. What are testers.
4. What's next forecast will be delivered.
Harvesting Nature praised the Group, the Group know the status of control, increasing the confidence of the IT department, the Group / customers will be more to let the team play. I always thought that "a good leader, to act with a policy means. Keen perception of the team, customer trends, find some time to adjust by means of the exceptions, we will maximize the benefits, rather than stepping on his men to climb .. blindly to cater to the customer, the higher will be overturned. "
Pulling away, there is a benefit that, by this method, project development process, will not deviate from the direction of guaranteed quality. Members will not be endless repair unanticipated demand, deepen the crew confidence in the product, the team of leaders, and gradually over-like agility. This is the incremental life cycle.
Another story, the last one. A small through the "incremental life cycle," we found that players have become accustomed to this highly efficient way to work and gain deep. A small decided to try a method, which uses the story, story split into individual chapters, R & D through the card, the time box.
Truly customer / leadership / team members to work immediately clear, team members take the initiative to receive daily tasks, schedule management quality through billboards, software and other means. Scrum / person in charge must be reasonable allocation of time box, strictly controlled in accordance with the agreed time. A small know that people are inert, to question everything, so all the time in the A small crew members deployed in need of work, strict, really do "leadership assignment -> members receive" to " people take the initiative got me to task, receive - excessive> feedback ", everyone is the owner of a small team, even if the person in charge of a servant leader. It is through "demand -> Analysis -> Design -> Create -> Test" in this way based on the "life-cycle agile iterative manner", will demand isolation, limiting WIP, A small office to obtain a higher step of the upgrade, the team revenue staff have also been a big adjustment, client / interests of the company to maximize and achieve win-win situation.
Of course, there are process-based Agile life cycle: some functions to work from TODO List of mention, and not according to work schedule based on iteration. Value of the work flow is manifested, limit the number of WIP in the system, to facilitate the timely detection of problems, reducing the need to rework the table more style, team, business party decides planning, product evaluation and review.
"Demand Change -> Analysis -> Create -> test -> limit the number of WIP" process development, process is characteristic of agile lifecycle. WIP is the first to propose and Toyota applications, WIP will talk about in a special course, not be repeated here.
| 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 |
Two important concepts of agile iterative and incremental life cycle when:
Iteration: like sketches or copy, by every delivery, repeated truth-seeking process, the quality of the software / project has become increasingly clear, so as to enhance the quality of software / project.
Incremental: Like puzzles, each delivery a little more, by accumulating the number of features that make the quality of software / project has become increasingly clear, so as to enhance the quality of software / project.
Believe that here, you may have questions, talk so much, in the end which is suitable, you can not use both? Congratulations, you have entered the agile development model.
Mixed life cycle: the project is not using a single method, doctors to diagnose patients by "look and smell", the project is no exception. It needs through a variety of combinations, according to the different periods of agile way to set up for the team. Example: "forecast, iterative, incremental, agile: Iterative, incremental" or a combination of coordination (servant) style approach, Scrum, Kanban, XP and other elements to build a cross-functional approach to Steering Group members, including sprint plans, Hitachi will, review, review / re-set agile project development approach. Goal of project management is under certain circumstances, the use of the best way to create maximum business value.
Finally, long-winded one, "there is no fixed mode, only to meet a variety of combinations of the moment", level of experience of the team, the cooperation of customers, projects require more teamwork, team members lack experience in agile methods, etc. should be considered as the elements of.
"In my long life, how many small bullets and shrapnel fell on my body, coming from nowhere, struck my heart, so I left a lot of bullet wounds.
And when my life is nearly twilight years, these countless wounds began to heal.
In a place that once injured, it is thought to grow out. "" The Birth of thinking "comes Quotations