Scrum流程(一)

Scrum流程(一)

Note of <Scrum(development) - Wikipedia.pdf>

Characteristics
The main roles in Scrum are:
1. the "ScrumMaster", who maintains the processes(typically in lieu of a project manager)
2. the "Product Owner", who represents the stakeholders and the business
3. the "Team", a cross-functional group of about 7 people who do the actual analysis, design, implementation,testing,etc.

Roles
All roles fall into two distinct groups----pigs and chickens. Joke:
A pig and a chicken are walking down a road. The chicken looks at the pig and says, "Hey, why don't we open a restaurant?" The pig looks back at the chicken
and says, "Good idea,what do you want to call it?" The chicken thinks about it and says,"Why don't we call it 'Ham and Eggs'?" "I don't think so," says the pig,
"I'd be commited, but you'd only be involved."

Pig roles
ScrumMaster(or Facilitator)
   ScrumMaster is not the leader of the team but acts as a buffer between the team and any distracting influences. A key part of the ScrumMaster's role is to
protect the team and keep them focused on the tasks in hand.

Team
   The team has the responsibility to deliver the product. A team is typically make up of 5-9 people with cross-functional skills who do the actual work(design,develop,test,technical,communication,etc).

Product Owner
   The Product Owner represent the voice of the customer. The Product Owner writes customer-centric items(typically user stories), prioritizes them and then places them in the product backlog.
   A Product Owner can be a member of the Scrum Team but cannot be a ScrumMaster.

Chicken roles
Stakeholders(customers,vendors)
     These are the people who enable the project and for whom the project will produce the agreed-upon benefit, which justify its production. They are only
     directly involved in the process during the sprint reviews.

Managers
     People who will set up the environment for the product development organizations.

Meetings
Daily Scrum
     This is called a "daily scrum", or "the daily standup".This meeting has specific guidelines:
      * The meeting starts precisely on time.
      * All are welcome, but only "pigs" may speak
      * The meeting is timeboxed to 15 minutes
      * The meeting should happen at the same location and same time every day
During the meeting,each team member answers three questions:
     * what have you done since yesterday?
     * what are you planning to do today?
     * do you have any problems preventing you from accomplishing your goal?

Scrum of scrums or Post-scrum
    held each day, normally after the daily scrum.
       * These meetings allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration.
       * A designated person from each team attends.

    The agenda will be the same as the Daily Scrum,plus the following four questions:
       * What has your team done since we last met?
       * what will your team do before we meet again?
       * Is anything slowing your team down or getting in their way ?
       * are you about to put someting in another team's way?

Sprint Planning Meeting
    At the beginning of the sprint cycle(every 7 - 30 days), a "Sprint Planning Meeting" is held.
      * Select what work is to be done
      * Prepare the sprint backlog that details the time it will take to do that work,with the entire team
      * Identify and communicate how much of the work is likely to be done during the current sprint
      * Eight hour time limit
              (1st four hours)Product Owner + Team:dialog for prioritizing the Product Backlog
              (2nd for hours) Team only: hashing out a plan for the Sprint,resulting in the Sprint Backlog

At the end of a sprint cycle,two meetings are held: the "Sprint Review Meeting" and the "Sprint Retrospective"

Sprint Review Meeting
    * review the work that was completed and not completed
    * present the completed work to the stakeholders(a.k.a. "the demo")---a.k.a as known as
    * incomplete work cannot be demonstrated
    * four hour time limit
Sprint Retrospective
    * All team members reflect on the past sprint
    * make continuous process improvements
    * two main questions are asked in the sprint retrospective:
           What went well during the sprint?
           What could be improved in the next sprint?
    * Three hour time limit