The Scrum notes.

Roles

Pigs

• Scrum Master:
• Ensures the Scrum framework is followed.
• Product Owner:
• Product's stakeholders and the voice of the customer.
• Create product backlog.
• Negotiates priorities.
• Defines releases.
• Development team (From three to nine members):
• Analysis
• design
• Development
• Testing
• Technical writing

Chickens

• Stakeholders
• Managers

Workflow

Before Start

• A sprint (or iteration) is the basic unit of development in Scrum. Each sprint is between one week and one month, usually two weeks.
• You must complete the work include development, testing, and document of the requirements at the end of the sprint.

Sprint Planning Meeting

• Four hours for a two-week sprint.
• Select highest priority requirements in the product backlog that can be completed in one sprint.
• First, the development team, scrum master and product owner select the requirements.
• Second, the development team discuss the details for each requirement and uses the planning poker to estimate the story points.
• Third, if the sprint spills, remove the demands. On the contrary, if the sprint can not be filled, add more demands.

Daily (Stand-up) Meeting

Each team member answers three questions:

• What did I complete yesterday?
• What do I plan to complete today?
• Any problems to impede me to complete the work?
• Scrum Master needs to write down these problems.
• Development team needs to log work.（e.g. use JIRA）

See: Problems that are easily encountered in daily meetings.

Sprint end

Sprint Review Meeting

• Two hours for a two-week sprint.
• Presents the completed work to the stakeholders.
• Discuss what requirements that stakeholders will be expected to complete at next sprint.

Sprint Retrospective Meeting

• One and a half hours for a two-week sprint.
• The meeting is facilitated by the scrum master.
• What is the good part during this sprint?
• What is the worst part during this sprint, and how to ameliorate?