Skip to main content

How to Start Doing Scrum

I got interested in Scrum when I heard about it at MySQL. They had something called a Daily Scrum, in which all the developers participated. Not working in development, I wasn't part of that process, but a year later, I was wandering through Barnes & Noble at Crossroads Mall, and there was Ken Schwaber's Book "Agile Project Management with Scrum".

My previous contacts with project management convinced me that project management was about estimating and counting beans, producing lots of documentation, and other very useful tasks. Maybe something a bank or other large enterprise would want to do, but somehow very removed from the actual process of producing software.

Ken's book spoke to me, so I bought it. It was a revelation! Finally a book on project management that actually provided useful information about how to plan, estimate and organize a project. A book that talked about people, what they should be doing, and how they should organize themselves.

So if you want to start doing Scrum, start with Ken's book and do exactly what he says.

Comments

jp said…
Hi Peter,

you mentioned the book of Ken Schwaber, really a great one ...

The ISBN of this book is 0-7356-1993-X.
I would recommend reading this book before implementing SCRUM. Alternatively there is great video of Ken Schwaber at Google TechTalk at youtube.com:

http://youtube.com/watch?v=IyNPeTn8fpo

Cheers, jp
Peter said…
Absolutely! I can also recommend the books from Mike Cohn. I am now working my way through the books on Lean Software Development by Mary & Tom Poppendieck. More on books in a post.

P.S. - You're My First Comment :-)
Hello Peter,

I have just write something about how to start with scrum on my french blog : http://www.fredericdoillon.com/2008/05/source-scrum.html

Some other interesting links!

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …