Category: Scrum

Sprinting is running over a short distance in a limited period of time. It is used in many sports that incorporate running, typically as a way of quickly reaching a target or goal, or avoiding or catching an opponent. A sprint is a time box. Each sprint has a start and end date during which a set of selected user stories have to be completed and confirmed. The following image shows you the key elements of a sprint, which includes a set of user stories, the scrum members involved, the assignment of work, the duration and end date (top-right corner).

Getting the preparation right and keeping a close watch on the mechanics is a great start but the biggest risk of derailment is from people problems. Planning is all about the interaction between the participants, so there’s plenty that can and will go wrong:

Although applied commonly to IT projects, scrum is equally useful in non-IT projects. Scrum is more about team dynamics and work culture than about any specific project management practice.

The Scrum Process Canvas is a Scrum management tool. It presents actionable Scrum activities in a one-page process canvas. Team members perform activities to manage and complete software projects. The Scrum process Canvas is fully customizable, allowing you to add additional activities (such as certain meetings) and process deliverables (such as domain-specific logs) to the Scrum process to meet your specific project needs.

According to Scrum.org, a Sprint is a “month or less framework within which a “completed”, usable and potentially releasable product increment is created. The duration of a Sprint is consistent throughout the development effort. A new Sprint begins immediately after the previous Sprint ends…….

As described in the Scrum Guide, the Scrum framework consists of Scrum teams and their associated roles, events, artifacts, and rules. However, Scrum rules are not as easy to identify as roles, events, and artifacts. This list attempts to extract these rules for conducting Scrum events and provide them as a supplemental resource to the Scrum Guide.

The Sprint Retrospective occurs after the Sprint Review and before the next Sprint is scheduled. For a one-month sprint, this is a three-hour meeting at most. The retrospective meeting is basically an “improvement” meeting to find ways and means to identify potential pitfalls, past mistakes, and seek new ways to avoid them, with all people in attendance – product owners, Scrum Masters, development team members, and optionally with stakeholders.

The sprint planning meeting is held before the sprint begins. The purpose of this meeting is to define the sprint plan and set sprint goals. The sprint plan includes agreeing on the number of backlog items in the sprint that will be the responsibility of the development team, as well as determining the goals for the current sprint and sprint backlog.