Agile Resources

I came across Andy Bacon his blog that lists some interesting articles and resources, you can find it here: https://andybacon.com/agile-resources/

And just in case he ever decides to take his website offline, here is a quick mirror 😉

Some Agile Basics

Agile Related Certifications

Scaling Frameworks

Retrospectives

Daily Scrum

Scrum Graphics

Checklists

User Stories

Role of Managers in Agile

DiSC Assessment (free)

Games

Metrics

Estimation, Data Driven Estimates, and Forecasting

Collaboration Tools

Happiness

Podcasts

Product Owner Resources

  • Opportunity canvas
  • Lean canvas
  • Product vision
  • Product roadmap
  • Release plan

Random Helpful Things

Technical Topics

Story Point Estimates Are Best Thought of as Ranges

When estimating with story points, most teams use a predefined set of values that doesn’t include every possible number.

One of the questions I often get about story points is what to do if you can’t decide whether a particular product backlog item should be an 8 or a 13 (or a 3 and a 5). Part of the answer can be found by thinking about water buckets.

Suppose you have 10 liters of water you need to store. You also have an 8-liter bucket and a 13-liter bucket.

Which bucket would you store the water in?

The 13-liter bucket, right? Ten liters of water doesn’t fit in an 8-liter bucket. The water would overflow and spill out.

Extrapolating further, you’d use the 13-liter bucket for all amounts of water from 9 liters through 13 liters. Once you hit 14 liters, though, you’d once again need a bigger bucket.

And so it is with the values you choose to use when estimating stories. Think of each value as a bucket. A value bucket is used for all stories between that value and the next lower value.

Read the complet blogpost here: https://www.mountaingoatsoftware.com/blog/story-point-estimates-are-best-thought-of-as-ranges

How to Work with Complex User Stories That Cannot Be Split

Most user stories can be split. It may be hard to find a good way to split some stories, but most can be split. These are known as compound stories—stories that are made up of multiple smaller stories.

There is another type of story: the complex story. Complex stories are ones that cannot be split. They are inherently large or complex and there are no subparts to be pulled into separate stories.

Even with a complex story, you don’t want to let the story linger open for three, four or more sprints. Doing so

  • Makes velocity less predictable from sprint to sprint
  • Increases the risk of a developer going astray from user expectations , and
  • Allows the team to develop the bad habit of leaving work incomplete at the end of an iteration

Use Progress Points to Identify Accomplishments

Read about it in this article: https://www.mountaingoatsoftware.com/blog/how-to-work-with-complex-user-stories-that-cannot-be-split

How to Deal with Bad Scrum User Stories as a ScrumMaster

It is common in the early stages of Scrum implementation for there to be misunderstandings about what User Stories are for and what makes them useful. A ScrumMaster’s task is to be able to help the Team and Product Owner when they are faced with ineffective User Stories as they go into Sprint Planning.

Read the complete article here: https://agilepainrelief.com/notesfromatooluser/2019/01/deal-with-bad-scrum-user-stories-as-a-scrummaster.html

User Story / Task templates

USER STORY:

WHO:
Requester

  • Add Requester here

WHAT:
Functional Requirements:

  • Add Functional Requirements here
  • Functional Impact Analysis on whole chain (this team is accountable that the impact analysis is done, but we can ask the requester to perform the impact analysis, if that is appropriate)

WHY:

Background and Introduction:

  • Add background and introductory information here

HOW:
External Dependencies:

  • What are the external dependencies that need to be addressed?

Test Strategy:

  • List Test Goals
  • Approach per Test Goal per Test Level (Sprint Test, iST, etc)
  • Which team has to do what

Test Data Availability:

  • Is the test data already available to test this user story? If not, who will be responsible for providing the test data? By when will the test data be available?

Solution Outline:

  • A brief outline of what should be the solution

Dependencies With Other User Stories:

  • Is this user story dependent on any other story?

Dependencies Within CCC:

  • What are the dependencies within the Capital & Control Chain with regards to this story?

NFRs:

  • Any non functional requirements that need to be addressed?

TASK:

Background and Introduction:

  • Add background and introductory information here

Functional Requirements:

  • Add Functional Requirements here

External Dependencies:

  • What are the external dependencies that need to be addressed?

Test Data Availability:

  • Is the test data already available to test this user story? If not, who will be responsible for providing the test data? By when will the test data be available?

Solution Outline:

  • A brief outline of what should be the solution

Dependencies With Other User Stories:

  • Is this user story dependent on any other story?

Dependencies Within CCC:

  • What are the dependencies within the Capital & Control Chain with regards to this story?

NFRs:

  • Any non functional requirements that need to be addressed?