Scrum description:

Link: http://scrum.org
Roles:
Product Owner
In Scrum, the Product Owner is responsible for communicating the vision of the p
roduct to the development team.
He or she must also represent the customer s interests through requirements and pr
ioritization.
Because the Product Owner has the most authority of the three roles, it s also the
role with the most responsibility.
The Product Owner is the single individual who must face the music when a projec
t goes awry.
Scrum Master:
The ScrumMaster acts as a facilitator for the Product Owner and the team. The Sc
rumMaster does not manage the team. Instead,
he or she works to remove any impediments that are obstructing the team from ach
ieving its sprint goals.
In short, this role helps the team remain creative and productive, while making
sure its successes are visible to the Product Owner.
The ScrumMaster also works to advise the Product Owner about how to maximize RO
I for the team.
Development Team:
In the Scrum methodology, the team is responsible for completing work.
Ideally, teams consist of seven cross-functional members, plus or minus two ind
ividuals. For software projects,
a typical team includes a mix of software engineers, architects, programmers, a
nalysts, QA experts, testers, and UI designers.
Each sprint, the team is responsible for determining how it will accomplish the
work to be completed. This grants teams a great deal of autonomy,
but, similar to the Product Owner s situation, that freedom is accompanied by a re
sponsibility to meet the goals of the sprint.
Events:
Sprint Planning:
At the beginning of the sprint cycle (every 7 30 days), a "Sprint planning meeting
" is held:[14]
Select what work is to be done
Prepare the Sprint Backlog that details the time it will take to do that work, w
ith the entire team
Identify and communicate how much of the work is likely to be done during the cu
rrent sprint
Eight-hour time limit [10]
(1st four hours) Entire team: dialog for prioritizing the Product Backlog
(2nd four hours) Development Team: hashing out a plan for the Sprint, resulting
in the Sprint Backlog
Daily Scrum Meeting:
Each day during the sprint, a project team communication meeting occurs.
This is called a "stand-up meeting" (or Daily Scrum (meeting)) and has specific
guidelines:
All members of the development team come prepared with the updates for the meeti
ng.

The meeting starts precisely on time even if some development team members are m
issing.
The meeting should happen at the same location and same time every day.
The meeting length is set (timeboxed) to 15 minutes.
All are welcome, but normally only the core roles speak.
During the meeting, each team member answers three questions:
What have you done since yesterday?
What are you planning to do today?
Any impediments/stumbling blocks? Any impediment/stumbling block identified in t
his meeting is documented by the Scrum Master and worked
towards resolution outside of this meeting. No detailed discussions shall happe
n in this meeting.
End meetings (Sprint Review and Sprint Retrospective)[edit]
At the end of a sprint cycle, two meetings are held: the "Sprint Review Meeting"
and the "Sprint Retrospective".
At the Sprint Review Meeting:
Review the work that was completed and the planned work that was not completed
Present the completed work to the stakeholders (a.k.a. "the demo")
Incomplete work cannot be demonstrated
Four-hour time limit
At the 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
This meeting is facilitated by the Scrum Master
How we used: