Scrum Institute, Scrum Framework Episode #4 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org

You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.

Listen to Scrum Institute Podcast on Apple
Listen to Scrum Institute Podcast on Google Play
Listen to Scrum Institute Podcast on Spotify
Listen to Scrum Institute Podcast on Listen Notes
Listen to Scrum Institute Podcast on Castbox

What Is Self Organization In Scrum Framework? This Might Surprise You!

The scrum team organizes itself. Scrum team members decide in consensus about tasks they need to execute to deliver the goals of a sprint. A self-organized team doesn’t require a manager or a team leader. 

Self-organization in the scrum framework is very disciplined. 

Sprint Backlog, Sprint Burn down Chart, and Daily Scrum Meetings which you are going to learn more about them later in this material build the foundation of self-organization. 

Organizing the work by themselves requires for the most teams a learning phase. Competent scrum masters who own scrum master certifications support their scrum teams to excel with self-organization quickly. 

Self-organization also includes the ability to work together despite different opinions and possible conflicts among various scrum team members. Self-organization requires compliance and trust in joint decision-making processes.

Those decision-making process in the scrum framework includes, but not limited to, planning, estimating, implementing, reporting, and reviewing the work the scrum team is jointly responsible.

Yes? Then you need to bring up a team that can self-organize its own work!

What Is Inspect And Adapt In Scrum Framework? This Might Surprise You!

Scrum Inspect and Adapt is a straightforward concept to comprehend, but the hardest to properly implement and master.

Companies have finally confirmed that none of their project managers can fully foresee the big picture of complex systems. They were unable to do reliable end-to-end planning. It was evident for them that they needed to try something different. 

Together with lean manufacturing (also known as lean movement), companies needed to develop a process to empower them strategically. They needed a standard operating procedure to help them learn and fix their courses of action while they’re running their projects and even operations.

That was the birth of Toyota Improvement Kata, which we today call “Inspect and Adapt” while we talk about scrum software development and delivery framework. 

According to “Scrum Inspect and Adapt”: 

• Step 1. Inspect: We do our best to grasp the current status of the project with our current level of know how and understanding about it. 
• Step 2. Adapt: We define a direction and vision about the next steps of our project and then strategize and execute our vision. 
• Step 3. Learn:  We carefully observe, learn, and teach each other while we do so. We continuously log what works and what doesn’t work while we do our work.
• Step 4. Restart:  Start over from Step 1 again.

Note that those four steps described above are analog, but not limited to the following Scrum rituals (Scrum events). 

• Step 1. Inspect is analog to Sprint Review Meetings and Sprint Retrospective Meetings.
• Step 2. Adapt is analog to Sprint Planning Meetings and Backlog Refinement Meetings.
• Step 3. Learn is analog to Daily Scrum Meetings.
• Step 4. Restart is analog to the closure of a sprint and the start of a new sprint.