Scrum framework

Lightweight framework - complex problems poster. Scrum is a framework not only for software development guiding the increment creation process, while offering enough freedom.
Read more

Scrum framework

Light framework – complex problems Lightweight framework helping generate value through adaptive solutions for complex problems. Founded on empiricism and lean, provides an environment for intelligence of its players.

Scrum Pillars:
  • Transparency
  • Inspection
  • Adaptation

Scrum values:
  • Commitment
  • Focus
  • Openness
  • Respect
  • Courage

Scrum Roles:
  • Scrum Master
  • Product Owner
  • Developers

Scrum Events

Events in Scrum are opportunities to inspect, adapt and enable transparency.

The Sprint
A container for all the events, not longer than one month. The value is created by the work done in a sprint.

Sprint Planning
Timeboxed for 8 hours. Initiates the sprint by creating a plan for addressing a valuability of the sprint, deciding what can be done and how.

Daily Scrum
Same time and place for 15 minutes to inspect work progress and adapt the Sprint Backlog if necessary.

Sprint Review
Outcome of the sprint is inspected. The outcome is taken into account and progress toward a product goal is discussed. Maximum timebox is 4 hours for a one-month sprint.

Sprint Retrospective
The maximum of three hours for a one-month sprint. Individuals, interactions, processes, tools, and the Definition of Done is inspected in order to create a plan for improving quality.

Scrum Artifacts

Represent work or value while maximizing transparency.

Product Backlog
An ongoing ordered list, which is the only source of work for the scrum team. It should reflect a product goal. At the top should be the most defined items which can be done within one sprint.

Sprint Backlog
Includes selected items from Product Backlog, plan for delivering them and the Sprint Goal based on which the previous are chosen. The Sprint Goal is a single objective to which developers commit.

Is presented at the Sprint Review as a stepping stone toward the Product Goal. To provide the transparency and meet the quality standards the Definition of Done must be met.

Scrum framework overview

Similar posters

Maslow's Hierarchy Of Needs
Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.
RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
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.