Mastering Prioritisation_ A Strategic Approach to Product Backlog Management (1).pptx

JohnBarratt7 33 views 54 slides Jul 18, 2024
Slide 1
Slide 1 of 54
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
45
Slide 46
46
Slide 47
47
Slide 48
48
Slide 49
49
Slide 50
50
Slide 51
51
Slide 52
52
Slide 53
53
Slide 54
54

About This Presentation

Slides From Agile Alliance Manchester 2024


Slide Content

Mastering Prioritisation: A Strategic Approach to Product Backlog Management Contributors John Barratt Version 1.0

Welcome [email protected] ‹#› Agile Coaching Training Systemic Modelling Practitioner

What brought you to be at the conference today? Icebreaker

By the end of this session you will be able to Analyze real-world examples to understand the practical effectiveness of Clean Language in various situations Grasp the essentials of Clean Language and its role in Product Backlog Management. Learn to employ Clean Language for clearer articulation and understanding of product backlog items and their customer impact. Apply Clean Language in realistic scenarios to prioritise product features effectively.

What is Clean Language? Clean Language is a communication technique developed by David Grove, designed to minimize the influence of the questioner's assumptions and biases. Key Principles: Neutrality Clarity Exploration

Why Clean Language and Agile Work? Enhances communication and understanding Helps in identifying underlying issues Facilitates more aligned decision-making Clean Language is particularly useful in agile for improving collaboration , prioritising features , and ensuring that all team members' perspectives are heard and valued .

Blue Brain Green Brain Red Brain Persecutor Rescuer Victim Evidence Inference Impact Problem Outcome Action Clean Interviewing: For Product Development https://bit.ly/3WnqRJE Join me online is September or October in the Wirral Promo code: Event10 What would you like to have happen? Then what happens? What will you see or hear? what needs to happen for … to turn it into an action? What kind of X? Is there anything else about X? What happens before? Tomorrow Tomorrow

What is bias? A bias is a systematic error in thinking that occurs when people are processing and interpreting information in the world around them and affects the decisions and judgments that they make . https://www.verywellmind.com/what-is-a-cognitive-bias-2794963 ‹#›

Why is Bias Bad? Are Contactless payments insecure? ‹#› You might build the wrong thing!

What Can Help? “Clean Interviewing , aims to maximise the reliability that information collected during an interview derives from the interviewee” https://en.wikipedia.org/wiki/Clean_language_interviewing ‹#›

Now let’s give it a go Save the Planet!

Evidence , Inference & Impact Evidence: What did you see or hear? Travelling to Manchester creates less greenhouse gasses then traveling to Texas Inference: What are you making up about what you saw/heard? I can still support the Agile Alliance, connect with people and learn lots without the extra travel Impact: What happened or could happen as a result ? Do my bit to Save the planet! ‹#›

Evidence , Inference & Impact Evidence: What did you see or hear? Travelling to Manchester creates less greenhouse gasses then traveling to Texas Inference: What are you making up about what you saw/heard? I can still support the Agile Alliance, connect with people and learn lots without the extra travel Impact: What happened or could happen as a result ? Do my bit to Save the planet! ‹#›

Questions to Find … Evidence Inference What did you see/hear? What did they do/say? Can you give me an example? What did you do/say? What was happening in the room? Impact What did that mean for you? What was that like? What did you think about this? What did you make up about that? What impact did this have? What happened next? Then what happened? What was the consequence of that? ‹#›

Interview Practise Continue the conversation on w hat brought you to be here today? Person 1 – Interviewee - Answers the questions honestly Person 2 – Interviewer – Tries to find out the Evidence, Inference and Impact Switch so you have time to play each role - 3 mins each ‹#›

Questions to Find … Evidence Inference What did you see/hear? What did they do/say? Can you give me an example? What did you do/say? What was happening in the room? Impact What did that mean for you? What was that like? What did you think about this? What did you make up about that? What impact did this have? What happened next? Then what happened? What was the consequence of that? ‹#› <<8:00->>

