Posted in My Scrum Notes, Scrum Roles

New Scrum Master Role Considerations

Learnings from Previous Scrum Master 

To the team

  • What responsibilities did the Scrum Master assume for the team?
  • What was the SM role in Scrum events?
  • How did the SM mentor/ coach/ teach?
  • Are there any recent improvements/ teachings that the SM has been implementing?

To the organisation 

  • What was the SM relationship like with the wider organisation?
  • What were the improvements the SM was heading up across the business? What were the recent successes/ failures?

In a scaled Scrum environment

  • What is the SM relationship with other SMs and teams?
  • Are there any further assumed responsibilities towards other teams?

Relationship with Your Manager

Five Conversations (1, page 93-4)

  1. The situational diagnosis conversation
    1. How did the organisation reach this point?
    2. What factors make this situation a challenge?
    3. What resources within the organisation can you draw on?
  2. The expectations conversation
    1. What does your new boss need you to do in the short term and in the medium term?
    2. What will contitute success?
    3. How will your performance be measured?
  3. The resource conversation 
    1. What do you need to be successful?
    2. What do you need your boss to do?
    3. Not just people/ equipment, but support for change in the organisation
  4. The style conversation 
    1. How you and your new boss can best interact on an ongoing basiss
    2. Medium and how often 
  5. The personal development conversation (a few months into your new role)
    1. How you are doing and what your development priorities should be

What to focus on

Early wins evaluation tool (1, page 129)

Use the resulting score from the below table to compare candidates for early wins.

 Not at allTo a small extentSomewhatTo a significant extentTo a great extent
Does the focal point offer an opportunity to make a substantial improvement in the performance of your unit?01234
Is this improvement achievable in a reasonably short time with available resources?01234
Would success also help lay the foundation for achieving agreed-to-business goals?01234
Will the process used to achieve the win help you make needed changes in behaviour in the organisation?01234


FOGLAMP Project Checklist (1, page 131)

Tool to help you cut through the haze and plan your critical projects

  • FOCUS: What is the focus for this project?
  • OVERSIGHT: How will you oversee this project? Who else should participate to help you get buy-in for implementing results?
  • GOALS: What are the goals and intermediate milestones and time frames for achieving them?
  • LEADERSHIP: What will lead the project? What training, if any, do they need to be successful?
  • ABILITIES: What mix of skills and representation needs to be included? Who needs to be included because of their skills? 
  • MEANS: What additional resources, such a facilitation, does the team need to be successful?
  • PROCESS: Are there change models or structured processes you want the team to use? How will they become familiar with this approach?

Decision Making

Team decision making (1, page 193)

  • If the decision is likely to be highly devisive (creating winners and losers) you need to take the heat
  • If your team are inexperienced as build consensus is unlikely to work and you risk imposing a decision anyway 
  • If you need to establish your authority (do not use once you are established)
Build consensus
  • If the decision requires energetic support for implementation from people whose performance you cannot adequately observe and control

Framing arguments (1, page 214 – 5)

Framing means carefully crafting your persuasive arguments on a person-by-person basis

Logos – data and reasoned argumentsWhat data or analysis might they find persuasive?What logic(s) might appeal to them?Are there biases to which they are falling prey and, if so, how might you demonstrate this?
Ethos – principles, policies, and other ‘rules’Are tehre principles or policies that they could be convinced should operate here?If you are asking them to act counter to a princple or policy, can you help them justify making an exception?
Pathos – emotions and meaningAre there emotional ‘triggers’ for example loyalty or contribution to the common good, to which you could appeal?Can you help them create a sense of meaning by supporting or opposing a cause?If they are reacting too emotionally, can you help them step back and get perspective?


Guidelines for Structures Self-reflection (1, page 223)

On a scale of high to low, do you feel:
  • Excited? If not, why not? What can you do about it?
  • Confident? If not, why not? What can you do about it?
  • In control of your success? If not, why now? What can you do about it?
