search back preload
The Scrum Framework
Written by Daniel Pedemonte   
Wednesday, 23 January 2013 13:45

An outcome-oriented Coaching Process that you can easily apply to any situation, Part ONE

Fotolia 30745145_S

A simple introduction

The Scrum Methodology is an action-oriented process designed to facilitate and add fluidity to any project you might be involved in.
There is a difference between a goal and an outcome. A Goal is an idea with a deadline; but it only becomes an Outcome when you begin to develop a strategy for how you’re going to achieve it. For this idea to really manifest you must have a very clear outcome, a compelling purpose to drive you and an action plan, a strategy that is flexible, giving you unlimited choices about how to achieve that outcome.
The Scrum methodology can be used as a guideline to turn goals into outcomes.

Going by the numbers

As always, it all starts with a person with a vision; clarity is power. This person provides a master goal to be accomplished, an Outcome fueled by a Purpose. This purpose will create the drive and meaning to follow through. This person also gets the money to support his vision.

1. Main roles

To begin understanding this process more easily, I’d introduce you to the three Scrum main roles. These are:

1. Product Owner
2. Scrum master or “Agile Coach”, as I prefer to call it.
3. Team members

Depending on what project are you going about to face, there surely are all different kind of team members available, but we don’t need to list them all here. Scrum works on shared commitment, regardless of what they excel at because they commit to create a set of goals in a pre-defined time frame, and they do whatever is necessary to achieve that goal; and it might mean to work outside their specific rolls, skills or company title.

2. The Product Backlog

Once the vision is clear, the Product Backlog is created by the Product Owner (PO), listing the stuff that needs to get done in order to get the desired outcome.
The Product Owner can be the person with the original vision, or perhaps someone else with enough rapport with the visionary to be able to convey it to the Team Members from the practical or business perspective. The PO should also know exactly what the “product” is supposed to do and look like, and guides the process to create the expected value.

One of the great things about this backlog is that it is prioritized by the PO, putting the highest values or risks at the top of the list in order to be handled first.

This Backlog might be improved by adding necessary stuff to the list as the project begins to move forward, but it can start with what we have initially. We must spend some time aiming but if we don’t start firing our shots, we will never know if our aiming is right (and we can always make adjustments afterwards!)


That's it for today. Be sure to follow this article tomorrow to read more about scrum processes like Sprint Planning and the Scrum work itself.

See you tomorrow; and remember, it is all up to you…
You can’t control the wind, but you can control your sails


Dan C. Pedemonte
Agile Coach . Human Potential Strategist 



Last Updated on Wednesday, 23 January 2013 17:13