Please try all of Scrum.

Scrum is a bare framework. It is very simple.

Scrum is not trying to be a full methodology.

Lots of people are doing Scrum-Butt.  “We do Scrum, but…”  And then they say…

…we don’t have a product owner.
…we change the length of the sprint often
…we don’t have a Scrum Master
…we don’t do a _daily_ scrum
etc.

I strongly urge you to try all of Scrum.  No Scrum-Butt.

Because I think more success will result. For you, for your team, and for your customers.

A simple definition of the bare framework can be found in the Scrum Guide or in this list.

If, because of impediments, you are doing Scrum-Butt now, this is ok.  Let me just ask two things. Try to fix the impediments.  And tell yourselves and tell others….”well, we are trying to do all of the bare framework of Scrum, but so far we are doing Scrum-Butt…”

Thanks. And I think that will help you and others.

Joe’s Agile Release Planning – New Version

I have posted a new version of the booklet.  Here:

http://agileconsortium.pbworks.com/w/page/57940361/Joe%27s%20Release%20Planning

It is free.  Hope you find it useful.

I hope you will leave comments or send me comments.

Summarizing Scrum (a list)

The more I think about Scrum, the more it becomes a Gestalt…a whole thing.  And it becomes somewhat misleading to talk about its parts.

One must do all of Scrum.  It you only take part of the medicine…well, you will not get the real benefit.

Still, we must talk about Scrum one word at a time. And, for reference and other purposes, we can simplify this into a lost.  A list as a basis for discussion.  One hopes these discussions lead to a better life for you, your Team and your customers.

Scrum was ‘co-created’ by Jeff Sutherland and Ken Schwaber.  Their definition of it, the core definition anyway, is in the Scrum Guide.

I have produced several versions of a two-page list of things that define Scrum. The link goes to my latest version (V5).

This list is based mainly in the Scrum Guide, and also discussions with Jeff Sutherland and much reading and experiences.

The first thing to note is how simple the basic framework of Scrum is.

Secondly, you will note my bias, which is that the ideas behind Scrum are at least as important as the explicit Roles, Meetings and Artifacts of Scrum.

The items in brackets [ ] are things that are not in the Scrum Guide. I believe all of  them are ‘supported’ by Jeff Sutherland if not others.  So I do not feel I am adding unfairly to Scrum. But they are not all required to be doing ‘the bare framework of Scrum’.