Reflections Grasp the essentials of Clean Language

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Ordering Product Backlog items Developing and explicitly communicating the Product Goal Creating and clearly communicating Product Backlog items Ensuring that the Product Backlog is transparent, visible and understood.

Scenario We are the team responsible for delivering the Agile Alliance E uropean edition conference. After a lower than expected number of registrations this year we need to work on a new strategy to make next year's conference a success. 5 TBC

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Developing and explicitly communicating the Product Goal

What Is A Product Goal? “describes a future state of the product ... is the long-term objective ... They must fulfill (or abandon) one objective before taking on the next.” ‹#› Scrum Guide - Source: https://scrumguides.org/scrum-guide.html#product-backlog

Source: https://thedecisionlab.com/biases/negativity-bias

‹#› "Focus on the outcome, not the obstacle. The direction of your focus is the direction your life will move. Let yourself move toward what is good, valuable, strong and true." www.greatday.com Ralph Marston

Cleanness Rating Classically Clean Strongly Leading Contextually Clean Mildly Leading And when…W hat would you like to have happen? Interviewer: What did you think of this year's conference? I agree, we should do it in London next year! What would make it better? Interviewee: It’s been a disaster ‘Not enough people registered for the conference, I agree, Do you think a different location would have helped? Interviewer: … https://en.wikipedia.org/wiki/Clean_language_interviewing ‹#› Interviewee: A financially viable conference that helps people grow as agile professionals Purpose: Developing and explicitly communicating the Product Goal

Interview Practise Using the scenario Interview the Product Owner to try move them from Problem to an Outcome to create the Product goal Person 1 – Product Owner - Answers the questions honestly Person 2 – Scrum Master – Tries to find out the Outcome whilst staying ‘Cleanish’ Switch so you all have time to play each role - 3 mins each + Feedback ‹#›

Cleanness Rating Classically Clean Strongly Leading Contextually Clean Mildly Leading And when…What would you like to have happen? Interviewer: What did you think of this year's conference? I agree, we should do it in London next year! I hope you agree What would make it better? Interviewee: It’s been a disaster ‘Not enough people registered for the conference, I agree, Do you think a different location would have helped? Interviewer: … Purpose : Developing and explicitly communicating the Product Goal https://en.wikipedia.org/wiki/Clean_language_interviewing ‹#› <<8:00->> And then what happens…

Reflections Developing and explicitly communicating the Product Goal

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Developing and explicitly communicating the Product Goal Creating Product Backlog items

Cleanness Rating Classically Clean Strongly Leading Contextually Clean Mildly Leading And what needs to be done for… to happen? Interviewer: and when It’s been a disaster as not enough people registered for the conference, what would you like to have happen? W e should do it in London next year that will solve the problem What kind of…? Interviewee: A financially viable conference that helps people grow as agile professionals Do you think a different location would help? Interviewer: … Purpose: Creating Product Backlog items https://en.wikipedia.org/wiki/Clean_language_interviewing ‹#›

Example Problem Outcome Ask ‘what would you like to have happen’, and if needed, ‘Then what happens’ Action Outcome: A financially viable conference that helps people grow as agile professionals Secure a Venue Develop a Conference Agenda Invite Keynote Speakers Organise Interactive Workshops Plan Networking Dinners Etc Etc Something that you’ve got, and you don’t want it Something you have not got yet but you would like Something useful that you can do to create or maintain what you want. ‹#› Problem: Not enough people registered for the conference Ask, what needs to be done for ‘A financially viable conference that helps people grow as agile professionals’ to happen?

Interview Practise Using the scenario Interview the Product Owner to try move them from Outcome to a high-level Product backlog Person 1 – Product Owner - Answers the questions honestly Person 2 – Scrum Master – Tries to find out actionable backlog items whilst staying ‘Cleanish’ Switch so you both have time to play each role - 5 mins each + Feedback ‹#›

