A User Story is the most widely used Agile Practice for capturing needs and requirements and describing Product Backlog Items. To get the most of any technique it is good to understand the why behind it not just the what. Let’s discuss how to write better User Stories in Scrum.

Just to set the scene, I haven’t figured this out yet. I can tell you my story, in all its ugliness. It’s based on a real story, but it’s changed significantly from reality to protect the innocent. I hope you still find my account useful.

Imagine a project with hundreds of people, a lead time in months, few releases a year. You could compare these as large cruise boats or tankers navigating for few weeks in the immensity and emptiness of the oceans and seas and then stopping to ports very far away from each other.

As promised, here is part two of the three-part blog series, inspired by the writings of John C. Maxwell, “The 15 Invaluable Laws of Growth: Live Them and Reach Your Potential.”

Hi Duncan, I took your Scrum Training class a couple of months back. You mentioned if we had any questions, we could email you and I have an interesting situation I found myself in regarding QA’s in our Scrum teams.

I often wonder about the Trustpilot reviews straight after a workshop. Did I entertain? Did I perform? Were attendees satisfied? Are attendees inspired? It matters. I just think it matters more if the workshop made a difference to the work lives of attendees. I can't take credit. The client does the hard yards.

When working with a flow-based Kanban system there are a few statements that I would suggest most teams should bear in mind.

Hello awesome people. Back at it again with new learning from the trenches. Over the years working with Product Owners who mainly work in large corporations, I see common challenges.

During this Liberating Structures strategy for Scrum meetup we addressed dealing with uncertainty — a particularly useful skill in highly competitive markets. Learn more about how to train and grow the resilience of your team when dealing with the unexpected.

Food for Agile Thought’s issue #214 delves into Scrum agility; we follow a notion for time-based estimates, and we learn more about similarities and differences between Cynefin and the Stacey matrix.

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions.

In organizations in which agile transitions take place, the ancient English proverb Blood is thicker than water is frequently appropriate. It is decided to adopt agile working, there is talk of Scrum, self-organizing teams, Sprints, standing meetings, sticky notes on the wall, etc. etc.

It's been a while since I wrote a blog, here is some good news, this is part 1 of a 3 part blog series, inspired by the writings of John C. Maxwell, “The 15 Invaluable Laws of Growth: Live Them and Reach Your Potential.”

While teaching and consulting, I’ve had many existing Scrum Masters pull me aside looking tired, frustrated, and worn out.

In my Professional Scrum classes, I always get asked about best practices.  It may be about facilitating events, Product Backlog refinement, defining value, forming Scrum Teams, or creating good Sprint Goals.

People always have questions and concerns about Risk management and Autonomy in the Scrum Team...

Hello awesome people. It's me again with a new learning from within a Scrum Team. The Development Team I was working with around 3 months ago challenged the Product Owner about the User Story she brought into the Sprint Planning.

Your Sprint is over. Your increment is “Done”, you have coded cleanly, your unit tests and integration tests are bright green, you are proud of your work. The Sprint Review is running smoothly. The Sprint Retrospective allows the team to find 1 or 2 areas of improvement without revolutionizing the world.

Teams often run through the motions of Scrum and get very hung up on story points, velocity, committed percentages and as a result struggle to deliver value. But what I’ll share today is what unlocks the value of Scrum;

End of September we went to Stockholm with 15 agile leaders. We wanted to visit several companies in and around Stockholm to see how they created a thriving environment for agile teams.

A few years ago, I was part of a team that was starting to work together under very difficult circumstances: We had to finish a showcase in the Industry 4.0 area within just six weeks.

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.

I'd like to share another story with you... Thank you Paul and Charlie for sharing your story. It moved me and left me with huge smile on my face. 

A few weeks ago we considered the Agile Manifesto from a lean perspective. We saw that it is possible to map the 12 agile principles to the 7 canonical “Lean Wastes” in terms of a mitigation approach.

Hello awesome people. I want to share with you my recent experience and discussion with a senior manager who needs advice on how to measure his organisation agility.

There are four key words in the first value of the Agile Manifesto: “Individuals and their interactions over processes and tools”

Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity.

In the world of tech, many industry giants such as Google choose to use a management framework known as Objectives and Key Results (OKR).

The legendary Steve Trapps has been talking to me for months about featuring in an interview. So here we are, I finally agreed and we spent 25 minutes talking about me; obviously mainly avoiding being narcissistic.

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions.

Warning - this post is not about Scrum. It is about Technical Debt in my home!!! Please do not judge me!!

If you want your organization to become agile, adding more whiteboards to the workspace will not suffice. You have to abandon the idea that the workspace is an assembly line for white-collar workers. You need to let go Taylorism. We are now in the age of the creative worker.

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.

Does your firm exceed your customer's expectations regularly? Is just meeting expectations good enough in your market? Businesses pursuing an improved ability to deliver customer value using Scrum face numerous challenges.

Sprint Goals are one of the more elusive parts of the Scrum Framework. Most teams know they are important, but few use them - for a variety of reasons. In this post, Barry Overeem and I bust the myth that Sprint Goals are optional in Scrum. And we make an effort to show what makes them so vital in the face of complex work. And more importantly, what you can do to start working with Sprint Goals from now on.

The Kanban Guide for Scrum Teams aims to help Scrum Teams leverage the ideas and practices of Flow and Kanban in a way that is coherent with Scrum as defined by the Scrum Guide.

Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. Much to the surprise of many readers, the direct Scrum Master engagement with a single Scrum Team of average size and a typical 2-week Sprint turned out to be about 12 hours per week.

I have my own biases,  having seen co-located teams work very well and having struggled with “dislocated” teams, I often recommend my clients to reconsider “dislocated” teams. 

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.

Product Owners have a tough job. I was in a Sprint Review recently where the Scrum Team had some stakeholders talking about an idea they thought was excellent. So, like any studious Product Owner, they immediately typed up the idea and added it to their Product Backlog.

At a recent training class one of the delegates spoke about their present company, about how it was the most “Agile” place he had ever worked.

I share my thoughts in this video about the practices and activities the Scrum Master should be doing to increase his/her awesomeness. Hopefully it will help you to find the gap towards awesomeness.

Every year I like to deliberately go somewhere far from the crowd to take a break and reflect. You can say that it's similar to a retrospectives. Often times I may not realised whether as a Scrum Master my service to the organisation is already effective or not.

A customer I was working with asked me to help out with the intake process for recruiting a new Scrum Master and a new Product Owner. I asked them what they had so far. They provided a clear job description describing what they wanted to see from the candidates.

Software developers are mostly guys, happy to work by themselves at night in dark rooms. And they turn coffee, cola and pizza into code. Right?

Defining Agile/Scrum for Marketing Scrum.org joined the discussion around Agile Marketing recently. This is an area close to my heart.

TL;DR: Scrum Master Duties, Serving a Single Team Scrum Master Duties: supposedly, a great Scrum Master serves only one Scrum Team—that’s at least a popular narrative in the Scrum community.

The Liberating Structure "Wicked Questions" makes paradoxical realities transparent. By doing so, you can engage in deeper strategic thinking and explore new possibilities.

Why is it that when the going gets tough, “agile” gets the blame? There is so much online bashing of [insert random agile framework or method] going on, that it made me wonder if there is a pattern behind it. I believe there is.

This blog gives a Lean perspective on the Agile Manifesto.