SlideShare a Scribd company logo
HOWTO BUILD A SUPERSTAR
SELF-ORGANIZING
TEAM?
Speakers
Roman Sakharov
Business Analyst
CSM,Trainer
Alex Lutsaevsky
Agile Coach
CSPO,Trainer
Give them the environment and
support they need, and trust them to
get the job done.
/Principles behind the Agile Manifesto/
Why not
having a
good old
command
and
control?
Let’s try? Line Up
Split to teams.
Each team has a
manager and a
bunch of workers.
Goal: to sort
people.
Manager sorts people by their
working experience in their last
company.
60 seconds
Iteration 1:
People self-organize to sort
themselves alphabetically by the
first letter of their second name.
60 seconds
Iteration 2:
People self-organize to sort
themselves by experience with
Agile.
60 seconds
Iteration 3:
What did it feel like as the manager
in the first iteration?
As the workers?
How easy or hard was it to arrange
yourselves?
Debrief:
Mechanical vs. Knowledge
Mechanical
work, C&C :
many hands
(resources)
Knowledge
work:
many brains
(experts)
C&C: Only one brain is used
1
Know how,
have no
authority
Have
authority,
have no idea
C&C: Slow decisions2
Issues
discovered and
resolved sooner
by people
experiencing
them directly
Autonomy
Mastery
Purpose
3 C&C: Lower motivation
Demotivated = ineffective
Decision chain = slow
Less brains = stupid
3 reasons why not
command & control:
1
2
3
Self-
organizing
team
What?
Does
it look
like
this?
Pulling work
Solving conflicts internally
Improving process by themselves
Suggesting solutions
Delivering value
Self-organizing is not
doing everything!
It’s getting work done.
Why? Self-
organizing
teams
How?
It is not a silver bullet!
Not for working by instruction.
Directing Coaching
Supporting Delegating
Is the team ready for this?
Heroes?
Lone wolves?
Newbies?
Blame games?
Forming
Storming
Norming
Performing
Easier to do on the
“norming” or “performing”
stages
You still need a leader.
Mentor, moderator, “the elder”
Effective
Organizes work
Facilitates team
decisions
Ensures knowledge
is shared
Ineffective
Micromanages
Fears the loss of
status quo
Hides knowledge,
gives tasks
And not an instant solution!
Build it step by step.
Step 1: Set the common goal
Do you have a shared vision?
Members help each other
to reach common goal.
Align individual goals to the
common goal
I want to learn new
things.
Experiment with new
technologies.
I want to try to be a
manager.
Mentor junior people.
Facilitate meetings.
I want more money.
That’s it!
Increase ROI to product.
I want to stay with my
family during evenings.
Getting things done, no
overtimes.
I want to apply my
engineering skills.
Take difficult
engineering tasks.
Step 2: Establish knowledge-
sharing environment
Goals?
Priorities?
Solutions?
Changes?
Mood?
Trust.
Do what you say.
Be open.
Say what you really mean.
And feedback loops
Learn if the team is on the right track from
Team Members, Company, Management, Stakeholders
Step 3: Give each a bit of authority
And slightly add more
Facilitator helps to resolve conflicts.
There will be conflicts
Listen to each team member.
Analyze the goal and root cause.
Team takes final decision.
Step 4: Let team decide
Use RomanVoting
to come up with
decision.
Step 5: Set “good” metrics
How Agile practices help us?
Set the common goal.
ProductVision, Backlog,
Sprint Goal
Give authority. Sprint Planning, Daily Scrum
Enable knowledge-
sharing.
Daily Scrum, Information
Radiators, Wiki, Feedback
Loops
Let team decide.
Retrospective Meetings,
RomanVoting
Set good metrics.
BusinessValue, ROI,
Customer Feedback
Let’s try a new challenge!
Build the tallest freestanding structure
The entire marshmallow must be on top
Use as much or as little of the kit
You are free to break up the spaghetti,
string or tape
The challenge lasts 18 minutes
Debrief
What was your process?
How did you invent it?
Were there any leaders?
How successful was the group?
What would you do next time to be
more successful?
Stop working for boss!
Work to get things done!
Visit http://bit.ly/EPAMAgile

More Related Content

How to build a superstar self-organizing team?

