Scrum Values / FROCC

Agile Scrum

Scrum Values / FROCC

Commitment, focus, openness, respect and courage are core values of Scrum, living these values are the base for successful Scrum.

Read more

Get PDF

Tags

5 scrum values Abbreviation Agile commitment courage focus frocc image Infographic openess Poster respect Scrum Scrum process framework scrum values scrum values and principles scrum values in agile values scrum

Article

Scrum Values / FROCC

The behavior of people using Scrum is one of the most important aspects of Scrum. Commitment, focus, openness, respect and courage are core values of Scrum and People living these values are the base for successful Scrum implementation.

Focus

Everyone focuses on the work of the Sprint and the goals of the Scrum Team. The focus is on the sprint work of the current.

Respect

Scrum Team members respect each other to be capable, independent people. The wider environment should be respected as the source of change.

Openess

The Scrum Team and its stakeholders agree to be open about all the work and the challenges involved, as a change or collaboration with people and all it takes.

Commitment

People personally commit to the goals of the Scrum Team. The commitment is reflected in the actions and the effort.

Courage

Scrum team members have the courage to do the right thing and work on tough problems in an Agile way, to consider change as a source of value.

Resources

scrumguides.org scrum.org guntherverheyen.com thescrumvalues.org scrumalliance.org knowledgehut.com

Similar posters

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.