What has bothered you so far?
  • With whom have you failed to connect? Why?
  • Of the meetings you’ve attended, which has been the most troubling? Why?
  • Of all that you’ve seen or heard, what has disturbed you most? Why?
What has gone well or poorly?
  • Which interactions would you handle differently if you could? Which exceeded your expectations? Why?
  • Which of your decisions have turned out particularly well? Not so well? Why?
  • What missed opportunities do you regret the most? Was a better result blocked primarily by you, or by something beyond your control?

Potentially Dysfunctional Behaviours

Action imperative (1, page 48)
  • when you feel too anxious or too busy to devote time to learning, and feel pressure to ‘do’ 
  • Leads to a death spiral 
  • Don’t learn – make a poor decision and undermine your credibility – alienate people – they don’t share info with you – start the loop again  
Undefended boundaries (1, page 224)
  • Fail to establish what you are willing and not willing to do. People will take whatever you have to give
  • The more you give, the less they will respect you and the more they will ask of you – another vicious cycle
  • If you cannot establish boundaries for yourself, you cannot expect others to do it for you
Brittleness (1, page 224)
  • Rigidity and defensiveness, resulting in overcommiting to failing courses of action
  • Finding it hard to admit you were wrong
Isolation (1, page 224)
  • Not taking time to make the right connections, perhaps overrelying on a few people or on official information
Work avoidance (1, page 224)
  • Choosing to delay work/ decisions by burying yourself in other work or fool yourself into believing that the time isn’t ripe to make the call
  • Avoiding taking the bull by the horns, resulting in the tough problems becoming even tougher
Yerkes-Dodson Law (1, page 227). Image from Wikipedia


  1. The First 90 days by Michael D. Watkins

Explore more

New Organisation Considerations

Agile Games
Posted in My Scrum Notes, Scrum

Scrum Considerations

Delivery of Value

Delivery Logistics

  • How frequent is delivery to the customer?
  • Is there an approval process to get to live
  • How are live releases conducted? Test customers? Downtime?

Sprint Outcome

  • Do the team deliver the sprint goal?
  • Is an increment delivered? (i.e. a ‘done’ potentially releasable step towards the product goal)

Value Focus

  • Does the team deliver what the business most needs?
  • How is ‘most valuable’ decided?
  • How are deliveries verified as achieving value?

Supporting Process Improvements

  • How are the Scrum team continuously improving?
  • Read through recent retrospective notes (if they exist) 
  • What challenges have they recently faced/ overcome?
  • Have there been changes across the organisation?

Previous performance (2)

  • How has this organisation performed in the past? How do people in the organisation think it has performed? 
  • If performance has been good, why has that been the case? 
  • What have been the relative contributions of strategy, structure, systems, talent bases, culture, and politics? 
  • If performance has been poor, why has that been the case? Do the primary issues reside in the organisation’s strategy? Its structure? Its technical capabilities? Its culture? Its politics? 

Scrum Events

Daily Scrum 

  • Does it happen every day at the same time and place?
  • Does the whole team participate? Are there any external people that participate/ observe?
  • Are problems/ impediments surfaced?
  • How are impediments left at the end of the event?
  • Is the Sprint Goal used as an anchor for the conversation?
  • Does someone facilitate the event or keep an eye on the team working agreements?

Sprint Planning

  • Does the PO participate? How do they communicate what is priority?
  • Do all the developers attend and participate?
  • Does it result in a Sprint Backlog and Sprint Goal?
  • Does the whole team believe the plan is achievable?
  • Are any forecasting metrics used, e.g. velocity from story points?

Sprint Review

  • Does this happen after every sprint?
  • (For scaling) Is the Sprint Review for the team only, or is it combined with other teams?
  • Are the right stakeholders in the room? Are there observers who don’t feedback or questions left for those outside the room?
  • Is feedback given and adaptations discussed?
  • What is the format? Is it a working session or a presentation?
  • Are challenges or adaptations during the sprint discussed? Is this done with transparency and safety?
  • Is this event used as a sign off for releases?
  • Is there an inspection of the Product Backlog?
  • Is the Definition of Done used to inspect the increment?
  • Is the increment ‘done’?