Editor's Notes

  1. http://www.abc.net.au/reslib/200804/r244014_993811.jpg
  2. Iteration 1: The manager is superskilled, practically omniscient; he can solve any problem himself and just command the workers to obey his wishes. The workers await commands and don't dare speak up, else the manager might lose face. The manager's assignment is to arrange the workers into a line based on some criterion that he doesn't have enough information about, like «how long have they worked for their company," without any input from the workers. Give the manager one minute. Start the timer, and let him go.Iteration 2: Let the workers arrange themselves horizontally across the room from left to right alphabetically by middle name.Iteration 3: Let the workers arrange themselves horizontally across the room from left to right by tenure at their job how long is their experience in Agile.
  3. Mechanical:People do small pieces of work. Work order is well-known and planned. No need to think, need to do stuff. Brain has knowledge, hands do stuff.Knowledge:Need to think, to be able to make decisions. Need to have full information. All have knowledge.If people have lack of information, they will design something wrong.
  4. Мозг менеджера – субъективен, мозг коллектива – объективен. Менеджер вообще далеко не всегда умнее своих подчиненных.
  5. http://thinkprogress.org/wp-content/uploads/2013/02/harlem-fake.jpeg
  6. http://www.linkedin.com/today/post/article/20130320152447-5799319-want-your-company-to-grow-fire-your-managers
  7. There are a lot of situation, when self-organizing
  8. Scenario 1: The Scrum team isn't ready to take ownership.Management gives responsibility and ownership to a Scrum team and trusts it to deliver projects. However, the Scrum team is not ready to take on that ownership.Possible causes for this behavior include:The team is used to command and control, and it has a hard time making decisions that normally were taken by the manager.The team consists of new members and is still in a formative stage, struggling to make collective team decisions.Heroism is prevalent, which makes it difficult for the team to make consensus-based decisions rather than specialists-driven decisions.Each team member relies on the others to do the work, due to competency problems or complacency (someone else will take care of it).Everyone is too comfortable doing their individual pieces of the overall work.Experienced Agile coaches or ScrumMasters embedded in the team can help with the initial transition to self-organization and help the team members cultivate Agile values and principles. Focusing on the positives of the team's dynamics, and making small improvements to the team's work, does encourage the team to make collective decisions and learn which activities provide the foundation for self-organization. Team members also should trust each other and express feelings openly.
  9. The leadership role should be given to those who have the best skills and knowledge to decide about the particular issue.
  10. Anyhow, in a group of individuals with different ideas, there will be different opinions. A one person is needed to have authority to stop the conversation and vote for the best opinion, to facilitate people to make decisions, to resolve conflicts between people.Scenario 2: Management isn't ready to give ownership to the team.When management isn't willing to give control to the Scrum team (even if it claims that it's doing so), we have to look at possible reasons why:Management is not aware of Agile principles and the importance of teamwork, and it sees no value in giving control to the team.Management fears the loss of the status quo, feeling themselves to be less empowered if decision making is left up to the team.A culture of micromanagement is deeply rooted within the organization.Changes in HR policies that include clearly describing the role of managers can be an important step in such cases, so that managers don't feel insecure about their futures in an Agile organization.
  11. Please share with us...what, in your experience, is a shared vision?what is it like to be on a team with a shared vision?what does it take to get to a shared vision?
  12. Team members should help each other - concentrating on delivering value, not only on performing their dutiesCross-functionality avoids bottlenecks and enables possibility to shift workloads and mutual assistance
  13. Think about team orientation.Team orientation tells how well the goals of a team and theindividuals meet [9]. Many researchers suggest that individualsshould emphasize the team goals over their own [4], [20],[21]. On one hand, losing individual autonomy is harmful forthe individual’s motivation [22]. On the other hand, too muchindividual autonomy is a threat for team work [16].
  14. Feedback is a great mechanism to understand where you are. You did something – you got reaction.Feedback from who? From team members, leader, company, stakeholders.How? Encourage trust to each other inside a team. Hold sessions with stakeholders. Get info from company and management.
  15. http://www.axisagile.com/blog/planning-and-metrics/scrum-metrics-and-reporting-measure-what-you-manage/Good metric – Used as a signal to help the team identify roughly where things are at and more importantly, as a guide to help the team inspect and adapt its processes to improve over time.Evil metric – Used as an inflexible indicator for micro-managing an individual’s performance over time and more importantly, for ‘beating’ people up and killing morale.
  16. http://marshmallowchallenge.com/Instructions.html
  17. http://marshmallowchallenge.com/Instructions.html