Reading 2

Forming and
Empowering Scrum
Team
 Penyusun Materi

Asyirini Fajrin Dayu Bagus P Harindra W Pradhana

Agile Delivery Lead Program Management Agile Coach & Scrum Master
& Scrum Master & Scrum Master

2
 Topic 4
Forming Scrum Team and
Managing Stakeholder
Engagement

3
 Outline

1 2 3

Managing
Forming Scrum
Stakeholders
Scrum Team Accountabilities
Engagement

4
 Forming
Scrum Team

5
If your team can’t be fed by two pizzas,
then it’s too big
(Jeff Bezos)

6
Scrum Team Size
The Scrum Team is small enough to remain nimble, typically 10 or
fewer people. Smaller teams communicate better and are more
productive. If Scrum Teams become too large, consider reorganizing
into multiple cohesive Scrum Teams

7
Many Skillset within a Single Team

The Scrum Team are large

enough to complete significant
work within a sprint.
The Scrum team also
cross-functional, meaning the
members have all the skills
necessary to deliver value.

8
Independent & Capable
The scrum team responsible for all product
related activities including
● Stakeholder engagement
● Research and development
● Operations and maintenance
Individual team members may have specialized
skills and area of focus
But accountabilities belongs to the team as a
whole

9
If you tell people where to go but not how to get
there, you’ll be amazed by the results
(George S Patton)

The best architectures, requirements, and