Sprint Retrospective

  • Does it result in concrete improvement proposals?
  • Do some proposals get implemented?
  • Does the whole team and the PO participate? Are there other observers either in the meeting or expecting notes afterwards?
  • Is there a nominated facilitator or note taker?
  • Is there an elephant in the room?
  • What are the current improvements/ impediments?
  • Are the team free to experiment? Is innovation celebrated?
  • How do they manage failure?


  • How long is a Sprint?
  • (For scaling) Does sprint start/ end times correlate with other teams? Are they in sync or staggered? 
  • Is Sprint length consistent? How are public holidays handled?
  • Are sprints cancelled? Why and by whom?


Sprint Backlog

  • Where is it? Is it highly visible?
  • Who looks at it?
  • Do the team actually use it, or is it a burden to them?
  • Do external stakeholders use it?
  • Do the team own it?

Product Backlog

  • Where is it? Is it highly visible?
  • Are the PBIs prioritised? How are they prioritised and by whom? Is there a process?
  • Are estimates used?
  • How is the Product Backlog used for forecasting?
  • How are the estimates done?
  • How are the PBIs refined? Who refines them? Are there any team standards as to what refined means?
  • Does the PO understand all of the PBIs and is able to prioritise? Is the backlog bloated with junk?

Definition Done

  • Does one exist?
  • Who wrote it/ owns it?
  • (Scaling) Are there shared standards/ definitions?
  • Does it evolve?


  1. Henrik Kniberg’s checklist
  2. The First 90 days by Michael D. Watkins

Explore more


Agile Games
Posted in My Scrum Notes, Scrum Roles

Consideration for a New Product Owner

Product Owner Role Overview

  • MUST – One person (2)
  • What happens when the Product Owner is not available or out of office?

Product Goal

  • How does the Product Owner develop the Product Goal?
  • How does the Product Owner communicate the Product Goal?
  • How does the Product Owner align the Product Goal with the business strategy (and other teams)?

Product Backlog Management

Product Backlog Ordering

  • Does the Product Owner have the knowledge to be able to order the backlog?
  • On what basis does the Product Owner order the Product Backlog?
  • How often does the order of the Product Backlog change? Why?


  • What does the Product Owner use to store the Product Backlog?
  • Is the Product Backlog visible?
  • Are there any personal tools the Product Owner uses in addition to the visible Product Backlog?

Product Backlog Items

  • Who constructs the Product Backlog Items?
  • How are Product Backlog Items communicated?
  • Check Product Backlog Items against positive and smells
  • Does the Product Owner understand all of the Product Backlog Items?


  • How does the Product Owner use the Product Backlog to forecast releases and deliveries?
  • How does the Product Owner communicate these forecasts?
  • How does the Product Owner handle changes to the forecasts?

Stakeholder Communication

  • Who are the Product Owner’s internal stakeholders?
  • What are the expectations in communication between the Product Owner and his/her/their stakeholders?
  • Does the Product Owner have direct contact with the customers?


  • Is the Product Owner’s decision respected with regards to order of the Product Backlog?
  • Is the Product Owner’s decision respected with regards to the forming of the Product Goal?
  • Is the Product Owner’s decision respected with regards to releasing functionality live?

Relationship with the Developers

  • How available is the Product Owner to the developers?
  • How do the developers and the Product Owner communicate?
  • Is there mutual respect between the respective responsibilities?


  1. Henrik Kniberg’s checklist
  2. The Scrum Guide

Explore more

User Stories

Posted in My Scrum Notes, Scrum Roles

First Conversation with the Scrum Team

