Scrum Development Blog

Better teams make better products.

Posts Tagged ‘team’

One Scrum Team. Four Languages.

Musing, Well Formed Teams | Posted by liz.weatherhead
Aug 24 2011

Does it ever appear that your Scrum team members can express the same thought in  four different ways?

  • “Let’s knock this product out of the park!”
  • “If we can reach consensus, we can move to the next level.”
  • “The SOP will tell us what to do next.”
  • “To be efficient, we must eliminate the fluff and complete only what is absolutely necessary.”
Some of these languages are pleasant and palatable to us.  Others repel us like vinegar. Our challenge as Product Owners,  ScrumMasters and teammates is to peel the words and find value in the thought.  Let’s revisit the statements and reveal what the intent truly is.
“Let’s knock it out of the park.”  This person is a risk-taker and consistently pushes us to move from good to great.  They share information though experiences and action.  They learn by jumping in and doing.  If the doing is wrong, well, then they learned something!
“If we can reach consensus, we can move to the next level.”  Team community is the cornerstone value of this team member.  They truly embrace the well-formed team approach.  They are reflective, yet thrive in environments that are experiential.  Feelings about teams and the product are not to be discounted.  There is deep realization that teams produce better products when they work in harmony.
“The SOP will tell us what to do next.”  Structure and rule following drive this team member to do their best.  This person thinks in black and white, right or wrong.  They will strive to keep the team on the correct path.  As reflective, analytical thinkers, they speak with great precision and deliberation.
“To be efficient, we must eliminate the fluff and complete only what is absolutely necessary.”  This team member is built with pure efficiency in mind and they expect the team to follow suit.  They are active and analytical and it is a powerful combination. They get down to business and get it done. Executing the thing right trumps doing the right thing every time.
As ScrumMasters and team members, we must navigate the terrain of foreign languages everyday.  They may pop with our customers, our vendors, or with each other.  The sooner we understand the source of the language, the sooner we can find value in it.

Join us at 3Back to learn more team navigation skills with 4MAT for Scrum Teams.

Agile’s 2 Big Rules

Agile Pathways | Posted by The 3Back Team
Sep 24 2010
Agile’s 2 big rules is a way to guide the team toward maturity while they are pursuing a product outcome.

Rule One: The team will adapt it’s processes to realities encountered and improve their ability to deliver quality product, within organizational constraints.

Rule Two: The team will seek regular feedback on behalf of the product from any acceptable source.

Start your team …

… in a …

Prescriptive Manner: Tell the team how to get started, balance and which constraints to apply.

… then look for …..

Descriptive Signs: Observe, support and nurture  the team to mature and take team ownership as they pursue product outcomes.

Scrum Team

Scrum Terms | Posted by The 3Back Team
Mar 25 2010
scrum team solutions

Scrum Team

The fundamental unit in Scrum is the team. The team is the engine that works to provide a solution in the form of a product. The use of the word team becomes a little redundant in Scrum so the language was modified in 2007 to make a distinction between Scrum Team and team. Before the 2007 the word team was used for both cases and this created confusion.  Stakeholders form the context in which the Scrum Team exists. Usually there is someone special in the Stakeholder group we call the Business Owner who asked the team to form and consigned resources to the Product Owner to get the job done.

A Scrum team is made up of the team, the Scrum Master and Product Owner. A scrum team has all of the skills necessary to produce a meaningful increment of work each sprint. There is a balance of power and responsibility across the roles of ScrumMaster Product Owner and team.

Team is typially focused on providing innovative solutions. Can=>What=>How shall we build this?

Scrum Master is concerned with health of the team. Are we a well formed team?

Product Owner is focused on direction of the product. Where to next?

Please note this is but, an introduction to the terms. A full understanding takes reading, training and applied effort to really understand the balance achieved with the Scrum Development Method.