Shades of Scrum

January 4, 2013 at 8:23 pm Leave a comment


Is Scrum a process? According to the Oxford dictionary a process is “a series of actions or steps taken in order to achieve a particular end”.

Is Scrum a method? According to the Oxford dictionary a method is “a particular form of procedure for accomplishing or approaching something, especially a systematic or established one”.

Is Scrum a methodology? According to the Oxford dictionary a methodology is “a system of methods used in a particular area of study or activity”.

, method or methodology. Remember that Scrum doesn’t say a word about how to estimate, how to do the software architecture, unit testing etc.

Scrum is a framework. The Oxford dictionary defines a framework as “a basic structure underlying a system, concept, or text”.

This means that every team builds it own p Scrum is none of these. Scrum is just to unspecific to be a process rocess / method / methodology using the Scrum framework as the basic underlying structure.

And that means that there is no best practice for a staffing the Product Owner, for the behavior of the ScrumMaster or the Sprint length.

In the “Shades of Scrum” blogpost series I explain possible implementations of parts of the Scrum framework with the underlying forces that may make one choice more suitable in a specific situation than another choice:

  • The ScrumMaster role: The article explains how the ScrumMaster role may change over time according to the ever growing capabilities of the team.
  • 3 Product Owners and a Product Owner Shaped Object: The article describes 4 implementations of the Product Owner role and argues that one of the more common implementations isn’t a valid Scrum Product Owner.
  • Sprint length: The article compares shorter and longer Sprint lengths and shows that longer Sprint lengths have their value – not only for beginners.
  • Waterfall, Pipelining and Sprints: Most companies aren’t capable of doing perfect Scrum from day 1. They need to transition from Waterfall to Scrum, maybe with Pipelining as an intermediate step. The article shows pros and cons of the Waterfall, Pipelining and Scrum Sprints and helps to define an appropriate process for the specific whole value stream.
  • The Sprint Planning and the pull principle: The team pulls work into the Sprint during the Sprint Planning. The article discusses different types of pull.
  • Estimation of the Product Backlog: The article presents different approaches to estimation and discusses when to use which approach.
  • Empirical Management Meetings: The article highlights that fact that most Scrum meetings are empirical management meetings and therefore there should be transparency, inspection and adaptation in the meetings. The article gives guidelines on how to optimize these meetings for your context.
  • Scrum outside IT: Scrum is used mainly for software development today but starts to spread out to other areas. The blogpost shows concrete example of Scrum outside IT and presents an approach to handle projects outside IT with Scrum.

Entry filed under: it-agile-blog-planet. Tags: .

Shades of Scrum: Waterfall, Pipelining and Sprints Shades of Scrum: Estimation of the Product Backlog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed



%d bloggers like this: