1.啥叫SCRUM
2. Why use SCRUM?
3. How to implement SCRUM?
4.Scrummaster is what role?
Difficulties 5.SCRUM
1.啥叫SCRUM?
All along, the field of software development in the existence of N in the software development methods, the most common is the waterfall, and from birth横空agile development methods, a result of the controversy Falls VS agile voice has not been消停. And Scrum Also as a quick on behalf of a very distinguished emerged.
Scrum (rugby team fight), software development model is a kind of Agile Development, in a recent epidemic in 2012 up gradually.
Scrum's basic assumption is: as the development of new software products, not the beginning of the definition of software products will be able to order the end of the process, the need for research and development, creativity, trial and error, we do not have a fixed ad hoc processes to ensure success. Scrum software development team into a football team analogy, the supreme goal of a clear, familiar with the development process necessary for the best model and technology, with a high degree of autonomy, closer co-operation and communication in order to solve the challenges of a high degree of flexibility to ensure that each days towards the goal of each stage there is a clear advance. Scrum development process is usually within 30 days (or a shorter period of time) for a stage, by the customers requirements specification of new products started development team and customers in every stage of the selection of the beginning of the complete specification of the development team must make every effort to 30 days after the delivery of results, the team met for 15 minutes every day to check the progress of each member and plans to understand the difficulties and try to rule out the possibility.
Explained below under the terms of the Scrum
backlog: all the tasks can be unpredictable, including functional and non-functional all the tasks.
sprint: the first time or on behalf of the development cycle, generally up to a 30-day period. During this time, the development team need to complete the development of a backlog, and, ultimately, the outcome is an incremental, and can deliver products.
sprint backlog: a sprint cycle task.
scrumMaster: responsible for overseeing the entire Scrum process, the revised scheme member of a team.
time-box: one for the meeting time. For example, the daily scrum meeting each time-box for 15 minutes.
sprint planning meeting: at the start before the convening of each sprint. Usually one day (8 hours). The need for the conference's mission is to: Product Owner and team members will be broken down into small backlog of functional modules, a decision in the forthcoming need to complete the sprint in the number of small functional modules, to determine the Product Backlog this task priority. In addition, the meeting also discussed in detail how it can be completed in accordance with the needs of these small functional modules. The modules developed with an hourly rate of the workload.
Daily Scrum meeting: the development team members held a general for 15 minutes. Members of each development ScrumMaster need to report the three items:
Today the completion of what?
Whether the obstacles?
Is about to do?
Through the meeting, team members can be mutual understanding of project progress.
Sprint review meeting: after the end of each Sprint, the Team will be the outcome of this demonstration of Sprint's work to the Product Owner and other relevant personnel. Generally four hours for the meeting.
Sprint retrospective meeting: Sprint summary. Conference participants for the team of internal staff development. General three hours for the meeting.
2. Why use SCRUM?
Scrum model is characterized by a significant response to change, it can respond to changes as soon as possible. So do many of the domestic outsourcing business overseas customers are asked to use this development method. The changing needs of today demand is A, tomorrow may be completely replaced by B, is God in this age of customers, developers and clients say is not unreasonable, therefore, continuously tracking customer needs and timely in accordance with the demand for change to make corresponding adjustments and changes in the nature of the benefits of that scrum.
3. How to implement Scrum?
(1) Scrummaster the entire product backlog into the Sprint Backlog, the Sprint Backlog is the human and material resources in accordance with the present conditions can be completed.
(2) Scrummaster held sprint planning meeting, division of Sprint is required to determine the task of tagging the priority of tasks and allocated to each member. Attention to the task here is based on an hourly basis, not by the person days.
(3) into the development cycle sprint, in this cycle, the need to convene a day Daily Scrum meeting.
(4) the end of the entire cycle sprint, held a Sprint review meeting, the results presentation to the Product Owner.
(5) team members held the last Sprint retrospective meeting, summing up issues and experience.
(6) This cycle, in accordance with the same steps for the next Sprint.
4.Scrummaster is what role?
There are many definitions of Scrummaster, but I think he is the definition of the role, rather than the definition of jobs.
The definition of the following explanation is also consistent with this view: Scrummaster on the role of the task is to safeguard the accessibility of the scrum process operation, and its role in leadership and management does not lie, but rather to safeguard the process. He is not a management decision-makers not involved in the development of the actual operation, the only process of its jurisdiction.
Difficulties 5.SCRUM
1, Sprint Backlog identified in the team to rely on the experience and the degree of实诚, lack of experience may lead to a large selection bias may be deliberately not reduced实诚(that is, take any punches either), if inexperienced, then it will be a lack of awareness of potential risks and to grasp the consequences of the failure of the final result. If the team selected a Sprint Backlogs and team development capabilities of Sprint match, then Scrummaster developers have the responsibility to urge the development of responsibility, which is the scope of his powers and responsibilities: punishment and reward.
2, burn maps there is no objective basis to rely on subjective judgments
3, Spring Backlog size of any objective measure, can not be shared between teams in a number of measurement methods. Sprint Backlog directly mapped to the scale of measurement were days, it is estimated will be a lot of psychological pressure (estimated at more like the work is to develop a commitment to staff, developers also have their own personality differences, no one do not want to give great pressure in the to work under)
Reference URL:
google agilechina