This interview structure is adapted from the sample questions from The First 90 Days, page 176 (1).


  • Meet with each direct report in turn and ask the following questions  
  • By asking the same questions of everyone you can see where similarities and differences lie, which will help you understand what kind of team player each person is a little more. 
  • Once you have gone through all the data of the interviews, gather the whole team together and discuss what you have found out through the interviews and have an open discussion.


  • What are the strengths and weaknesses of our existing use of Scrum and complementary practices?
  • What are the biggest challenges and opportunities facing us in the short term? In the medium term?
    • In terms of our Product and providing our customers with value
    • In terms of our Scrum team’s processes and ways of working
  • What resources could we leverage more effectively?
    • In terms of our processes
    • In terms of our tools
    • In terms of individuals in our team
    • In terms of our interactions inside and outside the team
  • How could we improve the way the team works together?
  • If you were in my position, what would your priorities be?

Optional Follow-up Questions


  • How do you think the skills and responsibilities are balanced in the team? 
  • If there is a mistake/ failure within the team, is it openly discussed in team events? What about with external stakeholders?
  • Is there anyone inside the team or externally who has a big influence on the way we work or what/how we develop, and why? 

Land mines 

  • What was the most recent surprises that detonated and put us off track?
    • What is the most common? 
  • What potentially damaging cultural or political missteps must you avoid? 


  • Are there any Scrum or complementary practices that you know about that you think would benefit us as a team?
  • What are the most recent improvements that were made to our practices?
    • Who lead the change?
    • Do you think it was successful/ worthwhile?
    • Was there any opposition to the change?
  • What current parts of our process frustrates you the most?


  1. The First 90 days by Michael D. Watkins

Explore more

Posted in My Scrum Notes, Scrum Roles

Considerations for a New Team

Scrum Roles

  • MUST – One Product Owner
  • MUST – One Scrum Master
  • MUST – Developers

Scrum Team Size and Structure

  • MUST – No sub-teams
  • MUST – No hierarchies
  • SUGGESTED – ‘Typically fewer than 10 people’ (3)
  • Are the team members remote or co-located?
  • Are all the team members committed to the team?
  • Are there any unspoken hierarchies, e.g. an assumed leader?


  • MUST – The team has all the skills necessary to create value each Sprint (3)
  • Are the skills siloed into specialisms, or are the team members multi-skilled (or T-shaped)?

Evaluating Group’s Skill Bases (2, page 162)

Four types of knowledge
  • Individual expertise: gained through training, education, and experience
  • Relational knowledge: An understanding of how to work together to integrate individual knowledge to achieve specified goals
  • Embedded knowledge: The core technologies on which your group’s performance depends, such as customer databases or R&D technologies
  • Metaknowledge: The awareness of where to go to get critical information


  • Do they decide what is developed?
  • Do they decide who does the development?
  • Do they decide how to build an increment?
  • What are they responsible for in terms of product development?
  • Are they held accountable for creating an increment?

Team Working Agreements


  • How do they like to communicate day to day?
  • Do they have any information radiators to aid their communication?
  • What are the understood response times for communications internally and externally?

Team Culture

  • Do they socialise away from work?
  • What is the energy of the team?
  • Is there overtime? Is it acceptable/ expected?

Evaluating Individuals (2, page 171)

Consider these six criteria

  • Competence: Does this person have the techincal competence and experience to do the job effectively?
  • Judgment: Does this person exercise good judgment, especially under pressure or when faced with making sacrifices for the greater good?
  • Energy: Does this team member bring the right kind of energy to the job, or is she burned out or disengaged?
  • Focus: Is this person capable of setting priorities and sticking to them, or prone to riding off in all directions?
  • Relationships: Does this individual get along with others on the team and support collective decision making, or is he difficult to work with?
  • Trust: Can you trust this person to keep her word and follow through on commitments?

Team Smells

Problematic behaviour patterns (2, page 120)

