-
Notifications
You must be signed in to change notification settings - Fork 18
Rules of the Scrum
Material on this page sourced from wikipedia: http://en.wikipedia.org/wiki/Scrum_(development)
Product Owner - Holly The Product Owner represents the voice of the customer and is accountable for ensuring that the Group delivers value to the business. The Product Owner writes customer-centric items (typically user stories), prioritizes them, and adds them to the product backlog. Scrum groups should have one Product Owner, and while they may also be a member of the Management Group, it is recommended that this role not be combined with that of ScrumMaster.
Group - Guillaume The Group is responsible for delivering the product. A Group is typically made up of 5–9 people with cross-functional skills who do the actual work (analyse, design, develop, test, technical communication, document, etc.). It is recommended that the Group be self-organizing and self-led, but often work with some form of project or group management.
ScrumMaster - Aaron Scrum is facilitated by a ScrumMaster, also written as Scrum Master, who is accountable for removing impediments to the ability of the group to deliver the sprint goal/deliverables. The ScrumMaster is not the group leader but acts as a buffer between the group and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster’s role is to protect the group and keep them focused on the tasks at hand. The role has also been referred to as a servant-leader to reinforce these dual perspectives.
Daily Scrum (project status meeting): The meeting length is set to 30 minutes (Scrum Master regulates time).During the meeting, each group member answers three questions: What have you done since yesterday? What are you planning to do today? Any impediments/stumbling blocks?
Sprint review meeting: Review the work that was completed and not completed. Two hour time limit. Each group member must answer the following questions: What went well during the sprint? What could be improved in the next sprint?
Sprint planning meeting: Held just before the beginning of the sprint cycle each month. Group selects what work is to be done. Prepare the Sprint Backlog with specific tasks (and their priority) and assign to group members.
Closing issues -For minor issues, mention that you have committed in the comments -Use the 'has branch' tag to signify development and workaround on larger issues