Scrum Product Owner
-
Upload
vishal-prasad -
Category
Business
-
view
114 -
download
6
description
Transcript of Scrum Product Owner
Scrum Product Owner
-by Vishal Prasad
Know Your Surroundings
What did I do
yesterday?
The Daily Scrum
What will I do today?
Are there any impediments in my
way?
Traditional Geometry
The Agile Manifesto
Agile Traditional
0 Individuals and Interactions
0 Working Software
0 Customer Collaboration
0 Responding to Change over
0 Processes and Tools
0 Comprehensive Documentation
0 Contract Negotiation
0 Following a Plan
Over
While there is value in the items on the right, we value the items on the left more.
Scrum Roles
Product Owner
Scrum Master
Development Team
Scrum FrameworkInputs from Executives,
Teams, Stakeholders, Customers, Users
Product BacklogSprint Backlog Task Breakout
Sprint Planning Meeting
Burndown/up Charts
Daily Scrum
1-4 Week Sprint
24 hours
Finished Work
Sprint Review
Sprint Retrospective
Scrooge – The Product Owner
0 Voice of his customers0 Discover needs0 Prioritize features0 Present a vision0 Detail the next features0 Responsible for ROI0 Manage stakeholders0 Accept / Reject work
results
Launchpad – The ScrumMaster
0 Ensure follow of process0 Remove blockers0 Ensure full productivity0 Enable co-operation0 Shield from interference0 Manage ceremonies0 Facilitate daily scrums0 Track progress
Huey, Dewey, Louie – The Development Team
0 Cross-functional team0 Negotiate sprint goal0 Specify work results0 Achieve committed goal0 Self organizing team0 Define processes0 Demonstrate work
results to product owner
An Idea!I have a new money making plan and I
need your help.
My goal is to develop a brochure for a club in a 3
day sprint
Conduct a sprint planning meeting in 12 mins. Decompose tasks from my backlog. Estimate
tasks, and commit delivery.
Scrooge’s Backlog
0 Create cover art, brand, and/or logo
0 Provide contact details0 Outline full week lunch
menu0 Outline minimum
requirements0 Define service offerings0 Write testimonials
Mini Scrum
0 Conduct a Sprint Day 1 – 8 minutes – deliver!0 Conduct a Daily Scrum – 3 minutes0 Conduct a Sprint Day 2 – 8 minutes – deliver!0 Conduct a Daily Scrum – 3 minutes0 Conduct a Sprint Day 3 – 8 minutes – deliver!0 Conduct a Sprint Review and Demo – 13 minutes0 Debrief as a group – 5 minutes0 Make it creative and fun!
Scrooge’s Vision
For working families, who prefer personal attention
for their single parent, “2nd Home” is an elderly
daycare club that provides a nursing
environment along with socializing activities, unlike “Next Steps”
Scrooge’s Acceptance Criteria
0 Cover art, brand, & logo0 Pink / Gold0 Must have the two word
brand name0 Must contain a happy
picture of an elderly person
0 Lunch menu0 7 different “themed
buffet” with pictures
0 Services offered0 5 different services out
of 39 including transport
0 Must include our new “Foot Spa” service
0 Architectural conformance0 Max A4 size0 No loose sheets0 Must fit in a handbag
Peer Consensus
0 Each member write their view of the vision
0 Highlight 3 keywords each
0 Write one word per post-it
0 Re-arrange words to come up with a vision statement
0 Add / Change words as needed
DRIVEN Product Owner
0 Decisive0 Realistic0 Informed0 Visionary0 Empowered0 Negotiable
Scrooge has the right to cancel the project at anytime and be left with a working system reflecting investment to date.
RE-TRAINED ScrumMaster
0 Resourceful0 Enabler0 Tactful0 Respected0 Argumentative0 Integrity0 Networked0 Empathetic Listener0 Determined
Generalized Specialist Team
0Cross – Functional0Self – Organized0Motivated0Collaborative0Communicative0Experimental Nature0Team Player0Courageous
Software Economics
You are working at a burger joint and are the only person on duty. A customer approaches and orders a Cheese Burger Deluxe Meal, with chicken wings, large fries, and a large drink.
The order sums up to INR 157 with taxes. The customer informs you that he has only INR 78.
What do you do and what do you tell the customer?
Technical DebtPr
ojec
t Bur
n D
own
TimeTechnical Debt
Deadline
Optimal Quality
Managerial Pressure
Ideal Quality
Sprint n
Vertical Slices
Database – Design, Code, Test, Integrate, Accept
Data Access Layer – Design, Code, Test, Integrate, Accept
Business Layer – Design, Code, Test, Integrate, Accept
Application Layer – Design, Code, Test, Integrate, Accept
User Interface – Design, Code, Test, Integrate, Accept
Sprint 1 Sprint 2 Sprint 3
The Product Vision
0 The product vision tells us how we are going to satisfy the customer needs0 Value proposition and key characteristics
0 What the vision should answer:0 Who is the customer?0 What is the customer’s problem0 How does the product solve the problem?0 How does the product add value?0 What are the benefits compared to others?0 On what basis will the customer judge it?
Elevator Statement & Product Box
For [frequent travelers]Who [want an all in one travel service][Travel Mate] is a [virtual travel agent]That [will do everything for my trip]Unlike [Itinerary Planner]Our Product [will remove the need to visit any other website or shop for a trip]
ClickBook
Fly
Create a Product
0 Your company has decided to diversify into a booking new area – an online travel assistant
0 Come up with your:0 Product Name0 Niche0 Elevator Statement0 Product Box
Brainstorm for user roles
0 Most projects talk about “the user” or “users”
0 But who are they? What do they want?
0 Most projects:0 Write requirements from one user’s perspective0 Assuming all users have the same goals0 End up with “missing” requirements
Personas
Peter
Peter is a 55 year old explorer who loves to visit new places.
He is a software engineer with a laid back lifestyle and enjoys his occasional drink with buddies at a sports bar.
He likes to do his research in detail before his travel since his wife generally accompanies him on his trips.
He would love to have a one stop web solution to plan out his trips – from travel, to accommodation, to activities, etc.
Name &
Picture …
Who?
Characteristics…
Who?
Why?
Types of Personas
0 Focal – Primary users. Optimize the design for them. At least one persona must be focal.
0 Secondary – Also use the product. Satisfy their requirements when possible.
0 Unimportant – Low priority users, including infrequent, unauthorized, or unskilled users, as well as those who misuse the product.
0 Affected – They don’t use the product but are affected by it.
0 Exclusionary – Someone we’re not designing for. Useful to prevent nonusers from our discussions.
Product Backlog
Sprint - 20%
Release - 20%
Future Releases - 60%
Prio
rity
DEEP Backlog
0 Detailed
0 Estimated
0 Emergent
0 Prioritized
User Stories
As a … (user of the system)
I want … (feature or problem to be solved)
So that … (benefit of the story being completed)
The “so that” part is incredibly valuable as it focuses people on the real reason behind this requirement.
INVEST in User Stories
0 Independent0 Negotiable0 Valuable0 Estimable0 Small0 Testable
The Tea Drinker
Write a user story to make yourself a cup of tea.
As a tea drinker, I want
a cup of tea so that I
can drink it As Peter, I want a cup of tea so that I can drink it
As Peter, I want a cup
of tea so that I can
quench my thirst
As Peter, I want an isotonic drink so that I can quench my thirst
Acceptance Test
0 When will this story be done?
0 What will we see?0 What will happen?0 What will be different?0 When will the team
stop?0 What are the conditions
for functionality, usability, and security being satisfied?
Acceptance Criteria
0 Different levels of acceptance
0 Keep to appropriate level
0 When will this story be “done”?
0 Questions can help0 Make them objective0 Make them automated
Prioritization
0 Shouting Loudest
0 Priority Poker
0 Kano Analysis
0 “35”
0 Free Market
0 Risk & Value
If everything is equally
important then
everything must be
equally unimportant.
- David B. Clarke
The Sinking Ship
0 Manmohan Singh
0 Narayan Murthy
0 Sachin Tendulkar
0 Sanjay Dutt
0 Zakir Hussain
0 Narendra Modi
0 Mukesh Ambani
0 Kailash Kher
0 Amitabh Bachchan
0 Rakhi Sawant
Your ship is sinking. It has a lifeboat that can carry only one person along with you to safety. In which order will you save these people.
Risk & ValueR
isk
Value
Avoid
Do Last Do Next
Do First
KANO ModelCu
stom
er S
atis
fact
ion
Feature Presence
Exciters & Delighters
Threshold Must-haveLinear
Planning Poker
Definition of Done
“What do we need to do, as a team, to ship software to our customers/stakeholders?”
- By Mitch Lacey
Sprint Planning
0 Define the sprint goal
0 Identify capacity
0 Create sprint backlog
0 Commit deliverables
0 Task breakout
Themes
0 Themes are group of similar functionality / requirement.
0 These can span across sprints, releases, or products.
0 Themes can be used for prioritizing requirements.
Product Canvas
- By Roman Pichler
Task Board
Velocity
0 Amount of work finished
0 Not a sprint prediction
0 Long term measure of capacity
0 Not comparable across teams
Release Planning
Sprint 5 Sprint 6 Sprint 7Sprint 8
(Release)Backlog
Metrics
0 Burndown
0 Burnup
0 Forecasting Velocity
0 Focus Factor
0 Creative Rewards!
When should you not do Agile?
0 Car pointing culture
0 Long working hours
0 Huge team size
0 Lack of integration
0 Exponential cost curve
0 Long feedback loop
Sprint Review & Retrospective
0 Start – Stop – Continue
0 Mad – Sad – Glad
0 Sail Boat
0 The Wheel – Start, Stop, Continue, More, Less
Appreciations
Risks
Puzzles
Wishes
Actions
ReferencesTitle Author
Succeeding with Agile: Software Development Using Scrum Mike Cohn
Agile Estimation and Planning Mike Cohn
Agile Product Management with Scrum Roman Pichler
Agile Retrospectives Ester Derby, Diana Larsen
Agile Software Development with Scrum Ken Schwabber, Mike Beedle
Agile Testing: A Practical Guide for Testers and Agile Teams Lisa Crispin, Janet Gregory
Clean Code Martin
Continuous Integration Paul Duvali
Extreme Programming Explained Kent Beck
Extreme Programming Installed Jeffries, Anderson, Hendrickson
References (Contd…)Title Author
How Do We Know When We Are Done? Mitch Lacey
Implementing Lean Software DevelopmentMary Poppendieck, Tom Poppendieck
Planning Extreme Programming Kent Beck, Martin Fowler
Pragmatic Project Automation Clark
Project Retrospectives: A Handbook for Team Reviews Norman L. Kerth
Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience
Arlo Belshee
Refactoring: Improving the Design of Existing Code Fowler
Retrospectives – The Missing Practice Tim Mackinnon
Scrum PrimerPete Deemer, Gabrielle Benefield, Craig Larman
References (Contd…)Title Author
Test Driven Development By Example Kent Beck
The Art of Agile Development James Shore
User Stories Applied Mike Cohn
What is Definition of Done (DoD)? Dhaval Panchal
Selling Agile – How to Respond to Concerns from Management, the Business, and the Team
Michelle Sliger, Stacia Broderick
The Scrum Field Guide Mitch Lacey
Collaboration Explained Jean Tabaka
The Pragmatic Programmer Hunt, Thomas
Agile & Iterative Development Craig Larman
References (Contd…)Title Author
Agile Coaching Rachel Davis, Liz Sedley
Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition
Lyssa Adkins
Lean from the Trenches: Managing Large-Scale Projects with Kanban
Henrik Kniberg
DSDM: Business Focused DevelopmentDSDM Consortium, Jennifer Stapleton
Be Agile!Happy Scrumming.