Cleanness Rating Classically Clean Strongly Leading Contextually Clean Mildly Leading And what needs to be done for… to happen? Interviewer: and when It’s been a disaster as not enough people registered for the conference, what would you like to have happen? We should do it in London next year that will solve the problem What kind of…? Interviewee: A financially viable conference that helps people grow as agile professionals Do you think a different location would help? Interviewer: … https://en.wikipedia.org/wiki/Clean_language_interviewing ‹#› <<12:00->> Purpose: Creating Product Backlog items

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Ordering Product Backlog items Developing and explicitly communicating the Product Goal Creating and clearly communicating Product Backlog items

‹#› Product Backlog Refinement “is the act of breaking down and further defining Product Backlog items into smaller more precise items” “ongoing activity to add details, such as a description , order, and size” Conducted in the current Sprint for optionally no more than 1-2 Sprints ahead. PBR

Why Product Backlog Refinement? Scrum dedicates time for Backlog Refinement as it is a learning and knowledge sharing activity. It is about clarifying with the Scrum Team the required knowledge so, they can have a shared understanding of the work to then self-manage around. “By the act of refinement of Product Backlog Items, we strive to cope with uncertainty and to reduce the risk , so that we can work on considered items with more confidence ” ‹#› Source - Piotr Górajek: https://medium.com/serious-scrum/endless-and-boring-product-backlog-refinement-meetings-e98f6a4a46ed

User Story A marker for “a promise for a conversation” Alistair Cockburn Agile Manifesto Co-Author Stories are not….. a Business Requirement Documentation Analysis Detail A way to avoid talking Use Cases Mandated in Scrum For Analysts only Only formatted one way Meant to be known in entirety upfront So what is a Story? ‹#›

‹#› Evidence Based … “A user story is nothing more than an agreement that the customer and developers will talk together about a feature.” Kent Beck, Martin Fowler, p46.

User Story Examples Worksheet

Interview Practise Using the user stories provided or your own refine the backlog using ‘cleanish’ questions Person 1 – Product Owner - Answers and asks questions provides a value score Person 2 – Developer– Answers and asks questions provides a size score Order your 5 backlog items (or as many as you get through) ‹#›

Worked Example Feature: Secure a Venue: As a conference organiser, I want to secure a venue with appropriate facilities so that attendees have a comfortable and conducive environment for the event. 1. Articulating Feature Descriptions: Developers: What kind of venue are we looking for? Product Owner: The venue should have modern facilities, adequate seating, breakout rooms, and be fully accessible. Additionally, it should be centrally located, easily accessible by public transport, and have sufficient parking. 2. Evaluating Customer Value: Developers: How does securing this venue benefit our attendees and organisers? Product Owner: It provides a comfortable environment for attendees, which enhances their overall satisfaction. A centrally located venue makes it easier for more people to attend, increasing our potential reach and impact, thus supporting our goal of helping people grow as agile professionals. Purpose: C learly communicating Product Backlog items and then Ordering Product Backlog items

Worked Example continued 3. Creating Acceptance Criteria: Developers: How will we know the venue is working as intended? Product Owner: We will receive positive feedback from attendees about the venue’s facilities, location, and overall comfort. Smooth operation of all planned events without logistical issues will also indicate success. 4. Balancing Feasibility and Impact: Product Owner: How feasible is it to secure this type of venue within our budget and timeframe? Developers: It’s feasible if we can confirm availability within the budget and required dates. Securing a centrally located venue that is accessible can attract more attendees, thus contributing to a financially viable conference. We'll need to coordinate site visits, negotiate terms, and finalize the booking agreement. Purpose: Clearly communicating Product Backlog items and then Ordering Product Backlog items

