CSPO Workshop Participant Workbook V5.0 (OCT 2020)

Download as pdf or txt
Download as pdf or txt
You are on page 1of 80

BUILD GREAT PRODUCTS

That Always Deliver


VALUE TO CUSTOMERS

Version 5.0 (October 2020)

Trainer

VIJAY BANDARU
CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

AGENDA
DAY 1 TOPICS DAY 2 TOPICS
Forming Teams, Intro & Workshop setup Product Discovery
Product and Product Levels Agile Product planning
Product Lifecycle Product Vision
Minimum Viable Product Prioritization Techniques
Project & Product Mindset Product Roadmap
Agile Manifesto Values & Principles Product Backlog
Scrum Framework overview Product Backlog Refinement
Scrum Framework Elements User stories
Scrum Values and Roles Release planning and Tracking
Scrum Framework Flow Product increment
Sprint, Scrum Artifacts & Definition of Done Release Planning and Tracking Simulation
Product Owner Role Deep Dive Certification Discussion
Day 1 Wrap up Closure

Scrum Alliance CSPO Certification Levels

VIJAY BANDARU WWW.LEARNOVATIVE.COM 2


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Meet Your Trainer

➢ Active knowledge sharing through Linked in Group “Universal Agile & Scrum Community
of Practice”
(https://www.linkedin.com/groups/8305379/)

➢ My previous Trainings Videos, Photos and Feedback at:


www.facebook.com/learnovative

Training is not just my PROFESSION, it is my PASSION

I hope you enjoy the learning in my class and wish you good luck !!

VIJAY BANDARU WWW.LEARNOVATIVE.COM 3


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Our working agreement

VIJAY BANDARU WWW.LEARNOVATIVE.COM 4


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Activity: What is your favourite Product and why?

✓ Products should be _____________ centric

✓ Products should be built to solve a ___________ or should fulfil a


___________

✓ _______________ segmentation is key in order to create successful


Products

✓ Products must be useful and also ____________

✓ Regular customer involvement during Product Development helps to


receive early ___________

✓ Early feedback helps you to keep cost of ____________ under control

✓ Product development should leverage the latest _________________

✓ Products should have a clear ___________ and a strong ____________

✓ Product owner should be ______________ to own the end to end Product


development and to make decisions

Focus on the “NEED” not the “REQUIREMENT”

VIJAY BANDARU WWW.LEARNOVATIVE.COM 5


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

✓ Few “Facts” about Product Owner


- Product Owner’s primary focus is not the “PROCESS”, rather, he/she focuses on the
“________________”
- Product Owner is NOT responsible for “_________” implementation
- Product Owner should be able to multiply _____________

Big picture of Product Owner role

VIJAY BANDARU WWW.LEARNOVATIVE.COM 6


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

What is Product?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 7


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

A Product should solve a


Particular PROBLEM or
Fulfil a specific NEED
PRODUCT LEVEL DESCRIPTION PRODUCT LEVEL NAME
Basic version of the Product that just fulfil the need GENERIC
The Product that contains the features that users do expect EXPECTED
The Product contains the features that are beyond AUGMENTED
expectations

The Product contains the features that are not available yet POTENTIAL
but may be expected by users in the future

VIJAY BANDARU WWW.LEARNOVATIVE.COM 8


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Activity: Go to the blank flipchart nearby your table as a team, chose a product from your
experience as a team and identify all the levels of that product using the below format and
for every level identify the features using post it notes. (10 Minutes)

Have a Gallery walk in clock wise direction to see other table’s work (Spend about 1
Minute at every table)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 9


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Lifecycle

______ _______ ______________ _____________ _____________ ___________

VIJAY BANDARU WWW.LEARNOVATIVE.COM 10


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Minimum Viable Product (MVP)

A minimum viable product (MVP) is a concept from Lean Startup that stresses the impact of
learning in new product development. Eric Ries, defined an MVP as that version of a new product
which allows a team to collect the maximum amount of validated learning about customers
with the least effort.

A key premise behind the idea of MVP is that you produce an actual product (which may be no
more than a landing page, or a service with an appearance of automation, but which is fully
manual behind the scenes) that you can offer to customers and observe their actual behavior
with the product or service. Seeing what people actually do with respect to a product is much
more reliable than asking people what they would do.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 11


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Examples:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 12


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

How Airbnb started with MVP?


Airbnb started off as a simple site launched by three founders who came up with the
assumption that people wouldn’t be able to find a place to stay during the Industrial Design
Society of America Conference in San Francisco in 2007. So they piled up all their beds in their
small apartment and put up a simple ad about renting an air bed on a simple web page. Soon,
they had three guests who wanted to share their apartment. Once they had proven that their
idea wasn’t a waste of time and money, they started looking for how to redesign the platform.
Today, Airbnb has 150 million users, 4 million listings, and is valued at $30 billion. It offers not
only accommodation but provides users with lists of restaurants and events in destination
cities along with feedback and ratings.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 13


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

PROJECT Vs PRODUCT
Activity: Understand Project Vs Product
Below are the characteristics of Product and Project. Discuss at your Table and separate them into
the below table. (3 Minutes)

PROJECT PRODUCT

VIJAY BANDARU WWW.LEARNOVATIVE.COM 14


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

PROJECT VS PRODUCT MINDSET

Activity: Map the below items to the PROJECT and PRODUCT Mindset

Shifting from Project Mindset to Product Mindset is


part of Agile Transformation

VIJAY BANDARU WWW.LEARNOVATIVE.COM 15


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Different Ways of Product Development

VIJAY BANDARU WWW.LEARNOVATIVE.COM 16


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

What is Agility?

Frequent delivery helps you to receive early “Feedback”

Consistent delivery helps you to increase “ROI” (Return On Investment)

Iterative (repetitive) improves the “Process”

Incremental (add on to) improves the “Product”

Map these items to the above statements:

Change, Value, Unpredictability, Consistently

Why Agile?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 17


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Agile Manifesto 4 Values


We are uncovering better ways of developing software by doing it and helping others
do it. Through this work we have come to value:

Individuals and interactions OVER Processes and tools


Working software OVER Comprehensive documentation
Customer collaboration OVER Contact negotiation
Responding to change OVER Following a plan

While there is value in the items on the Right side, we value the items on the LEFT MORE!

12 Agile Principles
1. Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software
2. Welcome changing requirements, even late in development. Agile processes harness
change for the customer’s competitive advantage
3. Deliver working software frequently, from a couple of weeks to a couple of months, with
a preference to the shorter timescale
4. Business people and developers must work together daily throughout the project
5. Build projects around motivated individuals. Give them the environment and support
they need, and trust them to get the job done
6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation
7. Working software is the primary measure of progress
8. Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefinitely
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity--the art of maximizing the amount of work not done – is essential
11. The best architectures, requirements, and designs emerge from self-organizing teams
12. At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behavior accordingly

VIJAY BANDARU WWW.LEARNOVATIVE.COM 18


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Activity: Understand the below 4 parameters. The RED lines indicate the
behavior of these parameters in waterfall way of working. GREEN lines
indicate the Agile way of working.

(2 Minutes)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 19


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Framework Overview


➢ Scrum is a FRAMEWORK to address COMPLEX adaptive problems

➢ Foundation for Scrum is Empiricism

➢ Empiricism asserts that knowledge comes from experience and the decisions are
made based on what is known

➢ THREE legs of Empirical process are:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 20


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Framework Elements

Map the below elements to the above diagram:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 21


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Team

VIJAY BANDARU WWW.LEARNOVATIVE.COM 22


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Framework Flow


Activity: Complete the Scrum Framework based on the explanation that we had

VIJAY BANDARU WWW.LEARNOVATIVE.COM 23


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Sprint

- Sprint is the heartbeat of Scrum (a container event)


- It is a timeboxed duration with a maximum duration of 1 month or less
- Every Sprint will have 4 events
o Sprint Planning: Maximum duration of 8 hours for a 1 month Sprint
o Daily Scrum: Maximum 15 minutes for any Sprint duration
o Sprint Review: Maximum duration of 4 hours for a 1 month Sprint
o Sprint Retrospective: Maximum duration of 3 hours for a 1 month Sprint
- Product Backlog Refinement: Is an ongoing activity to add details to the upcoming
Product Backlog Items. It can take up to 10% of Development Team’s capacity
- Sprint Characteristics:
o Timeboxed
o Iterative
o Incremental
o Protected

Sprint Cancellation
Abnormal termination of the Sprint before Timebox expires is called “Sprint Cancellation”
- Only Product Ower can take call on the Sprint Cancellation
- Only reason for Sprint Cancellation is “When Sprint Goal is obsolete”
- When Product Owner decides to cancel a Sprint, below things happen:
o Review of the items (if there are any by that time of canellation)
o Retrospective
o Next Sprint Planning

VIJAY BANDARU WWW.LEARNOVATIVE.COM 24


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Definition of Done
✓ Quality criteria checklist
✓ Helps Product Owner and Development team have a shared understanding on “Done”
✓ Created by Scrum team collaboratively
✓ Different for different products
✓ Created before Sprint planning
✓ If there are any organization level quality standards exist, they must be part of DoD
✓ Helps Development team in Sprint planning to forecast the work
✓ In multi-team environment, all teams should have a common Definition of Done
✓ Sprint retrospective is a formal opportunity for Scrum team to inspect and adapt

ACCEPTANCE CRITERIA DEFINITION OF DONE


Related to functionality Related to quality
Owned by Product Owner Owned by Development Team
Specific to each Product Backlot Item Common to entire backlog
Can be created at any time before Usually defined before the first Sprint
accepting into a Sprint

VIJAY BANDARU WWW.LEARNOVATIVE.COM 25


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Artifacts

✓ Artifacts help to enhance TRANSPARENCY


✓ They represent either WORK or VALUE
✓ Product Backlog and Sprint Backlog represent WORK
✓ Product Increment represents VALUE

VIJAY BANDARU WWW.LEARNOVATIVE.COM 26


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Owner Role

VIJAY BANDARU WWW.LEARNOVATIVE.COM 27


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Owner Rights


✓ Independent authority on Product Backlog (especially ordering and content)
✓ Decides when to release the Product increment
✓ “WHAT” part of the Product
✓ Sprint cancellation

Product Owner Responsibilities:

➢ SINGLE person, not a COMMITTEE

➢ Maximize the business value and the work of the Development team

➢ Owns the Product VISION (represents WHY we build product and WHAT the
desired end state is)

➢ Manages Product BACKLOG (Content, Availability & Order)

➢ Clearly expresses the Product Backlog items

➢ Ensure the Product backlog is visible and accessible to all

➢ Ensures Return on investment

➢ Works closely with Development team and Stakeholders

➢ Represents the customer/Business

➢ Tracks overall product Progress

➢ Reviews product backlog items and provide feedback/acceptance to


Development team

➢ Provides clarifications to the Development team

➢ Leads Product Backlog Refinement

VIJAY BANDARU WWW.LEARNOVATIVE.COM 28


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

4 Ws of the Product Owner:

W_ _ What about HOW then?


______________ is responsible
for the HOW part of the
W___ Product

W__
W___
Identify Product Owner activities with the INTERNAL (Team) and EXTEERNAL (Beyond Team):

(5 Min)

INTERNAL EXTERNAL

VIJAY BANDARU WWW.LEARNOVATIVE.COM 29


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Owner Role In A Sprint

Activities of Product Owner Respective part of Sprint


• Represents the Stakeholders to Dev team
• Explains/Presents the Backlog items to the Dev team
• Collaborates with Dev team to formulate the Sprint Goal
• Provides clarifications
• Provide Trade-off inputs
• Provides his inputs to the Dev team on anything related
to Process/Tools/Relationships and other areas
• Takes feedback from the team on any improvements that
Product owner has to work up on
• Product owner collaborates with Dev team for this
activity
• Involves the Dev team to get their support in estimates
• Available to the Dev team on need basis
• Provide clarifications
• Verifies the items that are done and provide inputs
• Approves the items that are done
• Represents the Dev team to the Stakeholders
• Explains what is done/not done
• Works with stakeholders to get their feedback
• Updates stakeholders on the forecast/Market conditions
• Together with stakeholders and Dev & Scrum Master
discusses that needs to be done next Sprint
• Product owner is optional
• If Dev team wants, then Product owner should attend
• Purpose is to provide clarifications

VIJAY BANDARU WWW.LEARNOVATIVE.COM 30


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Owner Key Characteristics


- Domain Knowledge
- Empowered
- Accountable
- Available
- Communication
- Passion
- Courageous

Activity: Read and understand the various shades (anti-patters) of Product Owner role in
various organizations.

Source: https://www.learnovative.com/different-shades-of-the-product-owner-role-in-organizations/

Discuss: (Possible challenges)


1. Product owner manages more than one product simultaneously
2. One Product owner per Development Team on the same Product instead of Single PO
3. Separate Product Owners for Feature/Component/Epic instead of Single PO
4. For a single Product, one PO at onsite and other PO at offshore
5. Relabeling Traditional Project Manager into a Product Owner role
6. One of the Development Team members is also a Product Owner of the Product

VIJAY BANDARU WWW.LEARNOVATIVE.COM 31


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Discovery
Do you know the Top 10 reasons for start-ups to fail?

Source: https://www.strategyzer.com/blog/posts/2018/10/15/why-companies-work-on-products-nobody-wants

VIJAY BANDARU WWW.LEARNOVATIVE.COM 32


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Discovery is the process that helps the


Product Owner to identify ideas to build Products that
are USEFUL and also USABLE

What is the difference between a User and Customer?

User:

Customer:

How do you empathize with Users as a Product owner?


“User Research” is one of the powerful ways to understand use behaviors, their needs, pains
and gains through some observations techniques. Key to user research is “Empathy”.
Empathy is to understand user’s needs, desires, and wants from their point of view.

User Research for a new Product is different from User Research for an existing product. For
a new product (0 → 1 Stage), User Research is done to validate product ideas and hypotheses.
For an existing product (1 → n Stage), User Research is done to get feedback on features of
the product.

User research helps in:

✓ Validate assumptions and hypothesis


✓ Get qualitative data about user needs/desires/behaviors
✓ Understand how users will interact and use your product
✓ Promotes iterative approach to refine your product
✓ Gives in depth understanding and clarity on what works and what does not work in your
Product

VIJAY BANDARU WWW.LEARNOVATIVE.COM 33


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

User Research helps improving the Design:

Steps to conduct User Research:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 34


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Common methods to conduct the User Research:


Description of the User Research Method

A/B Testing: This is a quantitative method in which you can create


two versions of a product or feature, and evaluate which one
works better with the users

Contextual Inquiry: Users are observed performing tasks in their


original habitat to gather information about the context of use of
the product

Focus Group: Moderated discussion with a group of users, allow


you to learn about user attitudes, ideas, and desires

Heatmap: A heatmap is a graphical representation of data where


values are depicted by color. Heatmaps make it easy to visualize
complex data of users and understand it at a glance

Interview: These are one-on-one discussions with individual users


to gather qualitative data about their pain points and motivations

Prototype: Allows the design team to explore ideas before


implementing them by creating a mock-up of the site. A prototype
can range from a paper mock-up to interactive html pages

Survey: Consists of a questionnaire with questions and structured


responses, and comes in handy when you need to quantify
qualitative information from users

User Feedback: You can ask users to give their opinions on the
product — their likes and dislikes, and if they would recommend
the product to others

VIJAY BANDARU WWW.LEARNOVATIVE.COM 35


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

How to select suitable User Research method?


Each User Research method has its own advantages and drawbacks, and it’s important to
understand which method to use depending on your product, your users, and the kind of
information you want to gather — information on what users think or what they do.

If you want to understand what users say or think, surveys, interviews and focus groups can
help you gauge their beliefs and attitudes. If, on the other hand, you want to focus on what
users do or how they use your product, methods like A/B testing and heatmaps are more
suitable.

Interviews are suitable for gathering qualitative data, whereas surveys are handier for
collecting quantitative data.

Select most appropriate User Research Technique for the below examples
Example scenario description Suitable User
Research Method
Your users are scattered across different locations and you do not have time
to meet everyone in person. But you need to understand their needs.
Your product is already into market and your users are using it. You want to
identify which features have issues with usability or performance issues based
on the information your received from your customer support team.
You have a new feature in your Product which has a complex navigation and
it is also longer. So how do you get inputs from users before implementing
the feature to make sure the navigation is correct?
You are planning your next major release planning. For that you would like to
get critical information from the users who are already using the current
version of your Product. How do you collect the feedback in this scenario?
One of the critical stakeholders has a language problem hence she cannot
explain you the requirement of the Product you are building. However she is
very critical stakeholder so how do you empathize with this Stakeholder?
You are a Product Owner for one of your company’s internal Product and
almost all your company employees will use this new Product. All your
employees are collocated so what is the best approach to collect the inputs?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 36


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Persona
✓ Fictional character who interacts with the Product/Service/Result
✓ Useful in considering the goals, desires, concerns
✓ Helps to identify the features based on different Personas
✓ Helps in:
o Coming up with better user experience
o Prevent some common design pitfalls
o Avoid “self-referential” designs
✓ Persona is key in building products that are close to customers’ needs

How to capture the Persona details?

Use Persona Canvas suggested by Roman Pichler. Explore this approach to get more
information.

Example Persona Canvas:

Let us take a problem statement and come up with a Product


Discuss as a team and come up with a Problem statement or a need for a segment of users. Identify
all possible Personas in the below table who are associated with that Problem or need.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 37


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Value Proposition Canvas


The Value Proposition Canvas is a tool which can help ensure that a product or service is
positioned around what the customer values and needs.

The Value Proposition Canvas was initially developed by Dr Alexander Osterwalder as a


framework to ensure that there is a fit between the product and market. It is a detailed look
at the relationship between two parts of the Osterwalder’s broader Business Model Canvas;
customer segments and value propositions.

The Value Proposition Canvas can be used when there is need to refine an existing product
or service offering or where a new offering is being developed from scratch.

The Value Proposition Canvas is formed around two building blocks – customer profile and a
company’s value proposition.

Customer Profile
• Customer jobs – the functional, social and emotional tasks customers are trying to perform,
problems they are trying to solve and needs they wish to satisfy.
• Gains – the benefits which the customer expects and needs, what would delight customers
and the things which may increase likelihood of adopting a value proposition.
• Pains – the negative experiences, emotions and risks that the customer experiences in the
process of getting the job done.

A customer profile should be created for each customer segment, as each segment has
distinct gains, pains and jobs.

Value Map
• Products and services – the products and services which create gain and relieve pain, and
which underpin the creation of value for the customer.
• Gain creators – how the product or service creates customer gains and how it offers added
value to the customer.
• Pain relievers – a description of exactly how the product or service alleviates customer
pains.

Achieving fit between the value proposition and customer profile


After listing gain creators, pain relievers and products and services, each point identified can
be ranked from nice to have to essential in terms of value to the customer. A fit is achieved
when the products and services offered as part of the value proposition address the most
significant pains and gains from the customer profile.

Identifying the value proposition on paper is only the first stage. It is then necessary to
validate what is important to customers and get their feedback on the value proposition.
These insights can then be used to go back and continually refine the proposition.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 38


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

VIJAY BANDARU WWW.LEARNOVATIVE.COM 39


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Example: Value Proposition Canvas for “A Taxi Smartphone”.

Create Value Proposition Canvas for your Product


Timebox: 12 Minutes

VIJAY BANDARU WWW.LEARNOVATIVE.COM 40


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Agile Product Planning (The Big Picture)

Planning is everything, Plans are nothing!

VIJAY BANDARU WWW.LEARNOVATIVE.COM 41


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

From the above planning levels, discuss and fill the following:
Planning Part of Scrum? How to represent? Who creates Review
Level Frequency
No Elevator Statement Product Owner Yearly once
Vision Vision Poster (Either creates
Press Release or co-creates)
One Pager
No Roadmap contains 2 to 3 Product Owner Twice an year
Roadmap Releases

No Release Plan Product Owner Quarterly


Release with the help of
Team(s)
Yes Sprint Goal & Scrum Team As per Sprint
Sprint Sprint Backlog duration (1 – 4
weeks)
Yes Sprint Backlog Development Daily
Daily Team

VIJAY BANDARU WWW.LEARNOVATIVE.COM 42


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Vision

VISION IS THE ART OF SEEING THINGS INVISIBLE


- Jonathan Swift

Product Vision helps you to “BEGIN with the END in the mind”
Product Vision indicates two factors.
______________ the Product is being Built and

_________________ is the desired end state

Vision covers the following:


• _________ will buy your product?
• Who is target ________________?
• What ____________ the Product will address?
• What are the critical _____________ factors?
• What are ____________ differentiating factors?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 43


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

A Good Product Vision should be:


B_____:
I_____:
C_____:
S_____:
Most popular Vision Statements:

Amazon: To be Earth’s most customer-centric company, where customers


can find and discover anything they might want to buy online.

Nike: Bring inspiration and innovation to every athlete* in the world. *If you
have a body, you are an athlete.

IKEA: To create a better everyday life for the many people.

Google: To organize the world’s information and make it universally


accessible and useful.

Loreal: To provide the best in cosmetics innovation to women and men


around the world with respect for their diversity.

Microsoft: To help people and businesses throughout the world realize


their full potential.

Product Vision can be created using following techniques:


➢ Elevator Statement
➢ Product Vision Box/Poster
➢ One Pager
➢ Press Release

VIJAY BANDARU WWW.LEARNOVATIVE.COM 44


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Advantages of Powerful Product Vision:

• Vision provides ___________ and helps the organization prepare for the future. 


• Vision provides guidance for __________-making. 



• Vision can help to __________ what you will and what you will not do. 


• Vision helps set ____________ and guides planning. 


• Vision _________ people and activities across the organization. 


• Vision provides __________ and a source of inspiration. 


• Vision __________ people and helps focus their efforts. 


Elevator Statement

Example Elevator Statement:


FOR < Those are into Product Management >
WHO < Wants to manage their Products better >
THE < CSPO > IS A < Scrum Alliance Certification >
THAT < makes you standing out of the crowd >
UNLIKE < Traditional Project Management Certifications >
OUR PRODUCT < Creates value for your money and shapes your
Career to become great Product Owners >

VIJAY BANDARU WWW.LEARNOVATIVE.COM 45


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Vision Box/Poster


The goal of PRODUCT VISION BOX/POSTER is to clarify the vision in detail so that everyone
will get clear understanding. This is to identify the Name with Logo and a tag line, outcomes
of the Product, most exciting product features, and key additional information.

Be sure to adorn the Poster with the key slogans, images, text and colors that would entice
your customers to “buy” this product.

Keep the following questions in mind when you create your Product Vision Box:

• Who? is the target customer for your product?


• What? does the product aim to achieve? How does it make user’s life easier or better?
• When? is the product expected to be delivered?
• Where? will the product be used? In which specific circumstances?
• Why? should users use this product instead of similar solutions to the problem?

Below is an example of Product Vision Poster for a reference.

Activity: Create your Product Vision using above two approaches (15 Minutes)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 46


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Prioritization

Source: Scrum inc.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 47


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

BUSINESS VALUE is the key to Prioritize the Product Backlog. Business Value can be related
to different aspects as listed below:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 48


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Prioritization Techniques
DOT Voting

MoSCoW

MUST:
SHOULD:
COULD:
WON’T:

Urgency Vs Importance Value Vs Cost

Few more methods to prioritize based on Business Value of Product Backlog Items:

- Value Poker (Relative weight by taking a reference value size and compare the rest)
- Break-even analysis (Cost of feature and expected revenue of the feature)
- Return on Investment ([Profit/Total estimated cost] * 100)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 49


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Activity: Create Epic/Feature map for your Product using the below template.
Create the map using post it notes. Using one of the above Prioritization
techniques, prioritize them.

Epic: A big chunk of functionality which takes beyond releases (months) (Eg: User
Management)

Feature: A coherent piece of Epic which is done in a release but beyond sprints (weeks)
(Eg: Register a new user using different ways)

User Story: A small portion of Feature which has some business value and can be done
within a Sprint (days) (Eg: A mobile user can register using his mobile number, A Facebook
user can register using his/her facebook id)

Note: Scrum does not recognize the above naming conventions. In Scrum terminology all
these items are called as “Product Backlog Items (PBIs)”

Note: Each small box is a User Story in the above diagram

VIJAY BANDARU WWW.LEARNOVATIVE.COM 50


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Roadmap

Steps involved in Product Roadmap creation:

1. Gather information (Audience, Technology, Market, Feature Backlog)


2. Organize into Timespan (Monthly/quarterly/half yearly)
3. Visualize (coarse-grained Features mapped to each release)
4. Buy-in (with Stakeholders and the team)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 51


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Goal Based Roadmap

Example Roadmap

VIJAY BANDARU WWW.LEARNOVATIVE.COM 52


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Tips to create effective Roadmaps:

1. Focus on Goals and Benefits


2. Do necessary Preparatory work
3. Tell a Coherent story
4. Keep it simple
5. Secure Strong Buy-in
6. Have the courage to say “No”
7. Know when to show dates
8. Make your Roadmap measurable
9. Determine cost top-down
10. Regularly review and adjust the Roadmaps

VIJAY BANDARU WWW.LEARNOVATIVE.COM 53


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product backlog
Product Backlog is like an iceberg,
you can see only the tip,
not the entire content !

Quick Formula for the ORDER RANK:


(Business Value weightage + Risk weightage)/Cost weightage =
ORDER RANK
(The Highest Order Rank value items are important and on Top)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 54


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

VIJAY BANDARU WWW.LEARNOVATIVE.COM 55


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Backlog recap: Fill the blanks in the below story to make it complete and
meaningful.

Once up on a time, there was a Product Owner named John. He started


a new Product based on an idea that he has got to solve a particular
problem. He created a _________________ to manage all the
requirements related to that product. He always ensures that all the
items that have high business ____________ and important and
urgent, and the items are in line with the product ____________ are
always kept on the ________ of the Product backlog. This helps John
to ______________ the product value. John allows anyone to add
new items to the ___________________ but he keeps the right of
______________ them. John takes his __________________ help
to estimate the backlog items during Product backlog ___________
or in the ______________ Planning. John always keeps the Product
backlog available to all so that it increases the
___________________. John always ensures that the higher order
items are __________ detailed and granular than the ________
order items. Even though there are more teams working on the
Product, John always maintains _________ Product backlog to
increase ______________ and reduce _____________ and to
____________ dependencies across the teams effectively. The
Product backlog contains the _________ (i.e., features) that helps
to achieve the __________ (i.e., product Vision).

VIJAY BANDARU WWW.LEARNOVATIVE.COM 56


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product backlog refinement

What happens in Product Backlog Refinement (PBR)?

Scrum Master facilitates the Product Backlog Refinement based on the need

VIJAY BANDARU WWW.LEARNOVATIVE.COM 57


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

User Stories

THREE “C”s of USER STORY

VIJAY BANDARU WWW.LEARNOVATIVE.COM 58


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Sample User story with Acceptance Criteria:

Another example user story:

User Story: As a Visa credit card user, I should be able to pay for the items in the shopping
cart using his/her card so that I can complete my shopping seamlessly

Acceptance criteria:
1. User credit card should be a Visa card
2. All other cards like Master, Amex cards payment should not be accepted
a. Message to show “Only Visa cards are allowed”
3. User card should have valid number of digits
4. Card CVV must be valid and 3 digits length
a. If invalid CVV then: “Wrong CVV, please try again”
5. Cards with expired should be rejected
a. Message: “Your card has expired, please try with another card”
6. Card holder name must be validated
a. Message: “Invalid card, please provide correct card holder name”
7. Different purchase amounts should work with positive amounts
8. Zero or negative amounts should be alerted
a. Message: “Amount should not be negative number”

Good acceptance criteria should be: SAFE

Success: What is the success criteria?


Advance: What has to happen before the success outcome can be reached?
Failure: What could go wrong and how can user be coped up?
Error: What are the error situations and what messages to be shown?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 59


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

“INVEST” of User Stories


Every user story should satisfy the “INVEST” principle in order to be a good user story. This
helps Scrum Teams to make it into working software quick and can deliver value to the
customer.

I_________________ –

N________________ –

V________________ –

E________________ –

S________________ –

T________________ –

VIJAY BANDARU WWW.LEARNOVATIVE.COM 60


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Splitting the user stories

Split the Stories vertically NOT horizontally

Splitting Techniques:
- Work flow steps pattern
- Operations pattern (CRUD)
- Simple to complex pattern
- Data entry patterns
- User Role/Persona based pattern
- Mock UI pattern
- Defer performance pattern
- Breakout a Spike pattern

VIJAY BANDARU WWW.LEARNOVATIVE.COM 61


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Example for Workflow steps pattern splitting:

Example for CRUD operations pattern splitting:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 62


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Simple to complex pattern splitting:

Data entry pattern splitting:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 63


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Story mapping

VIJAY BANDARU WWW.LEARNOVATIVE.COM 64


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Release Planning (Not part of core Scrum)

A very high-level plan for multiple sprints (E.g. 4 – 6 Sprints) is done during release planning.
It is a guideline that reflects expectations about which features will be implemented and when
they are completed. It also serves as base to monitor progress with the project.

Releases can be intermediate deliverables done during the project or the final delivery at
the end.
Prerequisites to create a Release Plan:
➢ A prioritized and estimated Product Backlog

➢ The estimated Velocity of the scrum team

➢ Conditions of satisfaction (goals for the schedule, scope, resources, cost etc.)

Depending on the type of project (Feature driven or Date driven) the release plan can be
created in different ways:

VIJAY BANDARU WWW.LEARNOVATIVE.COM 65


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

FIXED SCOPE (FEATURE DRIVEN) RELEASE PLANNING:

STEP 1:
The first step in fixed-scope release planning is to groom the product backlog to include at
least the product backlog items (PBIs) the organization must have in this release by creating,
estimating the size of, and prioritizing the PBIs that comprise the Minimally Releasable
Features.

STEP 2:
The second step in fixed-scope release planning is to determine the total size of the PBIs to
be delivered during the release. Do this by summing up the estimates of the must-have PBIs.

STEP 3:
The third step in fixed-scope release planning is to measure or estimate the team’s velocity
as a range.

STEP 4:
The fourth step in fixed-scope release planning is to divide the total size of the PBIs for the
release by the fastest velocity in the range. Round the answer up to the next integer. This will
indicate the lowest number of sprints required to deliver the features targeted for the release.

STEP 5:
The fifth step in fixed-scope release planning is to divide the total size of the PBIs for the
release by the slowest velocity in the range. Round the answer up to the next integer. This
will indicate the greatest probable number of sprints required to deliver the features targeted
for the release.

EXAMPLE
When asked how many sprints it will take to deliver the fixed scope, you can now answer
using a range: somewhere between the greatest probable number of sprints and the least
number of sprints. Suppose, for example, your features targeted for a release is estimated to
be 150 points, and the Scrum team’s predicted velocity range is 18-22 points per sprint. You
can estimate that the MRF will be delivered in 7-9 sprints. If you are running 2-week sprints,
this would equate to 14-18 weeks.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 66


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

FIXED DATE (DATE DRIVEN) RELEASE PLANNING:

STEP 1:
The first step in fixed-date release planning is to determine how many sprints are in the
release. If all sprint lengths are equal (which should be the ideal case), this is simple calendar
math, because you know when the first sprint will start and you know the delivery date.

STEP 2:
The second step in fixed-date release planning is to groom the product backlog to a sufficient
depth by creating, estimating the size of, and prioritizing product backlog items. You’ll need
enough PBIs to plan out to the fixed release date.

STEP 3:
The third step in in fixed-date release planning is to measure or estimate the
team’s velocity as a range.

STEP 4:
The fourth step in fixed-date release planning is to create a “will have” line by multiplying the
slowest number in the velocity range by the number of sprints. Count down that number of
points into the product backlog and draw a line.

STEP 5:
The fifth step in fixed-date release planning is to create the “might have” line by multiplying
the largest number in the velocity range by the number of sprints. Count down that number
of points into the product backlog and draw another line.

STEP 6:
The final step in fixed-date release planning is to compare the “will have” and “might
have” lines to the minimum releasable features (MRFs) in the product backlog. If all of the
must-have items are above the will have line, you are in great shape. If not, you will need to
decide whether to proceed as planned, revisit the MRFs, pivot, or terminate the project.
The image below shows several variations in how the must-have features (MRFs) might
compare to the will have and might have calculations from fixed-date release planning.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 67


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

After the Release Planning is done, the Scrum team starts Sprinting
to create potentially releasable product increment. Product Owner
closely collaborates with the Development team and the
Stakeholders to make effective decisions based on collaborative
discussions with them.
During each Sprint, the Development team tracks the progress of the work of Sprint using
some tracking mechanism. Most common approach is a “Sprint Burndown”.

Below are some example Burndown chars of a team which has different scenarios:

The Development Team updates the Sprint Burndown chart. Ideally it should be
updated as and when a user story is “Done”, or else at least once in a day it should
be updated.

VIJAY BANDARU WWW.LEARNOVATIVE.COM 68


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Tracking Progress through release Burndown chart:


Product Owner updates the Release Burnup/Burndown chart at the end of every Sprint. This
helps the Product Owner to update Stakeholders with the progress and also to make scope
vs time trade-off decisions.

Tracking Progress through release Burnup chart:

Blue line (Top) indicates the overall release backlog size. Till the 5th Sprint, it is same but in
Sprint 6 it has increased, that means some new work is added. Red line (bottom) indicates
the cumulative completion of the work in every Sprint. So, at the 8th Sprint, “Remaining work
to be complete” can be found by subtracting red line value (work complete) from the blue
line value (Total work). So, in the above it is 120 minus 97 which is 23. Now, to understand
how many more sprints it is needed to complete the 23 points of work, you have to check the
average velocity of all 8 Sprints. In the above it is: 12.125, let’s take 12. So now divide the 23
(remaining work) with 12 (Velocity) which gives the number of Sprints required to complete.
23/12 = 2 (rounded). This is how the Product owner will track the overall release progress.
VIJAY BANDARU WWW.LEARNOVATIVE.COM 69
CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Velocity

VIJAY BANDARU WWW.LEARNOVATIVE.COM 70


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product increment

** Only members of the Development Team create the Increment **


➢ Created by Development team
➢ Increment is the “Sum of all PBIs completed during the Sprint and the value of the
increments of all previous Sprints”
➢ The new increment must meet “Definition of Done”
➢ The increment must be in a usable condition irrespective of Product Owner wants to
release or not
➢ Is a small step towards the “Product Vision”

Reasons for releasing:


Customer Request
Market Opportunity
Required Release
Competitive Response
Major Release
Maintenance

VIJAY BANDARU WWW.LEARNOVATIVE.COM 71


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

APPENDIX

VIJAY BANDARU WWW.LEARNOVATIVE.COM 72


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Space for Notes

VIJAY BANDARU WWW.LEARNOVATIVE.COM 73


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Space for Notes

VIJAY BANDARU WWW.LEARNOVATIVE.COM 74


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Space for Notes

VIJAY BANDARU WWW.LEARNOVATIVE.COM 75


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

What makes you a Great Product Owner?

VIJAY BANDARU WWW.LEARNOVATIVE.COM 76


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Scrum Team Setup


Single Team setup

More than one Team setup

Scaled Team setup

VIJAY BANDARU WWW.LEARNOVATIVE.COM 77


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

Product Owner Anti-Patterns


1. One PO per Development Team instead of one PO per Product
2. Multiple PO for multiple smaller related “products” (e.g. PO for Android PowerPoint,
PO for iPhone PowerPoint, PO for Windows Desktop PowerPoint, PO for Mac
PowerPoint, PO for PowerPoint 365)
3. One PO per feature/component/epic (“feature” product owner, “component” Product
Owner, “epic” product owner)
4. One “onsite” PO & one “offshore” PO
5. PO being the bottleneck in communication, acting as in intermediator between the
team & stakeholders/customers increasing the number of “hops” in communication
6. PO not having the authority to terminate the Sprint
7. ex-BA now relabelled as PO – nothing changes in the work they do
8. PO not from Product Management or Product Marketing (if building external facing
product) or not from business (if building internal products)
9. Relabelling “project managers” to PO
10. “Technical” Product Owner (usually from engineering/IT), “proxy” Product Owner,
“functional” Product Owner ( i.e. functional managers are *relabelled* as Product
Owner e.g. “Dev” Product Owner, “QA” Product Owner)
11. PO not being a subject matter/domain expert and act as just order taker
12. PO having multiple Development Team level Product Backlog instead of having ONE
product backlog and multiple teams pulling from them
13. PO not understanding the customers/users of the Product and not understanding the
market
14. Others in the organization not respecting PO’s final decision on the Product Backlog
15. PO spoon-feeding the Development Team with Product Backlog items (duh!! seriously? )
instead of them writing it
16. PO & Development Team member being the same person
17. PO & Scrum Master being the same person
18. PO managing “Projects”, ”Programs” etc instead of “Product”
19. No Product Owner assigned to the Product
20. PO not meeting with the Dev. Team face to face periodically (if not co-located)

VIJAY BANDARU WWW.LEARNOVATIVE.COM 78


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

User Story Splitting Patterns

VIJAY BANDARU WWW.LEARNOVATIVE.COM 79


CERTIFIED SCRUM PRODUCT OWNER (CSPO) WORKSHOP

References for further Reading

www.pdfdrive.net is a great
online PDF books repository.
There are plenty of online books
available in there, so please try to
search for the books and read
them.
Google Drive Link:
https://tinyurl.com/CSPO-Vijay-Bandaru

VIJAY BANDARU WWW.LEARNOVATIVE.COM 80

You might also like