Sample Solution

• Training the Scrum Team in organizational environments wherein Scrum is not yet fully implemented
3. ScrumMaster Services to the Organization
• Facilitating and planning adoption and implementation of Scrum
• Helping employees and stakeholders understand and enact Scrum and empirical product development
• Causing change that increases the productivity of the Scrum Team
• Working with other ScrumMasters to increase the effectiveness of the application of Scrum in the organization
EVENTS (How SCRUM works?)
Scrum Process Framework can be viewed by means of a series of events and the corresponding artifacts. These events are time-boxed events which means that in a project, every scrum event has a predefined (maximum) duration. The vital events of scrum are:
• The Sprint
• Sprint Planning
• Daily Scrum Meetings
• The Sprint Review
• The Sprint Retrospective
The Sprint
During a Sprint event, a working product Increment is developed. The duration of this event is usually two weeks or one month, and this duration remains constant for all the sprints in the project. We cannot have different durations for the different sprints in a particular project. A new Sprint follows immediately after the previous Sprint is completed.
The Sprint Goal is an objective set for the Sprint during the Sprint Planning meeting. The scope of the sprint is clarified and re-negotiated between the Product Owner and the Team as more about the requirements is learned.
A Sprint should be cancelled in case the Sprint Goal becomes obsolete. This might occur if the organization changes its working or if market or technology conditions change in the industry. It is important to note that a sprint can be cancelled only by product owner, though others also have an influence on the same.
Since the Sprints are of short durations, cancellation during a sprint doesn’t make much sense. Also, since sprint cancellations consume resources, for getting re-organized into another Sprint it is difficult and uncommon.