PrOpER Coaching Cycle

Agile Education Leadership Scrum

PrOpER Coaching Cycle

PrOpER Coaching cycle is the iterative mental model. It can be used when a coach is new or anytime afterwards.

Read more

Get PDF

Tags

Abbreviation Acronym Agile Coaching Experimentation image Infographic Leadership Options Picture Poster Problem Proper Coaching Cycle Proper Coaching Model Review Scrum Software development

Article

PrOpER Coaching Model

PrOpER Coaching cycle is the iterative mental model for deciding where to start coaching. It can be used when a coach is new to the team and the problems are brainstormed and prioritized. It can be also used anytime during the coaching for solving any problem that occurs.

Problem

Define the problem to be solved. Check the current situation in the team and how they work. Based on that try to identify what needs to be improved.

Options

Try to think of the ways that can help to improve or even solve the problem we identify. Do not settle with only one idea try to think of at least three.

Experimentation

Pick one of the ideas from the previous step and apply it. Make observations of changes both improvements and downsides.

Review

Review the outcome. Reflect on the results of your experiment. Evaluate improvements and downsides. Conclude if you learned something.

PrOpER Coaching Model

Resources

Rachel Davies: Agile Coaching product.gabi.cat

Similar posters

RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.

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.