Ved_Dik2

· Which of the top three traits identified for your role do you think are the most important?

· Is there another trait that is not defined for your selected role that you think is important? Be sure to support your choice with real-world examples and discuss the outcome on the product, either good or bad.

W hitepapers

According to the Scrum Guide, Scrum is a framework within which people can address complex

problems, and productively and creatively develop products of the highest possible value. It’s a tool

organizations can use to increase their agility.

Within Scrum self-organizing, cross-functional, and highly productive teams do the work: creating

valuable releasable product increments. Scrum offers a framework that catalyzes the teams learning

through discovery, collaboration and experimentation.

A great Scrum Team consists of a Product Owner who maximizes value, a Scrum Master who enables

continuous improvement and a Development Team who focuses on delivering high quality product

increments.

For sure this sounds great!

But what are the characteristics of such a great Scrum Team?

This white paper will answer that question. It offers a detailed description of the characteristics and

skills of a great Product Owner, Scrum Master and Development Team.

If you know any other characteristics of a great Scrum Team, feel free to share them with me at

barry.overeem@gmail.com

Barry Overeem

Characteristics of a Great Scrum Team

July 2016

The Product Owner
The Product Owner is responsible for maximizing the value of the product and the work of the

Development Team. It’s a one-person role that brings the customer perspective of the product to a

Scrum Team1.

The Product Owner is responsible for:

 Developing and maintaining a product vision and market strategy;

 Product

management;

 Ordering and managing the Product Backlog;

 Involving stakeholders and end-users in Product Backlog refinement and backlog

management;

 Alignment with other Product Owners when needed from an overall product, company or

customer perspective.

A GREAT PRODUCT OWNER…

 Embraces, shares and socializes the product vision. A great Product Owner represents

the customers voice and creates a product vision together with the stakeholders. Every

decision is taken with the product vision in mind. This ensures sustainable product

development, provides clarity for the development team and increases the chances of product

success drastically.

 Exceeds the customer’s expectation. A great Product Owner truly understands the

customer’s intentions and goals with the product and is able to outstrip its expectations.

Customer delight is the ultimate goal!

 Is empowered. A great Product Owner is empowered to take decisions related to the

product. Sure, creating support for his decisions might take some time, but swiftly taking

important decisions is a primary condition for a sustainable pace of the development team.

 Orders the product backlog. A great Product Owner understands that the product backlog

should be ordered. Priority, risk, value, learning opportunities and dependencies are all taken

into account and balanced with each other. For example, when building a house the roof

might have the highest priority considering possible rain. But still it’s necessary to realize the

foundation and walls earlier and therefore order them above the construction of the roof.

 Prefers face-to-face communication. A great Product Owner understands that the best

way to convey information is face-to-face communication. User stories are explained in a

personal conversation. If a tool is used for backlog management, its function is to support the

dialogue. It never replaces the good old-fashioned conversation.

1 Scrum – A Pocket Guide by Gunther Verheyen

 Knows modeling techniques. A great Product Owner has a backpack full of valuable

modeling techniques. He knows when to apply a specific model. Examples are Business Model

Generation, Lean Startup or Impact Mapping. Based on these models he knows how to drive

product success.

 Shares experiences. A great Product Owner shares experiences with peers. This might be

within the organization, and outside it: seminars and conferences are a great way to share

experiences and gather knowledge. In addition, writing down your lessons learned can be

valuable for other Product Owners.

 Owns user story mapping. A great Product Owner should master the concept of user story

mapping. It’s a technique that allows you to add a second dimension to your backlog. The

visualization enables you to see the big picture of the product backlog. Jeff Patton wrote some

excellent material about the concept of story mapping.

 Has a focus on functionality. A great Product Owner has a focus on functionality and the

non-functional aspects of the product. Hours or even story points are less important. The goal

of the Product Owner is to maximize value for the customer. It’s the functionality that has

value; therefore this is the main focus for

the Product Owner.

 Is knowledgeable. A great Product Owner has in depth (non-)functional product knowledge

and understands the technical composition. For large products it might be difficult to

understand all the details, and scaling the Product Owner role might be an option. However

the Product Owner should always know the larger pieces of the puzzle and hereby make

conscious, solid decisions.

 Understands the business domain. A great Product Owner understands the domain and

environment he’s part of. A product should always be build with its context taken into

account. This includes understanding the organization paying for the development but also

being aware of the latest the market conditions. Shipping an awesome product after the

window of opportunity closes is quite useless.

 Acts on different levels. A great Product Owner knows how to act on different levels. The