Interview Practise Using the user stories provided or your own refine the backlog using ‘cleanish’ questions Person 1 – Product Owner - Answers and asks questions provides a value score Person 2 – Developer– Answers and asks questions provides a size score Order your 5 backlog items (or as many as you get through) ‹#› <<15:00->>

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Ordering Product Backlog items Developing and explicitly communicating the Product Goal Creating and clearly communicating Product Backlog items

Reflections Clearly communicating Product Backlog items and then Ordering Product Backlog items

What is Product Backlog Management Product Backlog management includes: https://scrumguides.org/scrum-guide.html#product-owner Ordering Product Backlog items Developing and explicitly communicating the Product Goal Creating and clearly communicating Product Backlog items Ensuring that the Product Backlog is transparent, visible and understood.

Discuss this scenario and other ways you could use Clean Interviewing in your work? Ensuring that the Product Backlog is transparent, visible and understood

Startup Alignment Challenge: Misaligned expectations and unclear requirements. Solution: Facilitated workshops using Clean Language to articulate and align visions. Outcome: Clear, shared requirements and improved team collaboration.

Educational Setting Challenge: Diverse learning needs of students. Solution: Applied Clean Language techniques to identify individual learning styles. Outcome: Tailored teaching methods that improved student engagement and performance.

Discovery Findings Internal What were the overall themes? ‹#› A Strong Foundation Levels of engagement in our evolution are extremely high There is a real desire to focus more on providing better customer experiences Practical Application Many are keen to find out what the agile evolution means for them and their teams specifically Key challenge: how will this work with external partners who do not work in an agile way? Pilot areas have been highlighted to start using agile within IAG Loyalty Things that Slow Us Down Silo’d working  Limited alignment and collaboration > duplication of work Decisions and approvals made hierarchically > slows us down Decisions made by committee/ no accountability > slow us down Feedback given too late > work wasted Legacy systems Lack of Clarity Unclear strategy/ vision that is not communicated Unclear who has the authority to make decisions Contradicting objectives between departments Uncertainty around who our customer is  These themes have informed the four pillars….

Outcome 1 Our way of working Our way of working is embedded in our culture. It shows up in how we do things and is a critical part of who we are. New hires and candidates understand what life is like at IAG Loyalty.  Confidential - People Team Update ‹#› Outcome 2 Clear prioritisation IAG Loyalty colleagues have a clear understanding of our strategic priorities and how they support the delivery of our strategy. Teams cross-collaborate to deliver the value. Outcome 3 Seamless workflow Work is flowing through IAG Loyalty transparently and efficiently.  We are able to respond swiftly to changes and can monitor our capacity to ensure we focus on the right priorities. Outcome 4 Skilled & engaged colleagues Our colleagues are engaged and have developed the capabilities they need to embed Agile into our culture and ways of working. “I know what it means to be part of IAG Loyalty and how things are done around here.” “I am clear on our priorities and why they are the right focuses – it helps me decide where to invest my time.” “We deliver work effectively, navigate obstacles and re-organise ourselves quickly to find solutions." “I have the skills I need to do my job and am clear on our progress.” By fully embracing and adopting Agile ways of working, we will power our growth and deliver greater value to our stakeholders, partners & customers.   Auditory Prospective Measures

What difference has it made? ‹#› Removed due to Confidentiality

REFLECTION WHAT? SO WHAT? NOW WHAT? ‹#› What did you find most valuable about this session? So what impact did this have on your application of clean interviewing in your context? Now what actions will you take to implement the skills and knowledge?

Summary Clean Language can be used in many settings not just Product Backlog Management come to tomorrow's session to learn more Clean Language will help you be less bias and increase the chance of building the right thing Clean Language can help to express the value of backlog items as well as making it clearer what you are building Whilst Clean Interviewing is simple to understand it is difficult to master and will take practise.

Questions? Connect for Slides ‹#› https://bit.ly/3WnqRJE Or j oin me online in September or October in the Wirral to learn more Discount code: Event10