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 :-)
Anonymous said…
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

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…