Know Your Surroundings
The Daily Scrum
What will I do today?
Traditional Geometry
The Agile Manifesto
Agile Traditional
0 Individuals and
Interactions
0 Working Software
0 Customer Collaboration
0 Respond...
Scrum Roles
Product
Owner
Scrum
Master
Development
Team
Scrum Framework
Inputs from Executives,
Teams, Stakeholders,
Customers, Users
Product Backlog
Sprint Backlog
Task Breakout...
Scrooge – The Product Owner
0 Voice of his customers
0 Discover needs
0 Prioritize features
0 Present a vision
0 Detail th...
Launchpad – The
ScrumMaster
0 Ensure follow of process
0 Remove blockers
0 Ensure full productivity
0 Enable co-operation
...
Huey, Dewey, Louie – The
Development Team
0 Cross-functional team
0 Negotiate sprint goal
0 Specify work results
0 Achieve...
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 sprin...
Scrooge’s Backlog
0 Create cover art, brand,
and/or logo
0 Provide contact details
0 Outline full week lunch
menu
0 Outlin...
Mini Scrum
0 Conduct a Sprint Day 1 – 8 minutes – deliver!
0 Conduct a Daily Scrum – 3 minutes
0 Conduct a Sprint Day 2 – ...
Scrooge’s Vision
For working families, who
prefer personal attention
for their single parent,
“2nd Home” is an elderly
day...
Scrooge’s Acceptance Criteria
0 Cover art, brand, & logo
0 Pink / Gold
0 Must have the two word
brand name
0 Must contain ...
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-...
DRIVEN Product Owner
0 Decisive
0 Realistic
0 Informed
0 Visionary
0 Empowered
0 Negotiable
Scrooge has the right to cance...
RE-TRAINED ScrumMaster
0 Resourceful
0 Enabler
0 Tactful
0 Respected
0 Argumentative
0 Integrity
0 Networked
0 Empathetic ...
Generalized Specialist Team
0 Cross – Functional
0 Self – Organized
0 Motivated
0 Collaborative
0 Communicative
0 Experime...
Software Economics
You are working at a burger joint and are
the only person on duty. A customer
approaches and orders a C...
Technical Debt
ProjectBurnDown
Time
Technical Debt
Deadline
Optimal
Quality
Managerial
Pressure
Ideal
Quality
Sprint n
Vertical Slices
Database – Design, Code, Test, Integrate, Accept
Data Access Layer – Design, Code, Test, Integrat...
The Product Vision
0 The product vision tells us how we are going to satisfy the
customer needs
0 Value proposition and ke...
Elevator Statement & Product
Box
For [frequent travelers]
Who [want an all in one
travel service]
[Travel Mate] is a [virt...
Create a Product
0 Your company has
decided to diversify into a
booking new area – an
online travel assistant
0 Come up wi...
Brainstorm for user roles
0 Most projects talk about “the user” or “users”
0 But who are they? What do they want?
0 Most p...
Personas
Peter
Peter is a 55 year old
explorer who loves to
visit new places.
He is a software engineer
with a laid back l...
Types of Personas
0 Focal – Primary users. Optimize the design for them. At least one
persona must be focal.
0 Secondary –...
Product Backlog
Sprint - 20%
Release - 20%
Future Releases - 60%
Priority
DEEP Backlog
0 Detailed
0 Estimated
0 Emergent
0 Prioritized
User Stories
The “so that” part is incredibly valuable as it focuses people on the real reason
behind this requirement.
INVEST in User Stories
0 Independent
0 Negotiable
0 Valuable
0 Estimable
0 Small
0 Testable
The Tea Drinker
Write a user story to make yourself a cup of tea.
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 w...
Acceptance Criteria
0 Different levels of
acceptance
0 Keep to appropriate
level
0 When will this story be
“done”?
0 Quest...
Prioritization
0 Shouting Loudest
0 Priority Poker
0 Kano Analysis
0 “35”
0 Free Market
0 Risk & Value
The Sinking Ship
0 Manmohan Singh
0 Narayan Murthy
0 Sachin Tendulkar
0 Sanjay Dutt
0 Zakir Hussain
0 Narendra Modi
0 Muke...
Risk & Value
Risk
Value
Avoid
Do Last Do Next
Do First
KANO Model
CustomerSatisfaction
Feature Presence
Exciters &
Delighters
Threshold
Must-have
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.
...
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 7
Sprint 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 Exponen...
Sprint Review &
Retrospective
0 Start – Stop – Continue
0 Mad – Sad – Glad
0 Sail Boat
0 The Wheel – Start, Stop,
Continue...
References
Title Author
Succeeding with Agile: Software Development Using Scrum Mike Cohn
Agile Estimation and Planning Mi...
References (Contd…)
Title Author
How Do We Know When We Are Done? Mitch Lacey
Implementing Lean Software Development
Mary ...
References (Contd…)
Title Author
Test Driven Development By Example Kent Beck
The Art of Agile Development James Shore
Use...
References (Contd…)
Title Author
Agile Coaching Rachel Davis, Liz Sedley
Coaching Agile Teams: A Companion for ScrumMaster...
Be Agile!
Happy Scrumming.
Scrum Product Owner
Upcoming SlideShare
Loading in...5
×

Scrum Product Owner

895

Published on

Scrum Product Owner Training Slides.

Published in: Software
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
895
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
39
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Scrum Product Owner"

  1. 1. Know Your Surroundings
  2. 2. The Daily Scrum What will I do today?
  3. 3. Traditional Geometry
  4. 4. 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.
  5. 5. Scrum Roles Product Owner Scrum Master Development Team
  6. 6. Scrum Framework Inputs from Executives, Teams, Stakeholders, Customers, Users Product Backlog Sprint Backlog Task Breakout Sprint Planning Meeting Burndown/up Charts Daily Scrum 1-4 Week Sprint 24 hours Finished Work Sprint Review Sprint Retrospective
  7. 7. Scrooge – The Product Owner 0 Voice of his customers 0 Discover needs 0 Prioritize features 0 Present a vision 0 Detail the next features 0 Responsible for ROI 0 Manage stakeholders 0 Accept / Reject work results
  8. 8. Launchpad – The ScrumMaster 0 Ensure follow of process 0 Remove blockers 0 Ensure full productivity 0 Enable co-operation 0 Shield from interference 0 Manage ceremonies 0 Facilitate daily scrums 0 Track progress
  9. 9. Huey, Dewey, Louie – The Development Team 0 Cross-functional team 0 Negotiate sprint goal 0 Specify work results 0 Achieve committed goal 0 Self organizing team 0 Define processes 0 Demonstrate work results to product owner
  10. 10. 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.
  11. 11. Scrooge’s Backlog 0 Create cover art, brand, and/or logo 0 Provide contact details 0 Outline full week lunch menu 0 Outline minimum requirements 0 Define service offerings 0 Write testimonials
  12. 12. Mini Scrum 0 Conduct a Sprint Day 1 – 8 minutes – deliver! 0 Conduct a Daily Scrum – 3 minutes 0 Conduct a Sprint Day 2 – 8 minutes – deliver! 0 Conduct a Daily Scrum – 3 minutes 0 Conduct a Sprint Day 3 – 8 minutes – deliver! 0 Conduct a Sprint Review and Demo – 13 minutes 0 Debrief as a group – 5 minutes 0 Make it creative and fun!
  13. 13. 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”
  14. 14. Scrooge’s Acceptance Criteria 0 Cover art, brand, & logo 0 Pink / Gold 0 Must have the two word brand name 0 Must contain a happy picture of an elderly person 0 Lunch menu 0 7 different “themed buffet” with pictures 0 Services offered 0 5 different services out of 39 including transport 0 Must include our new “Foot Spa” service 0 Architectural conformance 0 Max A4 size 0 No loose sheets 0 Must fit in a handbag
  15. 15. 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
  16. 16. DRIVEN Product Owner 0 Decisive 0 Realistic 0 Informed 0 Visionary 0 Empowered 0 Negotiable Scrooge has the right to cancel the project at anytime and be left with a working system reflecting investment to date.
  17. 17. RE-TRAINED ScrumMaster 0 Resourceful 0 Enabler 0 Tactful 0 Respected 0 Argumentative 0 Integrity 0 Networked 0 Empathetic Listener 0 Determined
  18. 18. Generalized Specialist Team 0 Cross – Functional 0 Self – Organized 0 Motivated 0 Collaborative 0 Communicative 0 Experimental Nature 0 Team Player 0 Courageous
  19. 19. 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?
  20. 20. Technical Debt ProjectBurnDown Time Technical Debt Deadline Optimal Quality Managerial Pressure Ideal Quality
  21. 21. 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
  22. 22. The Product Vision 0 The product vision tells us how we are going to satisfy the customer needs 0 Value proposition and key characteristics 0 What the vision should answer: 0 Who is the customer? 0 What is the customer’s problem 0 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?
  23. 23. 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]
  24. 24. 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 Name 0 Niche 0 Elevator Statement 0 Product Box
  25. 25. 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 perspective 0 Assuming all users have the same goals 0 End up with “missing” requirements
  26. 26. 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.
  27. 27. 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.
  28. 28. Product Backlog Sprint - 20% Release - 20% Future Releases - 60% Priority
  29. 29. DEEP Backlog 0 Detailed 0 Estimated 0 Emergent 0 Prioritized
  30. 30. User Stories The “so that” part is incredibly valuable as it focuses people on the real reason behind this requirement.
  31. 31. INVEST in User Stories 0 Independent 0 Negotiable 0 Valuable 0 Estimable 0 Small 0 Testable
  32. 32. The Tea Drinker Write a user story to make yourself a cup of tea.
  33. 33. 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?
  34. 34. Acceptance Criteria 0 Different levels of acceptance 0 Keep to appropriate level 0 When will this story be “done”? 0 Questions can help 0 Make them objective 0 Make them automated
  35. 35. Prioritization 0 Shouting Loudest 0 Priority Poker 0 Kano Analysis 0 “35” 0 Free Market 0 Risk & Value
  36. 36. 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.
  37. 37. Risk & Value Risk Value Avoid Do Last Do Next Do First
  38. 38. KANO Model CustomerSatisfaction Feature Presence Exciters & Delighters Threshold Must-have
  39. 39. Planning Poker
  40. 40. Definition of Done “What do we need to do, as a team, to ship software to our customers/stakeholders?” - By Mitch Lacey
  41. 41. Sprint Planning 0 Define the sprint goal 0 Identify capacity 0 Create sprint backlog 0 Commit deliverables 0 Task breakout
  42. 42. 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.
  43. 43. Product Canvas - By Roman Pichler
  44. 44. Task Board
  45. 45. Velocity 0 Amount of work finished 0 Not a sprint prediction 0 Long term measure of capacity 0 Not comparable across teams
  46. 46. Release Planning Sprint 5 Sprint 6 Sprint 7 Sprint 8 (Release) Backlog
  47. 47. Metrics 0 Burndown 0 Burnup 0 Forecasting Velocity 0 Focus Factor 0 Creative Rewards!
  48. 48. 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
  49. 49. 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
  50. 50. References Title 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
  51. 51. References (Contd…) Title Author How Do We Know When We Are Done? Mitch Lacey Implementing Lean Software Development Mary 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 Primer Pete Deemer, Gabrielle Benefield, Craig Larman
  52. 52. 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
  53. 53. 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 Development DSDM Consortium, Jennifer Stapleton
  54. 54. Be Agile! Happy Scrumming.

×