a·gen·tic a·gil·i·ty

Adventures in Scrum: Lesson 1 – The failed Sprint

TL;DR; Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.

Published on
4 minute read
Image
https://nkdagility.com/resources/OG5mmVtH9nU
Subscribe

I recently had a conversation with a product owner that wanted to have the Scrum team broken up into smaller units so that less time was wasted on the Scrum Ceremonies! Their complaint was around the need in Scrum to have the entire “Team” (7+-2) involved in the sizing of the work during the “Sprint Planning Meeting”.

Update 16th March 2010


The standard flippant answer of all Scrum professionals, “Well that’s not Scrum”, does not get you any brownie points in these situations. The response could be “Well we are not doing Scrum then” which in turn leads to “We are doing Scrum…But, we have split the scrum team into units of 2/3 so that they can concentrate on a specific area of work”. While this may work, it is not Scrum and should not be called so… It is just a form of Agile. Don’t get me wrong at this stage, there is nothing wrong with Agile, just don’t call it Scrum.

The reason that the Product Owner wants to do this is that, in effect, through a number of miscommunications and failings in our implementation of Scrum, there was NO unit of potentially Shippable software at the end of the first sprint. It does not matter to them that most Scrum teams will fail the first Sprint, even those that are high performing teams. Remember it is the product owners their money!

We should NOT break up scrum teams into smaller units for the purpose of having less people tied up in the Scrum Ceremonies.

The amount of backlog the Team selects is solely up to the Team… Only the Team can assess what it can accomplish over the upcoming Sprint.
- Scrum Guide , Scrum.org

The entire team must accept the work and in order to understand what they can accept they must be free to size it as a team. This both encourages common understanding and increases visibility on why team members think a task is of a particular size. This has the benefit of increasing the knowledge of the entire team in the problem domain.

A new Team often first realizes that it will either sink or swim as a Team, not individually, in this meeting. The Team realizes that it must rely on itself. As it realizes this, it starts to self-organize to take on the characteristics and behaviour of a real Team.
- Scrum Guide , Scrum.org

This paragraph goes to the why of having the whole team at the meeting; The goal of Scrum it to produce a unit of potentially shippable software at the end of every Sprint. In order to achieve this we need high performing teams and this is what Scrum as a framework has been optimised to produce.

I think that our Product Owner is understandably upset over loosing two weeks work and is losing sight the end goal of Scrum in the failures of the moment. As the man spending the money, I completely understand his perspective and I think that we should not have started Scrum on an internal project, but selected a customer  that is open to the ideas and complications of Scrum.

So, what should we have NOT done on our first Scrum project:

“Your team may be dysfunctional … but at least you can see the impediments. Now you have the ability to do something about it!”
- Kane Mar Scrumology , Scrum Coach

I will be brining all of these things up at the Sprint Retrospective and we will learn from our mistakes and move on.

Do, Inspect then Adapt…


Need Help?

Professional Scrum Developer Training

Adventures in Scrum: Lesson 1 – The failed Sprint SSW has six Professional Scrum Developer Trainers who specialise in training your developers in implementing Scrum with Microsoft’s Visual Studio ALM tools.


Technorati Tags: Scrum   SSW

Smart Classifications

Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.

Subscribe

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Higher Education Statistics Agency Logo

Higher Education Statistics Agency

Slicedbread Logo

Slicedbread

Workday Logo

Workday

Jack Links Logo

Jack Links

MacDonald Humfrey (Automation) Ltd. Logo

MacDonald Humfrey (Automation) Ltd.

Lockheed Martin Logo

Lockheed Martin

Teleplan Logo

Teleplan

Ericson Logo

Ericson

Cognizant Microsoft Business Group (MBG) Logo

Cognizant Microsoft Business Group (MBG)

Emerson Process Management Logo

Emerson Process Management

Healthgrades Logo

Healthgrades

Milliman Logo

Milliman

Flowmaster (a Mentor Graphics Company) Logo

Flowmaster (a Mentor Graphics Company)

Deliotte Logo

Deliotte

ProgramUtvikling Logo

ProgramUtvikling

Graham & Brown Logo

Graham & Brown

Microsoft Logo

Microsoft

Department of Work and Pensions (UK) Logo

Department of Work and Pensions (UK)

Washington Department of Transport Logo

Washington Department of Transport

Nottingham County Council Logo

Nottingham County Council

Ghana Police Service Logo

Ghana Police Service

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

New Hampshire Supreme Court Logo

New Hampshire Supreme Court

Lean SA Logo

Lean SA

SuperControl Logo

SuperControl

Graham & Brown Logo

Graham & Brown

Genus Breeding Ltd Logo

Genus Breeding Ltd

Ericson Logo

Ericson

Sage Logo

Sage