Scrum Roles
Scrum Master-- project leader, project manager
Protection team from outside interference, is the team leader and facilitator, responsible for Scrum teams improve the efficiency, control "review and adaptation" cycle of Scrum. The investment maximize output with the Product Owner, he ensures that all stakeholders can understand the concept of agility and agile respect.
Team-- developers, testers, graphic design, DBA and other functions of the whole team
Team responsible for delivering the goods and responsible for the quality, team work together with all those who made product needs, including customers and end users, and jointly create a Product Backlog. According to the consensus of the team to create a functional design, test Backlog items delivered products.
Product Owner-- product owners, product managers, operations staff
Drive from a business perspective projects, dissemination of clear vision products, and define its main features. Product Owner main responsibility is to ensure that only the development team for the organization's most important Backlog items to help the team in the Sprint to complete their work, do not interfere with team members and the team quickly provide all the information needed.
User-- end users, operations personnel, system personnel
Many people are likely to be the end user, such as marketing staff, the real end-user, the best experts in the field, it could be because of their expertise and IT consultant was hired. End users based on their knowledge of the business definition of the product, and inform the team of my expectations request.
Manager-- management, investors
Management must build a good environment for the Scrum team to ensure that the team can work well, when necessary, they will be together again with Scrum Master organizational structure and guidelines.
Customer-- customers, system personnel, operations personnel
Customer demand is the person proposed for the Scrum team, she will sign a contract with the organization to develop products. Generally speaking, these people are senior managers in the organization, responsible for purchasing software development capabilities from external software development company. In the company's internal product, the person in charge of the project budget is approved by the customer.
Scrum the output thereof
Product Backlog - Backlog items to be developed, the backlog of tasks.
Product Backlog includes all content to be delivered, the contents of the order based on the value your business needs arrangement, each Backlog priority is adjustable, you can increase or decrease the demand, so the product Backlog will continue to drive maintained in accordance growing.
Sprint Backlog - Sprint intended to "sprint" means iterations, the length is typically one to six weeks.
Sprint before the start of the definition of this "Sprint Backlog" Sprint to be discussed, from which this Sprint to be done "has been set Product Backlog".
Has been set is the product of Product Backlog Sprint Planning Meeting, which defines the team accepted the workload throughout the course Sprint will remain unchanged.
User Story, Task-- user stories, tasks
By User Story to describe the items in the Sprint Backlog, User Story is a brief description from the user's point of view a function module of the system made. A User Story describes the project in a small function, and will have little effect after the completion of this function, or create any value for customers. User Story of a size and complexity should be completed in one of the appropriate Sprint. If the User Story is too large, it may lead to the development across several Sprint, this time should be the User Story decomposition. In order to timely and efficient completion of each Story, the Scrum each team will Story into several Task. Each Task, preferably not more than eight hours, to ensure that a working days to complete, if the Task longer than eight hours, it shows the Task division problems, we need special attention.
Obstacles Backlog-- list of questions, the backlog of pending transactions.
He cited the progress of all problems within the team and team-related projects and hinder, Scrum Master need to ensure that all obstacles Backlog in question have been assigned and can be resolved.
General meeting rules
basic requirements
• Every meeting should start on time, end on time.
• Each meeting will take the form of open, everyone can participate.
Pre-preparation
• All people must be invited in advance to attend, so that they have time to prepare.
• Send meeting outline with meeting the goals and intentions.
• Reserve all the resources needed for the meeting: room, projectors, flip charts, presided over the equipment, and other things needed for this meeting.
24 hours ago • will send reminders.
• Prepare flip chart with conference rules.
Conference to promote
• When the discussion, the meeting must be present to promote the people. He could not participate in specific discussions, but he needs to pay attention to the process of discussion, if the discussion participants lose focus, he will have to be brought back to the formal discussion.
• promote the goals and intentions of people to show the meeting.
• When necessary, to promote people may agree to a written meeting notes.
• Promoting people can record the views of the team, or a team of professors how they record the document; and to promote people may be recorded on a flip chart, a visual dialogue.
• promote people will be ending the meeting, and a very brief review.
Output Conference
• Use flip charts or handwritten instructions to record documents, to the content on the whiteboard and flipchart pictures.
• meetings and everyone must convey a clear common perception of the outcome of the meeting.
Allow the team to sit together!
• Everyone lazy move, try to make "Product Owner" and "full-functional teams" are sitting together!
• hear each other: everyone can talk to each other, do not shout, do not have to leave their seats.
• see each other: everyone can see each other, can see the task board - do not have to be close enough to see the content, but you can at least see a ballpark.
• Isolation: If your whole team stood up suddenly, spontaneously formed a fierce design discussions, anyone outside the team will not be disturbed, and vice versa.
Team building
• Scrum team the best toll at "5-9" people.
• All functions of the team: Development Group (background development, front-end developers, testers --3 to 8 people), Scrum Master (Project Manager), Product Owner
• Part-time team members: artists, DBA, operation and maintenance
Daily Legislative Council (Daily Standup Meeting) - recommend starting before work
Purpose of the meeting
• Team work in a meeting to plan, coordinate its daily activities, you can also report and discuss the obstacles encountered.
• task board can help the team focus on top of daily activities, to update the task board and burndown charts at this time.
Components
• task board, sticky notes, marker
• Tip: ScrumMaster Do not stand in front of or next to the team task board, do not create an atmosphere similar to teachers and teaching.
basic requirements
• Members: team, Scrum Master
• unable to attend the team members to be represented by a companion.
• Duration / Venue: 15 minutes a day, same time, same place.
• Tip: team members while listening to the speaker, should be thinking about this question: "? How can I help him do it faster."
Output Conference
• team clearly know each others' work, the latest work progress chart.
• get the latest "obstacle Backlog"
• Get the latest "Sprint Backlog"
Meeting procedure
• team gathered in the next storyboard, you can enclose a ring.
• Starting from the first to the left, that he is now working to complete the team partner.
• The members of the task then the task board in the correct column.
• If possible, the member can select a new task, cross it into a "work in progress" column.
• If the member experience problems or obstacles, we should report it to Scrum Master.
• Each team member Repeat steps 2 through 5.
Everyone three questions:
• When the last meeting of the task which has been completed? : From the task "Processing" state to the "completed" state. - today completed what?
• Before the next meeting, what you plan to complete the task? : If the task status is "pending" to "Processing" state. If the task is not in the Sprint Backlog, add this task. If the task is not the day to, this task subdivided into multiple tasks. If the task can be completed in one day, the task status is set to "Processing." If the task status is already "being processed", asked whether the problems have hampered the task is completed. - What are you doing tomorrow?
• What is the problem hindered your development? : If there is hinder your development progress of the problem, adding to the disorder to disorder the Backlog. - Today encountered any problems?
Precautions
•do not be late
• Do not exceed the time limit
• Do not discuss technical issues
• Do not change the topic of the meeting
• Do not participate in the preparation of the case
• Scrum Master for team members do not move a task card, do not update burndown for the team.
• Scrum Master Do not ask questions, do not report to the team members Scrum Master or management personnel.
• If a representative is unable to attend the meeting, the team needs to be notified, and to find.
TaskPad
• Task plate collection select good Product Backlog and Sprint Backlog, and visually show.
• task can only be maintained by the board team, using different colors of "sticky notes" to distinguish developer, or accept the name task on "sticky notes" to write.
• Use a large white board, you can also use the software.
There are four task panels:
• Choose a good Product Backlog: according to priority, in the current team will be working in the Sprint Product Backlog entry or story on the column.
• To be completed tasks: To complete a story, you have to complete some tasks. In the Sprint planning meetings, or during the current Sprint, collect all new tasks you need to complete specific Backlog items and place them in the column.
• Work in progress: When the team members begin a task, he will be the task corresponding card into the "work in progress" column. From the beginning of the last daily Scrum meetings, did not complete the task will be placed in the column, and mark on it (usually a red dot). If a task in the "pending task" column in which more than one day, as far as possible the task into smaller parts and then put the new tasks that column, remove it belongs major task card. If a new task can not be completed because of an obstacle, you'll get a red dot marks, Scrum Master will write down a barrier.
• Complete: When a card to complete the task, the completion of the members of this task will be placed in "Done" column and start selecting the next task card
Burndown
• To track the progress done by the team, burndown horizontal axis represents the total time for the entire Sprint vertical axis represents the Sprint all tasks, the unit can be hours, days and other people. Generally, the burndown have "Sprint burndown" and points "Release burn Diagrams".
• Team burndown updated daily.
• If burndown been rising state, or after a period of time Sprint, Y values on the Sprint burndown still with Sprint started almost the same time, it shows too much of the Sprint Story, to remove some of the Story Sprint to ensure that this can be successfully completed. If Sprint Burndown decline rapidly, for example, Sprint has just more than half of the Y value is close to 0, then the Sprint assigned tasks too, but also add some tasks to come. In the Sprint planning meeting, if the team is about to do the task of understanding and awareness is not sufficient, it is likely to result in both cases. (Exercise self estimated time of team members)
• To facilitate team burndown update, no need to make it look stunning, do not be too complex, difficult to maintain.
Release Burndown: Scurm record the progress of the project, and its horizontal axis represents all Sprint this project, and the vertical axis represents each Sprint before the start of unfinished work, its unit may be a (Story of the number), and other person-days .
Sprint planning meeting - the first part (morning)
Purpose of the meeting
• The work of the Conference to analyze the main purpose is to understand in detail what the end-user in the end to, product development teams can learn more about the real needs of the end user from the conference. At the end of the meeting, the team will decide what they can deliver.
• Product Owner in the pre-meeting preparation: Entry of the demand (user stories), prioritization, recently one or two iterations of function most want to see. Pre-meeting preparation is essential to help the product owner to sort things out, and will not change frequently raised during the iteration, add or delete stories.
basic requirements
• iteration plan will be held on the first day of each iteration, the objective is to select and to estimate the current iteration of work items.
• Only team members can decide how many teams can receive Backlog items in the current Sprint work.
Components:
• After estimating and ordering the Product Backlog.
• flip chart, marker pens, scissors, glue, sticky notes, whiteboards, pencils and crayons.
• holiday schedule, contact details of key personnel information.
• Participants members: team members, Scrum Master, the Product Owner
Duration: the Sprint, the weekly meeting occupation time of 60 minutes, the meeting was held in the morning, so there is the possibility of convening Sprint planning meetings on the same day in the second part.
Output Conference
• Choose a good Product Backlog entry.
• Backlog needs of each entry.
User Acceptance Testing • Backlog of each entry.
Meeting procedure
• Product Backlog starting with the first entry (story).
• Discuss the Product Backlog entry to in-depth understanding.
• Analyze, clear user acceptance testing.
• Find non-functional requirements (performance, stability ...)
• find acceptance conditions.
• the need to clarify "done" to what level.
• Get a clear understanding of all aspects of Backlog items.
• a correlation graph plotted required deliverables, comprising the flowchart, the UML diagram, hand-drawn sketches, UI screen design.
• back to Step 1, select the next Backlog items.
Process Review: Ask the team can quickly answer the following questions, need only brief answers to questions: "? We can finish first in the Sprint Backlog items in it," If we can get a positive answer, then continue to ask the next Backlog items, until the last analysis Backlog items have been finished. - Next, take a break. After the break, the above-described process for a next deployment Backlog items.
The end of the process:
• to leave before the end of the first part of the Sprint Planning Meeting for 20 minutes.
• ask again - this time to be more serious, the official: "Can you complete the first Backlog items, ... Second, ...?"
• If the team believes they can no longer accept more Backlog items, then stop.
• Now it is a very important step: away Product Owner, in addition to team owner and Scrum Master, and had to leave.
• After everyone else left, then asked the team: "Really - you believe they can complete the list?"
• hope the team can now briefly discuss to see if they think they can finish in the end how much work.
• The results of the Product Owner and the end-user communication.
Note: Do not change the size Backlog items, do not estimate the task.
Sprint Planning Meeting - Part II (afternoon)
Purpose of the meeting
• The meeting of the Working design-focused, product development teams can complete the design work for the solution they want to achieve, at the end of the meeting, the team know how to build them in the current Sprint features to be developed.
basic requirements
• Only product development team in order to develop solutions outside, architect or other teams are just invited to help the team.
Components:
• be able to help the team build solutions for people in the Sprint, such as vendors or people from other teams.
• Choose a good Product Backlog entry.
•flip chart......
Note: Do not estimate the task, do not assign tasks.
Output Conference
• application design, architectural design, related chart
• Make sure the team knows how to complete the task!
Meeting procedure
• Backlog starting with the first entry.
• View charts, for determining the correct understanding of customer needs.
• Backlog items around the design, and similar based on the following questions: • What we need to write an interface?
• What kind of architecture we create?
• What we need to update the table?
• What we need to update or components written?
•......
When the team know exactly how they should develop this feature, you can turn to the next Backlog items. In the last 10 minutes of the meeting, team members use sticky notes to write the initial task. This helps team members know from where the next job to carry out, these tasks on the task board.
Duration: After the completion of the first part of the Sprint Planning Meeting, convened the meeting. Lunch can be used as two meetings of a longer rest. But Sprint plans to complete the first part of the same day, the Sprint, the weekly meeting occupation time of 60 minutes.
Estimating conference - Sprint merged into the second part of the meeting depending on the project
Purpose of the meeting
• Strategic planning to do, you need to know Backlog items in size, it is necessary to enter the version planned; if you want to know the team in a Sprint can be completed much work, this data is also necessary.
• Team members can know from the conference in the next phase of the project what will happen.
basic requirements
• Only team to make estimates, Product Owner (Product Owner) need to be present to help determine whether certain user stories into smaller stories.
Components:
• Product Owner Product Backlog scheduled according to the order of business value.
• staff need to attend: Team, Product Owner, User, Scrum Master
Precautions:
• Do not estimate the size of the workload - only team to do so.
• Product Owner does not participate estimates.
Meeting procedure
• Prodcut Owner wants to show her entry Product Backlog estimated.
• Planning Poker team used to estimate Backlog items.
• If a Backlog items too large, you need to put the next or subsequent Sprint, the team will divide the large Backlog Backlog entry to a small number of entries, and the new Backlog items are estimated using planning poker .
• re-evaluate the current Backlog is not complete, but it might be completed in the next three Sprint entries.
Duration: The meeting time is limited to no more than 90 minutes. If Sprint lasts longer than a week then each Sprint estimates hold two meetings more appropriate.
Output Conference
• After estimating the Product Backlog.
• smaller Backlog items.
Poker estimate
Specific steps:
• Everyone estimates their independence after the dark cards, listen with open password cards.
• greatest value and the smallest PK, can refer other people to attend.
• After re-discuss the cards and flop.
• Repeat the process until the results are close.
common problem
1, Why the task to be distributed to groups rather than individuals?
A: The fear of the wrong brand can not tell why, so even if he does not do this function in the future, this feature is also very understanding.
2, why not let the last collar tasks themselves estimate?
A: Because he does not know, probably because of a code is available, do not know a software does not work .... but choose the wrong implementation.
3, why do not we adopt the master estimates that he is not the most powerful it?
A: The master idea is often the disciples could not understand, for example, why not stay in her country but had to Buddhist sutras like the common estimate is to let you control your own implementation methods and master the differences in the process of thinking.
Sprint Review Meeting (Review Meeting)
Purpose of the meeting
• Scrum team in a meeting to show to the end user work product, team members hope to get feedback, and to create or change the Backlog items.
basic requirements
• Sprint review meeting allows all participants to try new features exhibited by the team.
Components
• There may be incremental product release, showing by the team.
Output Conference
• feedback from end users.
• Backlog of barriers to enter.
• Team Backlog input.
• feedback from the team generate input for the Product Backlog.
Duration: 90 minutes, at the end of the Sprint.
Meeting procedure
• Product Owner welcome to participate in the Sprint Review Meeting.
• Product Owner to remind you about the purpose of this Sprint: Sprint goal, Scrum teams selected to develop the story in this the Sprint.
• Product development teams demonstrate new features, and allows end users to try new features.
• Scrum Master advance the proceedings.
• End-user feedback will be recorded by the Product Owner and / or Scrum Master documented.
Precautions:
• Do not display products increments impossible released.
• Scrum Master not responsible for displaying the results.
• Do not show team for Product Owner.
Sprint reflection meeting (Retrospective Meeting)
Purpose of the meeting
• The meeting corresponds metaphor: medical diagnosis! Its purpose is not to find a cure plan, but to find out what needs improvement.
Components
• Participants: team members, Scrum Master
basic requirements
• learn from the past and guide the future.
• improve team productivity.
Precautions
• Do not allow management personnel to participate in the meeting.
• Do not discuss things found outside the team.
Output Conference
• Backlog of barriers to enter.
• Team Backlog input.
Duration: 90 minutes, the first few minutes after the Sprint Review Meeting.
Meeting procedure
• Prepare a written "in the past which did a good job?" Wall chart.
• Prepare a written "What should be improved?" Wall chart.
• Draw a line with a time of start and end dates.
• Give each team member issued a stack of sticky notes.
• Start Review.
• Make a safe practice.
• a collection of facts: sticky notes issued by constitutes a timeline. Each team member (including Scrum Master) on each sticky notes written on an important event.
• "What are doing well in the past?": The process of collecting facts to take the same, but this time put sticky notes on a prepared flip chart.
• Make a separator to distinguish between "past which did a good job," and the next thing you want to output.
• "What should be improved?": Be like that "in the past which did a good job."
• sticky notes will now be grouped:
• What can we do enter the "Team Backlog of.
• What's out of our control? "Backlog of barriers to entry.
• sort the list based on the views of two team members.
• The two lists as the first part of the second portion of the input of the next Sprint Planning Meeting Sprint and Sprint planning meetings, and decide how to time to process the information on these findings.
来自 <https://blog.csdn.net/inny100_100/article/details/54633757>