most common way to define these levels is strategic, tactical and operational. A Product

Owner should know how to explain the product strategy at board level, create support at

middle management and motivate the development team with their daily challenges.

 Knows the 5 levels of Agile planning. Within Agile, planning is done continuously. Every

product needs a vision (level 1) which will provide input to the product roadmap (level 2). The

roadmap is a long range strategic plan of how the business would like to see the product

evolve. Based on the roadmap, market conditions and status of the product the Product

Owner can plan releases (level 3). During the Sprint Planning (level 4) the team plan and agree

on Product Backlog Items they are confident they can complete during the Sprint and help

them achieve the Sprint Goal. The Daily Scrum (level 5) is used to inspect and adapt the team’s

progress towards realizing the Sprint Goal.

 Is available. A great Product Owner is available to the stakeholders, the customers, the

development team and the Scrum Master. Important questions are answered quickly and

valuable information is provided on time. The Product Owner ensures his availability never

blocks the progress of the development team.

 Is able to say ‘no’. A great Product Owner knows how and when to say no. This is probably

the most obvious but most difficult characteristic to master. Saying yes to a new idea or

feature is easy, it’s just another item for the product backlog. However, good backlog

management encompasses creating a manageable product backlog with items that probably

will get realized. Adding items to the backlog knowing nothing will happen with them only

creates ‘waste’ and false expectations.

 Acts as a “Mini-CEO”. A great Product Owner basically is a mini-CEO for his product. He has

a keen eye for opportunities, focuses on business value and the Return On Investment and

acts proactive on possible risks and threats. Everything with the growth (size, quality, market

share) of his product taken into account.

 Knows the different types of valid Product Backlog items2. A great Product Owner can

clarify the fact that the Product Backlog consists of more than only new features. Fore

example: technical innovation, bugs, defects, non-functional requirements and experiments,

should also be taken into account.

 Takes Backlog Refinement seriously. A great Product Owner spends enough time refining

the Product Backlog. Backlog Refinement is the act of adding detail, estimates and order to

items in the Product Backlog. The outcome should be a Product Backlog that is granular

enough and well understood by the whole team. On average the Development Team spends

no more than 10% of the capacity of the Development Team on refinement activities. The way

it is done isn’t prescribed and is up to the team. The Product Owner can involve stakeholders

and the Development Team in backlog refinement. The stakeholders because it gives them

the opportunity to explain their wishes and desires. The Development Team because they can

clarify functional and technical questions or implications. This will ensure common

understanding and increases the quality of the Product Backlog considerably. As a

consequence, the opportunity to build the right product with the desired quality will also

increase.

2 http://www.barryovereem.com/the-backlog-prioritisation-backlog/

The Scrum Master
According to the Scrum Guide the Scrum Master is responsible for ensuring Scrum is understood and

enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices,

and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those

outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and

which aren’t. The Scrum Master helps everyone changes these interactions to maximize the value

created by the Scrum Team.

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of

them and knows when and how to apply them, depending on situation and context. Everything with

the purpose of helping people understand and apply the Scrum framework better.

The Scrum Master acts as a:

 Servant Leader whose focus is on the needs of the team members and those they serve (the

customer), with the goal of achieving results in line with the organization’s values, principles,

and business objectives3;

 Facilitator by setting the stage and providing clear boundaries in which the team can

collaborate;

 Coach coaching the individual with a focus on mindset and behavior, the team in continuous

improvement and the organization in truly collaborating with the Scrum Team;

 Conflict navigator to address unproductive attitudes and dysfunctional behaviors;

 Manager responsible for managing impediments, eliminate waste, managing the process,

managing the team’s health, managing the boundaries of self-organization, and managing the

culture;

 Mentor that transfers agile knowledge and experiences to the team;

 Teacher to ensure Scrum and other relevant methods are understood and enacted.

A GREAT SCRUM MASTER…

 Involves the team with setting up the process. A great Scrum Master ensures the entire

team supports the chosen Scrum process and understands the value of every event. The daily

Scrum for example is planned at a time that suits all team members. A common concern about

Scrum is the amount of ‘meetings’, involving the team with planning the events and discussing

the desired outcome will increase engagement for sure.

 Understands team development. A great Scrum Master is aware of the different phases a

team will go through when working as a team. He understands Tuckman’s different stages of

team development: forming, storming, norming, performing and adjourning. The importance

of a stable team composition is therefore also clear.

 Understands principles are more important than practices. Without a solid, supported

understanding of the agile principles, every implemented practice is basically useless. It’s an

