search back preload
The Scrum Framework . Final
PDF
Print
E-mail
Written by Daniel Pedemonte   
Wednesday, 23 January 2013 16:09

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

Fotolia 20567878_S

 

Ok, let’s get right into it. Today we'll see how the Scrum is really implemented and the steps the Team Members need to take in order to complete their task in time:

4. Working the Sprint

Daily Scrums:
Once the Sprint Backlog is defined, the Team starts working on the Sprint Backlog.
For a fluid and continuous work, they have Daily Scrums, which are problem-solving, action-oriented meetings where they commit on what they are going to GET DONE.

During these meetings, the Team Members state what they have done the day before, what they are going to get done that day, and what is on their way.
Whatever the problem they might be having, it must be presented to the whole team and handled right away (there is no point in having a meeting to set another meeting and then see how they can solve the problem).

The role of the Agile Coach is crucial here. His work is to resolve the Team’s INSIDE obstacles and also to act on behalf of the Team to resolve the obstacles OUTSIDE the Team as soon as possible to avoid losing momentum.

During the 4 weeks’ timeframe, the Team Members are:

. Working on the Sprint Backlog items until they are ALL completed.
. Keeping all outside Project Members updated of every progress, every step of the way.
. Evaluating the process (are we making measurable results? Are we still going in the right direction?)

By the end of the 4 weeks), the Sprint Backlog is completely done. We have valuable and measurable results to start implementing and we’re closer to our objective.


5. Sprint Review Meeting

This is a review meeting where we review THE PRODUCT, the “what” part of our work. We bring the OUTSIDE MEMBERS of the project and we actually show them the tangible results of our committed 4 weeks work, they can interact with the team, give valuable feedback and really see our progress towards the final outcome.


6. Sprint Retrospective Meeting

This is a review meeting for Team Members only. They might include the Product Owner, but it is optative. In this retrospective, the members evaluate their actions and performance as a team; the “how” part of the work.
The Agile Coach is the main facilitator and this important role includes making agreements with the team on changes and improvements in the way they’re working together.
These agreements will later come to nurture and enhance the following Sprints creating a Kaizen cycle of constant and never-ending improvement.

If an important improvement idea presents itself (either from the Sprint Review or the Sprint Retrospective Meeting) it can and probably will be added to improve the original Product Backlog.


7. Remember to use this Success Formula

Finally, always remember to follow these simple steps when undertaking an outcome-oriented action:

1. Know your outcome
2. Get yourself to take action simply by deciding to do so
3. Notice what you’re getting from your actions
4. If what you are doing is not working, change your approach!

If you also want to save time and energy, use role models to accelerate the pace of your success:

1. Find someone who’s already getting the results you want
2. Find out what that person is doing
3. Do the same things, get in the same state of mind, model that person’s beliefs, and you WILL get the same results.


Remember: “Simplicity is the ultimate sophistication.” – Leonardo da Vinci

 

avatar-mini

Dan C. Pedemonte
Agile Coach . Human Potential Strategist 

 


 

Last Updated on Wednesday, 23 January 2013 17:13
 

RSS-header

RSS-bottom