top of page
at-white-board.jpg

Workshops

Workshops are classes with outcomes.

We work with your team to achieve specific outcomes.

Do you need to align your organization around the right products? Or would you like to empower your team by allowing them to self-organize? Bringing in a strong facilitator with experience in helping organizations deliver results can make all the difference.

Your team struggles with the flow of work. For example, it may sail through development but never complete testing. Limiting Work in Progress may benefit your team.

The most empowered Scrum teams control the structure and organization of the Scrum team itself. It makes sense. Scrum Team members are responsible for delivering a done increment for each Sprint so they can decide how to organize and structure themselves. 

 

Teams that self-organize have higher morale and better throughput. They understand their purpose more clearly because they must consider the product goal when deciding on team structure. They adapt to changing work requirements better because they can change how the team works together to meet evolving customer needs.

Self-Organization

Scrum is a popular framework for delivering complex products. But have you ever stopped to define what the products are for your organization? Organizing Agile teams around product delivery can remove blockers, eliminate dependencies, and accelerate value delivery. In this workshop, Rebel Scrum can help your organization’s leaders define products so that you can build teams around value.

Product Definition

Are you excited about experiencing the power of these workshops in your organization? Contact Rebel Scrum, and let's talk about it.

This facilitated workshop uses the power of the team to identify improvement opportunities and identify steps to address them.

TRIZ Workshop

SCRUM ROAD
Scrum Kitchen

The concept of limiting work in progress revolves around the principle that focusing on fewer tasks at a time leads to better outcomes. In a Scrum context, this involves limiting the number of user stories, features, or tasks the development team is actively working on during a sprint. By doing so, teams prevent themselves from spreading thin and promote a concentrated effort on a select number of items. In this workshop, we lead an activity that helps teams understand the impact of limiting work in progress, and we introduce critical concepts like lead time, work item age, and cycle time. We then help teams identify the best way to visualize their work and set the right work-in-progress limits for their product.

Limiting Work in Progress

bottom of page