3 http://www.infoq.com/articles/leadership-challenge

empty shell. An in-depth understanding of the agile principles by everyone involved will

increase the chances of successful usage of practices drastically.

 Recognizes and acts on team conflict. A great Scrum Master recognizes team conflict in

an early stage and can apply different activities to resolve it. A great Scrum Master

understands conflict isn’t necessarily wrong. Healthy conflict and constructive disagreement

can be used to build an even stronger team.

 Dares to be disruptive. A great Scrum Master understands some changes will only occur by

being disruptive. He knows when it’s necessary and is prepared to be disruptive enough to

enforce a change within the organization.

 Is aware of the smell of the place. A great Scrum Master can have an impact on the culture

of the organization so that the Scrum teams can really flourish. He understands that changing

people’s behavior isn’t about changing people, but changing the context which they are in:

the smell of the place.

 Is both dispensable and wanted. A great Scrum Master has supported the growth of teams

in such a manner they don’t need him anymore on daily basis. But due to his proven

contribution he will get asked for advice frequently. His role has changed from a daily coach

and teacher to a periodical mentor and advisor.

 Let his team fail (occasionally). A great Scrum Master knows when to prevent the team

from failing but also understands when he shouldn’t prevent it. The lessons learned after a

mistake might be more valuable than some good advice beforehand.

 Encourages ownership. A great Scrum Master encourages and coaches the team to take

ownership of their process, task wall and environment.

 Has faith in self-organization. A great Scrum Master understands the power of a self-

organizing team. “Bring it to the team” is his daily motto. Attributes of self-organizing teams

are that employees reduce their dependency on management and increase ownership of the

work. Some examples are: they make their own decisions about their work, estimate their

own work, have a strong willingness to cooperate and team members feel they are coming

together to achieve a common purpose through release goals, sprint goals and team goals.

 Values rhythm. A great Scrum Master understands the value of a steady sprint rhythm and

does everything to create and maintain it. The sprint rhythm should become the team’s

heartbeat, which doesn’t cost any energy. Everyone knows the date, time and purpose of

every Scrum event. They know what is expected and how to prepare. Therefore a complete

focus on the content is possible.

 Knows the power of silence. A great Scrum Master knows how to truly listen and is

comfortable with silence. Not talking, but listening. He is aware of the three levels of listening

– level 1 internal listening, level 2 focused listening, level 3 global listening, and knows how to

use them. He listens carefully to what is said, but also to what isn’t said.

 Observes. A great Scrum Master observes his team with their daily activities. He doesn’t have

an active role within every session. The daily Scrum, for example, is held by the team for the

team. He observes the session and hereby has a more clear view to what is being discussed

(and what isn’t) and what everyone’s role is during the standup.

 Shares experiences. Great Scrum Masters shares experiences with peers. This might be

within the organization, but also seminars and conferences are a great way to share

experiences and gather knowledge. Of course writing down and sharing your lessons learned

is also highly appreciated. And yes, for the attentive readers, this is exactly the same as for

the Product Owner and the Development Team.

 Has a backpack full of different retrospective formats. A great Scrum Master can apply

lots of different retrospective format. This ensures the retrospective will be a fun and useful

event for the team. He knows what format is most suitable given the team’s situation. Even

better: he supports the team by hosting their own retrospective. To improve involvement this

is an absolute winner!

 Can coach professionally. A great Scrum Master understands the power of professional

coaching and has mastered this area of study. Books like Coaching Agile Teams and Co-Active

Coaching don’t have any secrets for him. He knows how to guide without prescribing. He can

close the gap between thinking about doing and actually doing; he can help the team

members understand themselves better so they can find news ways to make the most of their

potential. Yes, these last few sentences are actually an aggregation of several coaching

definitions, but it sounds quite cool!

 Has influence at organizational level. A great Scrum Master knows how to motivate and

influence at tactic and strategic level. Some of the most difficult impediments a team will face

occur at these levels; therefore it’s important a Scrum Master knows how to act at the

different levels within an organization.

 Prevent impediments. A great Scrum Master not only resolves impediments, he prevents

them. Due to his experiences he is able to ‘read’ situations and hereby act on them proactively.

 Isn’t noticed. A great Scrum Master isn’t always actively present. He doesn’t disturb the team

unnecessary and supports the team in getting into the desired ‘flow’. But when the team

needs him, he’s always available.

 Forms a great duo with the Product Owner. A great Scrum Master has an outstanding

partnership with the Product Owner. Although their interests are somewhat different, the

Product Owner ‘pushes’ the team, the Scrum Master protects the team. A solid partnership is

