Scrum Sprint

  • Sprint is a container that contains all other events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective).
  • It’s the core Scrum event during which all the work is done.
  • Time-box for the sprint is 1 month. The length of the sprint can change however, it is not recommended to change it often.
  • The sprint should be long enough to meet the sprint goal, but short enough for the sprint goal to remain up to date, with respect to changing environment.
  • Shorter sprints provide a higher frequency of improvements and learning, reducing the risk and the cost.
  • The main benefit of the sprint is a reduction of risk and the distribution of costs.
  • The sprint can be canceled if the goal of the sprint becomes obsolete.
  • Visual tools such as Burndown charts are used to monitor the progress of work in the sprint.
  • Burndown is a chart showing the initial scope of the sprint and the remaining work as the sprint progresses.

Scrum Sprint overview.

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.