Skip to main content

Managing Scrum: Paper, Office or Dedicated Tools?

My first real Scrum Project was trial by fire. I didn't have much time to get organized or to learn new tools and techniques. While I did consider paper and cards, and The Book sings the their praises, I had never worked with them before nor had I ever actually seen someone using them. So when it came to the choice of tools for managing the backlogs and the daily scrum, there was really one alternative: the spreadsheet (better the devil you than the one you don't!). And that's how we got started.

Very quickly, we discovered the limitation of a standard software based approach. That spreadsheet becomes an impediment. In our case, keeping the spreadsheet synchronized between my version and the customer's version was a problem. The customer would change the layout in ways I did not want (and probably the other way around as well). And getting the updated product backlog back in time to plan the next sprint was also a never ending challenge. So we needed a tool.

Actually, the team decided they wanted a tool, so they evaluated several tools and eventually chose TargetProcess.

Much later, I attended two different CSM courses, once with Mike Cohn and once with Boris Gloger. Both teachers showed how to do cards and what cards are really good for.

So what is the value of the three alternatives to managing Scrum teams? What are the strengths and limitations of each?

I'll look at these options over the course of the next few days.

[ Next: Paper. ]

[BTW - A part of me wants to call this 'Rock, Paper, Scissors', but I digress.]

Comments

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 …