extremely valuable for the Development Team. Together they can build the foundation for

astonishing results.

 Allows leadership to thrive. A great Scrum Master allows leadership within the team to

thrive and sees this as a successful outcome of their coaching style. They believe in the motto

“leadership isn’t just a title, it’s an attitude”. And it’s an attitude everyone in the team can

apply.

 Is familiar with gamification. A great Scrum Master is able to use the concepts of game

thinking and game mechanics to engage users in solving problems and increase users’

contribution.

 Understands there’s more than just Scrum. A great Scrum Master is also competent with

XP, Kanban and Lean. He knows the strengths, weaknesses, opportunities and risks of every

method/framework/principle and how & when to use them. He tries to understand what a

team wants to achieve and helps them become more effective in an agile context.

 Leads by example. A great Scrum Master is someone that team members want to follow.

He does this by inspiring them to unleash their inner potential and showing them the desired

behavior. At difficult times, he shows them how to act on it; he doesn’t panic, stays calm and

helps the team find the solution. Therefore a great Scrum Master should have some

resemblance to Gandalf. The beard might be a good starting point 🙂

 Is a born facilitator. A great Scrum Master has facilitation as his second nature. All the Scrum

events are a joy to attend, and every other meeting is well prepared, useful and fun, and has

a clear outcome and purpose.

The Development Team
According to the Scrum Guide the Development Team consists of professionals who do the work of

delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Only

members of the Development Team create the Increment. Development Teams are structured and

empowered by the organization to organize and manage their own work. The resulting synergy

optimizes the Development Team’s overall efficiency and effectiveness.

Development Teams have the following characteristics:

 Self-organizing. They decide how to turn Product Backlog Items into working solutions.

 Cross-functional. As a whole, they’ve got all the skills necessary to create the product

Increment.

 No titles. Everyone is a Developer, no one has a special title.

 No sub-teams in the Development Team.

 Committed to achieving the Sprint Goal and delivering a high quality increment.

A GREAT DEVELOPMENT TEAM…

 Pursues technical excellence. Great Development Teams use Extreme Programming as a

source of inspiration. XP provides practices and rules that revolve around planning, designing,

coding and testing. Examples are refactoring (continuously streamlining the code), pair

programming, continuous integration (programmers merge their code into a code baseline

whenever they have a clean build that has passed the unit tests), unit testing (testing code at

development level) and acceptance testing (establishing specific acceptance tests).

 Applies team swarming. Great Development Teams master the concept of ‘team

swarming’. This is a method of working where a team works on just a few items at a time,

preferably even one item at a time. Each item is finished as quickly as possible by having many

people work on it together, rather than having a series of handoffs.

 Uses spike solutions. A spike is a concise, time-boxed activity used to discover work needed

to accomplish a large ambiguous task. Great Development Teams uses spike experiments to

solve challenging technical, architectural or design problems.

 Refines the product backlog as a team. Great Development Teams consider backlog

refinement a team effort. They understand that the quality of the Product Backlog is the

foundation for a sustainable development pace and building great products. Although the

Product Owner is responsible for the product backlog, it’s up to the entire team to refine it.

 Respects the Boy Scout Rule. Great Development Teams use the Boy Scout Rule: always

leave the campground cleaner than you found it. Translated to software development: always

leave the code base in a better state than you’ve found it. If you find messy code, clean it up,

regardless of who might have made the mess.

 Criticizes ideas, not people. Great Development Teams criticize ideas, not people. Period.

 Share experiences. Great Development Teams share experiences with peers. This might be

within the organization, but also seminars and conferences are a great way to share

experiences and gather knowledge. Of course writing down and sharing your lessons learned

is also highly appreciated. And yes, for the attentive readers, this is exactly the same as for

the Product Owner.

 Understands the importance of having some slack. Great Development Teams have

some slack within their sprint. Human beings can’t be productive all day long. They need time

to relax, have a chat at the coffee machine or play table football. They need some slack to be

innovative and creative. They need time to have some fun. By doing so, they ensure high

motivation and maximum productivity. But slack is also necessary to handle emergencies that

might arise; you don’t want your entire sprint to get into trouble when you need to create a

hot-fix. Therefore: build in some slack! And when the sprint doesn’t contain any emergencies:

great! This gives the team the opportunity for some refactoring and emergent design. It’s a

win-win!

 Has fun with each other. Great Development Teams ensure a healthy dose of fun is present

every day. Fostering fun, energy, interaction and collaboration creates an atmosphere in