Lack of…Symptoms
FocusThe group can’t clearly define its priorities, or has too many.
Resources are spread too thin, leading to frequent crises and firefighting.
People are rewarded for their ability to put out fires, not for devising enduring solutions.
DisciplinePeople exhibit great variation in their levels of performance.
Employees don’t understand the negative consequences of inconsistency.
People make excuses when they fail to make commitments.
InnovationThe group uses internal benchmarks to measure performance.
Improvements in products and processes unfold slowly and incrementally.
Employees are rewarded for maintaining stable performance, not for pushing the envelope.
TeamworkTeam members compete with one another and protect turf rather than work together to achieve collective goals.
People are rewarded for creating fiefdoms.
Sense of urgencyTeams members ignore the needs of external and internal customers.
Complacency reigns, revealed in beliefs such as ‘We’re the best and always have been’ and ‘It doesn’t matter if we respond immediately’


  1. Henrik Kniberg’s checklist
  2. The First 90 days by Michael D. Watkins
  3. The Scrum Guide

Explore more

Posted in My Scrum Notes

Persona Creating Workshop


  • To all have a shared understanding of the user roles that we are building the product for
  • To be able to use the roles when writing our BDD, stories, and to use when breaking down the stories in the story mapping workshops

Resources Needed

  • Post-it notes
  • Pens

Workshop Structure

Brainstorm an initial set of user roles

  • Everyone (the full team) writing role names on cards all together to brainstorm
  • A user role is one user. A company as a whole cannot use the software, so stick to one person
  • When the card is placed on the table or wall, the person reads out the name of the role and nothing more at this stage
  • Timebox to 15 minutes. End when the room stalls and people have stopped writing

Organise the initial set

  • Overlap cards where the roles overlap. The bigger the overlap of the cards, the bigger the overlap of the roles.

Consolidate roles

  • Authors of overlapping cards describe exactly what they meant
  • Group decides if roles are equivalent and rips up one (or both and creates a new one)
  • Rip up any cards that are not important to the success of the product (e.g. someone just browsing and never purchasing)
  • Can then create an overhead role to categorise some of the roles (like all job seekers, all recruiters etc)

Refine the roles

Add role attributes to each role. This is something that distinguishes one role from another e.g.

  • Frequency of using the software
  • User’s level of expertise with the domain
  • User’s general level of proficiency with computers
  • General user’s goal for the software – convenience/ rich experience
  • Type of outcome wanted from the product (e.g. part time or full-time role)


Make sure to have very strict time boxes for the team to complete the tasks in as it will be very easy to stray off topic and argue about the fine details which are not important

Explore more

User Interviews

User Testing
Posted in My Scrum Notes

User Story Mapping Workshop

“Story mapping keeps us focused on users and their experience, and the result if a better conversation, and ultimately a better product.” (1)

Exercise Walkthrough

Use the example of a morning routine for training for the people in the workshop

Start with talking about the Opportunity

Frame your idea

  • Why?
  • What are the benefits?

Put the opportunity into context

Talk about users and how this impacts them

  • Use personas

Build a narrative flow

Talk through the journey that each user will take to realise their benefit

  • Mile wide, inch deep
  • Tell a story
  • If there is a disagreement over the order, go with the most popular as it likely will not matter
  • Add in more steps for a good vs bad journey

Brainstorm Stories

All attendees brainstorm stories and stick them underneath each of the narrative flow steps that they apply to

  • Explore details and options
  • Specific things the user will do
  • Alternate things the user could do
  • Include risk stories
  • What would make it cool?
  • Play the ‘What about?’ game
    • E.g. What about when things go wrong?

Organise the Stories

Collate similar stories and talk high level about each of the stories so all in the room have a shared understanding.

  • Move all the stories down the wall to leave a gap at the top as you talk through them
  • Draw a line across the board (blue line on above picture) below the gap that has been left

Outcome #1 Focus

Discuss and decide what Outcome #1 can be

  • Top outcome is sea level
  • For maximum learning
  • Opening game

Outcome #1 Populate

Work together to decide which stories are part of Outcome 1

  • Move only the stories up above the line that are necessary for Outcome 1
  • Not all the steps from the narrative flow must be present in the Outcome
  • Move the stories from below Outcome 1 down to make a gap


Repeat steps 6 – 9 with the next Outcome until you have:

  • Middle outcome is the fish
  • Business rules
  • Wider user journey
  • Performance


  1. User Story Mapping by Jeff Patton

Explore more

User Stories