What Scrum Is, What It Isn't

Table of Contents

Format: Lecture
Duration: 60 minutes

Abstract

This presentation looks at what Scrum really is, and what it isn't. This distinction is important because many people mistakenly feel forced to use certain practices even when they really wouldn't suite them. Or maybe they object to Planning Poker, thinking it is a silly game (it isn't, but that's beside the point), and therefore object to Scrum, even if those two aren't the same. From adaption point-of-view, there is very little in Scrum itself that can be changed (or should be changed), but the various "non-Scrum" (but Agile) practices are the adaption point teams and organizations should look at in their Agility.

Detailed description

See What Scrum Is What It Is Not - Heiramo.ppt. I held this presentation in Turku Agile Day on March 19th 2009 in about 45 minutes. I plan to expand it a little with detail in the practices section for a 60 min presentation.

Biography

Petri Heiramo has been focusing strongly on Scrum and Agility since 2005. He has been working at Digia since 2000, and has gained a lot of experience in different kinds of projects both in Agile and traditional way. For the last 5 years he has been responsible for the improvement of the software development processes in the company. Petri was the first Finn to be approved as Certified Scrum Trainer by Scrum Alliance in late 2008.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Jul 30, 2009

    Vasco Duarte says:

    How will this presentation help the participants improve their understanding of ...

    How will this presentation help the participants improve their understanding of Scrum. Will you mention some "paradigms" (i.e. stuff that is critical) of Scrum that people should be aware of? Will you make a distinction between what Scrum "really needs" and what is part of Scrum but not "critical"?

    Will I, after attending this session, be able to go into a team and assess if they are doing the "critical bits" of Scrum? Perhaps with a checklist/assessment tool?

    Will you give people an overview of what a Retrospective agenda could be if you were trying to raise awareness about "are we really doing scrum" in a team?