Skip to main content

Sprint Zero

When I joined the project, we had just finished a release, but didn't have a clear definition of what to do next. So the developers were instructed to use the time productively, to wrap up whatever they were doing or do any long postponed housekeeping. I didn't want to take time to figure out what they were doing, much less tell them what they should be doing. So it was their first taste of self organization.

The customer was a bit skeptical about Scrum, but given the problems to date and the time pressures, he was willing to play the guinea pig.

During Sprint Zero, we got ready for our first Sprint. Scrum makes very clear what needs to be done before you can start Sprinting.

Scope, Quality, Cost, Time. These are the factors that any project manager has to have under control and these are defined very precisely for each sprint.

One one level, getting ready for Scrum means getting an initial definition of the project parameters. On the other level, getting ready for Scrum means educating the people involved (team and customer) so they know what is expected of the them, what they can expect from the other players, and how they can influence the process.

Scope

We had many feature lists, bug lists, wish lists and absolutely no idea what was really important. So this first step was to define the total scope. I collected all the feature lists, wish lists and bug lists I could find, and sent them to the customer with instructions to consolidate and prioritize the list on a scale of 1 to 3. The consolidated list had over 100 entries, and customer himself realized that the list of priority 1 items was so long that he had to introduce a Priority 0 to mark the items that were really important to him. This consolidated list became our product backlog.

During Sprint Zero, the team estimated all the Priority Zero and good chunk of the Priority One tasks (the twos and threes we left for a later date, which turned out to be never).

Quality

The team's first task was to take an hour or two and come up with a definition of done. Here's what they came up with:
  • Tested (Unit Tests, Test Casses passed)
  • Deployed on the Acceptance Test Server
  • Documented (JavaDoc)
  • Checked into Subversion
  • Successful build
  • Successful check-style
  • Completed code review
  • "Usable" for the User, approved by our usability guru
This last point had some problems with it, which I will write about some other day.

The team was also introduced to Scrum during this period, but that is also a topic for another post.

Time

How long should a sprint last? 2 Weeks, 4 Weeks? Originally my thinking was true to the book, 1 month. But we had a serious trust problem with the customer and substantial pressure to get a release out by the end of the year. So the customer wanted to work closely with us.

Not knowing what a release really entails, but knowing that a release takes about 3 weeks (with only 7 weeks left in 2006), I suggested we do a two week sprint, with a dry run release to exercise the process. Then another two week Sprint to get all the urgent functionality finished for the December release.

This idea was accepted, but the pressure from the customer's customer to get out a new release with bug fixes and missing functionality was intense, so we ended up installing our dry run release as well. This proved to be an important learning experience.

Cost

In our case, cost is defined by the number of developers assigned to the project and the duration of the Sprint. Sum for your team (Availability * Duration * Daily Rate) = Cost. Actually it's a cost ceiling. Under Scrum, there's not much overtime, so there is an upper limit on the costs defined by the time.

The actual cost will be lower, because people provide support, get sick, take a day off, get called urgently into another project, whatever. (Real availability of the development staff for actual development work can be a very hot topic with the product owner).

Communicating the upper limit proved to be a very good trust building measure. Our actual costs were always a bit lower, so the customer was always pleasantly surprised by the actual invoice.

Once we had the team prepared, the product backlog in place, and agreement on the Sprint Duration, we were ready for our first planning meeting.

Comments

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…

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…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…