designs emerge from self-organizing teams
(Agile Principles #11)

10
Self-Managed Team
Team empowered and have the autonomy
to plan and decide who does what, when
and how
The team can select whatever structure,
techniques and methodologies to monitor
and manage their processes and progress
in achieving their goal
The Scrum Master should support the team
being self-managed and focus towards
their goal

11
Psychological Safety
Psychological safety needed to empower
the team and promote self-management
● Approach as collaborator, not adversary
● Respect as human being
● Blamelessness, replace with curiosity
● Ask for feedback
● Do measurement

12
Further Readings
● https://agilemanifesto.org
● https://scrumguides.org
● https://www.scrum.org/resources/blog/scrum-guide-2020-update-self-mgt-replaces-sel
f-organization
● http://www.stevedenning.com/Radical-Management/most-high-performance-teams-ar
e-self-organizing.aspx
● https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-t
o-create-it

13
 Outline

1 2 3

Managing
Forming Scrum
Stakeholders
Scrum Team Accountabilities
Engagement

14
Scrum Accountabilities

15
Meet the Scrum Team
PRODUCT OWNER
The Product Owner is accountable for
maximizing the value of the product
resulting from the work of the Scrum
Team
DEVELOPERS
Developers are the people in the
Scrum Team that are committed to
creating any aspect of a usable
Increment each Sprint
SCRUM MASTER
Scrum Masters are true leaders
who serve the Scrum Team and
the larger organization
16
The Product Owner
Is one person, not a committee and accountable for :
● Developing and explicitly communicating the
Product Goal
● Creating and clearly communicating Product
Backlog items
● Ordering Product Backlog items with the highest
value first
● Ensuring that the Product Backlog is transparent,
visible and understood

17
Developers
The people in the Scrum Team that are committed
to create usable increment each sprint and
accountable for :
● Creating a plan for the Sprint, the Sprint Backlog
● Instilling quality by adhering to a Definition of
Done
● Adapting their plan each day toward the Sprint
Goal
● Holding each other accountable as professionals

18
The Scrum Master
Accountable for establishing Scrum both within the
team and throughout the organization by helping
everyone understand Scrum in both theory and
practice
Accountable for Scrum Team’s effectiveness by
enabling them to improve its practices within the
Scrum framework
Serve both the Scrum Team and the entire
organization

19
Serve the Scrum Team
● Coaching the team members in
self-management and cross-functionality
● Helping the Scrum Team focus on
creating high-value Increments that meet
the Definition of Done
● Causing the removal of impediments to
the Scrum Team’s progress
● Ensuring that all Scrum events take place
and are positive, productive, and kept
within the timebox

20
Serve the Product Owner
● Helping find techniques for effective Product
Goal definition and Product Backlog
management
● Helping the Scrum Team understand the
need for clear and concise Product Backlog
items
● Helping establish empirical product planning
for a complex environment
● Facilitating stakeholder collaboration as
requested or needed

21
Serve the Organization
● Leading, training, and coaching the
organization in its Scrum adoption
● Planning and advising Scrum implementations
within the organization
● Helping employees and stakeholders
understand and enact an empirical approach
for complex work
● Removing barriers between stakeholders and
Scrum Teams

22
Further Readings
● https://agilemanifesto.org
● https://scrumguides.org
● https://www.scrum.org/resources/truth-about-job-titles-scrum

23
 Outline

1 2 3

Managing
Forming Scrum
Stakeholders
Scrum Team Accountabilities
Engagement

24
Stakeholder Engagement

25
Who are The Stakeholders?
● The Users – The person who actually use the product
● The Internal customers – The people responsible to fund
decisions for the product development
● The External Customer – The people responsible to pay
the use the product

26
 When is someone a really
stakeholder
Actual ● Are they going to use or are
they using the product on a
Stakeholders? regular basis?
Or just your ● Are they investing
significantly in the
Audience? development of the product?
● Are they personally invested
in solving a challenge that
your product addresses?

27
Stakeholders Map

● Identify your
stakeholder
Keep Actively ● Map them into their
High
Influence Satisfied Engage respective quadrant
● Address each area
appropriately
Low Keep
Influence Monitor ● Monitor for context
Informed shifting

Low Interest High Interest

28
Customer Collaboration
Agile Value #3
Customer
Collaboration over
Contract Negotiation

Agile Principles #4
Business people and
developers must work
together daily
throughout the
Collaboration – two or more
people working together to project
achieve the same goal
29
Further Readings
● https://agilemanifesto.org
● https://scrumguides.org
● https://scrum.org
● https://medium.com/the-liberators/actual-stakeholders-or-just-your-audience-a5b6069
dc01f
● https://medium.com/the-liberators/how-to-find-your-stakeholders-e6d96fa2e5a8

30
 Outline

1 2 3

Managing
Forming Scrum
Stakeholders
Scrum Team Accountabilities
Engagement

31
 Topic 5
User Research, Persona, Story
and Journey Map

32
 Outline

33

1 2 3

User (Customer) User Journey

Product Goal
Persona

33
User (Customer) Persona

34
“If i had asked people what
they wanted, they would
have said faster horse
- Henry Ford
Why we need User Persona?

36
User Persona Template
PAIN:
Tugas banyak, lebih fokus jika
malam hari
Kesehatan mulai terganggu

Nama: Danny GAIN:

Mahasiswa Informatika
Tech Savvy (laptop, Tablet, Hp)
Rumah Bogor, kuliah Jakarta
Jomblo - Single
Extrovert
Lebih seru ngerjain tugas sambil
nongkrong di tempat yang
instagramable

37
How much personas that you need?

38
Validate your assumptions..!!

39
 Outline

40

1 2 3

User (Customer) User Journey

Product Goal
Persona

40
User (Customer) Journey

41
Keep remember your own CONTEXT
A user (customer) journey map examines the relationship between a customer and
an organization, brand, or product over time. It’s a research-based tool which takes
all touchpoints and channels of interaction into account

NEW PRODUCT EXISTING PRODUCT

42
Persona Daily Journey Example

Activity Wake up, still Join several Go to gym to Time for

sleepy due to Classes & takes exercise & relax homework, &
Andy is not a some notes prepare for
morning tomorrow
person

Touchpoint

43
User Journey Map - Product Based
Scenario: After workout, Danny need to buy some Coffee

Awareness Acquisition Service Loyalty

Get IG Ads Buy Online Coffee Get

send to Voucher
home

Step 1 Step 2 Step 3 Step 4

Visit Select & Order Fulfill the Close &

Web/App Coffee Payment review order

44
 The Big Question
What are the Problems that we can found in every Steps?

Can we solve it, to give impact to the Users

45
 Outline

46

1 2 3

User (Customer) User Journey

Product Goal
Persona

46
Product Goal

47
 “A product is a vehicle to deliver value. It
has a clear boundary, known
stakeholders, well-defined users or
customers. A product could be a service, a
physical product, or something more
abstract.”
- ScrumGuide.Org

Product Definition in Scrum

Product Goal in an Organization

Product Vision
long term strategic goal

Product Goal
Intermediate goals

Sprint Goal
immediate tactical goals

49
Defining SMART “Product” Goal
The Product Goal describes a future state of the product which can serve as a target for the
Scrum Team to plan against……. They must fulfill (or abandon) one objective before taking
on the next.

50
Product Goal Template Example

51
References:
https://www.w3schools.in/entrepreneurship/crossing-the-chasm/
https://www.nngroup.com/articles/false-consensus/
Framework (Disciplined Entrepreneurship) (d-eship.com)
Best Customer Journey Map Templates and Examples (userinterviews.com)
Scrum Guide | Scrum Guides
https://www.youtube.com/watch?v=gzfEjfpzPmk

52
Summary
Why need to define our user, thus we can explore their needs

In order to understand our user, we need to have an Empathy to

our user. By visualize their journey & validating it, we can find any
momentum that can be use to define our Product

Product is a vehicle to deliver value in scrum. Every Product have

a Goal that aligned with the Organization’s vision. A SMART
Product Goal will help all related parties chasing a same direction.

53
 Outline

54

1 2 3

User (Customer) User Journey

Product Goal
Persona

54
 Topic 6
Product Roadmap, MVP and
Iteration

55
 Outline

56

1 2 3

Product MVP & Iteration Product Backlog

Roadmap Management

56
Product Roadmap

57
Product
Roadmap
What is a Product Roadmap ?

A high-level visual that maps out the

evolution of your product over time.
It can be used a shared source of truth
that outlines the vision, direction,
priorities, and progress of a product
over time

58
Product Roadmap
Why is it Serves as a helpful guide for
Important ? teams to plan tasks and execute
on the strategy. A plan of action
that aligns the organization
around short and long-term
goals for the product or project,
and how they will be achieved

59
Product Roadmap
Who create The process works best
the Product
when collaboration is at
Roadmap?
front

60
Product Roadmap
The roadmap owner is not only
Who own
responsible for being as inclusive as
the Product possible, but for filtering all the input
Roadmap? so that goals, features and timelines
can all be changed as necessary. Then
it’s a matter of sharing the roadmap
at the appropriate time so that no one
is taken by surprise on where a
particular release is at.

61
Product Roadmap Practices
Product Roadmap
Coffee Shop Web

Stick to the Product Goal

Vision : What are we doing next ?

Strategy : What’s the actual plan ?

Objectives : Why are we doing this now ?

63
Now-Next-Later
Product Roadmap

Objectives

Advertise the Increase

Coffee Shop Transaction

Extend user Enhance user

time in web experience

64
Product Roadmap Tips
Goal Oriented Shared Actionable
The goals state the Note that collaborative The best way to achieve
specific value a product is roadmapping does not this is to base the plan on
likely to create and mean that everybody gets a validated product
therefore communicate their way or is necessarily strategy, a strategy whose
why it is worthwhile to super happy with every key assumptions have
progress it single decision been tested.

65
 ROADMAP ≠ FIXED RELEASE PLAN
Roadmap means a set strategy. Agile
means figuring out and adjusting your
strategy along the way.
 Outline

67

1 2 3
Product MVP & Iteration Product Backlog
Roadmap
Management

67
MVP & Iteration

68
The
MVP
Minimum Viable Product

The MVP was introduced by Eric Ries,

is a product with just enough features
to gather validated learning for its
continued development (Ries,2011).
MVP allow us to discover what
customers really want instead of
spending all of our time and money
building something they might want.
69
Iterative vs Big Bang Approach

Risks are mitigated earlier

Risks are mitigated earlier

70
MVP Examples

71
Spotify
Evolution
2022 1998

72
SPOTIFY Evolution
 How to Define MVP

Make sure your planned MVP aligns Translate your MVP functionality
with your business objectives into a plan of development action

Start identifying specific problems

you want to solve or improvements
you want to enable for your user
persona

74
 Outline

75

1 2 3

Product MVP & Iteration Product Backlog

Roadmap Management

75
Product Backlog Management

76
Product Backlog
Management
Backlog management is the process through which product
owners add, adjust, groom, and prioritize the backlog to make
sure the most valued features are shipped to users.

77
Product Backlog
Prioritization
Four useful factors to prioritise the
product backlog :

● Value
● Risk & Uncertainty
● Realisability
● Dependencies

78
Product Roadmap vs.
Product Backlog

79
PB Ordering Practices
Many methods exist:
ICE, MOSCOW, KANO, User voice (Voting), buy a feature
(crowd funding), etc...

ROI = Value / Investment

1. Value is not just about money
2. Investment is not just about Effort <- size is only this
3. Ordering is not just about individual ROI

80
Product Backlog
Refinement
What is Product Backlog Refinement ?

This is an ongoing activity to add

details, such as a description, order,
and size. Attributes often vary with the
domain of work.

81
User Story
The 3Cs of a Story

User stories have three critical

aspects. We can call these Card,
Conversation, and Confirmation.

82
User Story
What Makes a Good
Story?

The acronym INVEST helps to

remember a widely accepted
set of criteria, or checklist, to
assess the quality of a user story

83
User Story
examples

84
Product Backlog
Management

85
References
● https://www.romanpichler.com/blog/agile-product-roadmap/
● https://www.scrum.org/resources/blog/tips-agile-product-roadmaps-product-roadmap-
examples
● https://scrumandkanban.co.uk/incremental-or-iterative/
● https://www.scrum.org/resources/what-is-a-product-backlog

86
 Outline

87

1 2 3

Product MVP & Iteration Product Backlog

Roadmap Management

87
Terimakasih

88