which the team will flourish!

 Don’t have any Scrum ‘meetings’. Great Development Teams consider the Scrum events

as opportunities for conversations. Tobias Mayer describes this perfectly in his book ‘The

Peoples Scrum’: “Scrum is centered on people, and people have conversations. There are

conversations to plan, align, and to reflect. We have these conversations at the appropriate

times, and for the appropriate durations in order to inform our work. If we don’t have these

conversations, we won’t know what we are doing (planning), we won’t know where we are

going (alignment), and we’ll keep repeating the same mistakes (reflection).”

 Knows their customer. Great Development Teams know their real customer. They are in

direct contact with them. They truly understand what they desire and are therefore able to

make the right (technical) decisions.

 Can explain the (business) value of non-functional requirements. Great Development

Teams understand the importance for non-functional requirements like e.g. performance,

security and scalability. They can explain the (business) value to their Product Owner and

customer and hereby ensure its part of the product backlog.

 Trust each other. Great Development Teams trust each other. Yes, this is obvious. But

without trust it’s impossible for a team to achieve greatness.

 Keep the retrospective fun. Great Development Teams think of retrospective formats

themselves. They support the Scrum Master with creative, fun and useful formats and offer

to facilitate the sessions themselves.

 Deliver features during the sprint. Great Development Teams deliver features

continuously. Basically they don’t need sprints anymore. Feedback is gathered and processed

whenever an item is ‘done’; this creates a flow of continuous delivery.

 Don’t need a sprint 0. Great Development Teams don’t need a sprint 0 before the ‘real’

sprints start. They are able to deliver business value in the first sprint.

 Acts truly cross-functional. Great Development Teams not only have a cross-functional

composition and act truly cross-functionally. They don’t talk about different roles within the

team but are focused on delivering a releasable product each sprint as a team. Everyone is

doing the stuff that’s necessary to achieve the sprint goal.

 Updates the Scrum board themselves. Great Development Teams ensure the Scrum/team

board is always up-to-date. It’s an accurate reflection of the reality. They don’t need a Scrum

Master to encourage them; instead they collaborate with the Scrum Master to update the

board.

 Spends time on innovation. Great Development Teams understand the importance of

technical/architectural innovation. They know it’s necessary to keep up with the rapidly

changing environment and technology. They ensure they have time for innovation during

regular working hours, and that it’s fun and exciting!

 Don’t need a Definition of Done. Great Development Teams deeply understand what

‘done’ means for them. For the team members, writing down the Definition of Done isn’t

necessary anymore. They know. The only reason to use it is to make the ‘done state’

transparent for their stakeholders.

 Knows how to give feedback. Great Development Teams have learned how to give each

other feedback in an honest and respectful manner. They grasp the concept of the ‘Situation

– Behavior – Impact Feedback Tool’ and hereby provide clear, actionable feedback. They give

feedback whenever it’s necessary, and don’t postpone feedback until the retrospective.

 Manages their team composition. Great Development Teams manage their own team

composition. Whenever specific skills are necessary, they collaborate with other teams to

discuss the opportunities of ‘hiring’ specific skills.

 Practice collective ownership. Great Development Teams understand the importance of

collective ownership. Therefore they rotate developers across different modules of the

applications and systems to encourage collective ownership.

 Fix dependencies with other teams. Great Development Teams are aware of possible

dependencies with other teams and manage these by themselves. Thereby ensuring a

sustainable development pace for the product.

 Don’t need story points. Great Development Teams don’t focus on story points anymore.

They’ve refined the product backlog so that the size for the top items don’t vary much. They

know how many items they can realize each sprint. Counting the number of stories is enough

for them.

About the Author
Barry is a freelance Agile Coach and Professional Scrum Trainer at Scrum.org. He is an active member

of the Agile community and shares his insights and knowledge by speaking at conferences and writing

articles.

Since 2000 he fulfilled several roles within the software development environment, these vary from

application consultant, project manager and team lead. Since 2010 his primary focus is applying the

Agile mindset and Scrum Framework. Barry is specialized in the role of the Scrum Master and helping

people understand the spirit of Scrum and hereby using the Scrum framework better. Due to his own

practical experience as a Scrum Master, Barry gained a lot of experience with starting new teams,

coaching teams through the different stages of team development and applying different types of

leadership. Sharing these experiences and hereby contributing to others persons growth is his true

passion!

Turn in your highest-quality paper
Get a qualified writer to help you with

“ Ved_Dik2 ”

Get high-quality paper

NEW! AI matching with writer

Are you stuck with your online class?

Get help from our team of writers!

Order Today