28 July 2008

Book Notes: Scrum and XP from the Trenches

As I read books, I note the contents that I think are most important - for me. You might find it useful, but consider reading the book for yourself: Henrick Kniberg: Scrum and XP from the Trenches.

This one even comes as a free online edition, which I printed out and read in one afternoon. Then I bought the printed edition for $22.95 - worth every penny. If they had a hardcover edition in color, I would not hesitate a moment to get that as well.

I got the printed edition specifically to let it circulate in the office and do some damage. Within 4 days, 3 people have read it, and the 4th one has it on his desk now. One of our teams had its very first retrospective after that, and suddenly the quality of our stories is the subject of many discussions. Many, good results within less than a week - that's how good this book is.

Here is my brief of the content, in my own personal order of importance.


Scrum Master Checklist
  • After Sprint Planning
    • Create Sprint Info Page
    • Link to it from the wiki
    • Print it, put it on the wall for bypassers to see
    • Spam everyone with sprint goal + link to sprint info page
    • Update sprint statistics (velocity)
  • Every Day
    • Daily Scrum Started + Ended on time
    • Stories added / removed to sprint backlog as needed to keep sprint on schedule
    • Inform PO about changes to the sprint backlog
    • Backlog + Burndown is up2date
    • Resolve problems + impediments, report them to boss
  • End Of Sprint
    • Sprint demo (everyone should know the date)
    • Retrospective
    • Update sprint statistics

Retrospectives

Goal of the retrospective is to improve. Answer the question: "What can we do better?"
  • Plan 1-3 hour retrospectives, in separation - without disturbances.
  • Show + Summarize sprint backlog
  • Do the round. Everyone gets the chance to say good+bad+ugly+ideas
  • Summarize ideas + suggestions
    • Good: what would we do again
    • Improve: vote on ideas for improvement, select only the top 1-2 ideas
    • Not all bad things need to be acted upon. Some problems solve themselves with experience.

Sprint Planning Agenda

  • 30min: PO goes through sprint goal and summarizes backlog.
  • 1h 30min: Team time-estimates, breaks stories down into tasks. Importance of stories is updated accordingly, items are clarified. How to demo is filled in for all high-importance items.
  • 1h: Team selects stories to be included in iteration.
  • 1h: Select time + date for scrum meetings. Further breakdown of stories into tasks.

Each Story has:
  • ID
  • Name
  • Importance
  • Initial Estimate
  • How to Demo (this is, in essence, a use case, or user acceptance test)
  • Notes
Optional:
  • Components (We don't have this)
  • Requestor
  • Description: We have that additional. This could probably be the same as "How to Demo", but sometimes contain technical details that a user story should not have.
Important: No technical language! Describe stories in user terms that anyone can understand!

Preparation for Sprint Planning
  • The backlog should exist.
That's it. Surprisingly simple. In more detail:
  • Each story that has a remote chance to make it into the iteration should have its own distinctive importance.
  • Product Owner (PO) understands all stories, and can clarify them.
  • PO is the only one who defines priority.
  • Team is the only one who defines estimates.

Sprint Planning

  • Output:
    • Sprint Goal
    • Know which team members are available
    • Commitment of the team
    • Backlog for sprint
    • Time + Place for daily scrum meetings
  • Agenda:
    • PO summarizes goal + most important stories
    • Team estimates stories, starting with the most important
    • PO answers scope questions for stories.
      Note: Code quality is part of the scope of any story that is absolutely not negotiable. Code must be clean, hack-free and, if possible, unit-tested. UI can be crude if it is going to be fixed later, but quick fixes in underlying code are a big NO-NO!
  • Agenda Detail, Example:
    • See Above

How to decide which story goes into the iteration

  • Use your gut feeling.
  • Once you did a few iterations, you know your velocity and can use that too. I don't know my velocities, so I didn't read those few pages.

Use Index Cards


Usually, teams sit around a computer or stare into a beamer while doing milestone planning. They go through story after story until they're finished. This sucks, big time - because it is a big waste of everyones time: while one person is driving the keyboard, all others are forced to watch and fall asleep. Using index cards not only keeps them awake, it also is faster and more fun. Update your excel sheets or whatever you use AFTER the meeting.
NOTE: I found this advice to be one of the best, and just used it in my second planning meeting. It works wonders, really is much faster and more fun.

Importance values are used only initially for the priorities. Strike them out as soon as you re-order your stories.

Time-Estimation is easier if a story is broken down into tasks first. Stitch tasks with small post-its onto your stories.


Definition Of Done

  1. Alpha-Tested
  2. Tester says it is OK
  3. Unit tested
  4. Documented (short)
Don't be too strict with your definition of done, and don't apply it to each story equally.
Bummer. We still have none of that, and it came back to haunt me today. Big time. Some day, there'll be a post in the "In The Pit" series about that.


Breaking Stories into smaller ones

  • Story: Stuff that is visible to the PO or user.
  • Task: Stuff that is not.
Example: the story "User Management" could be broken down into "Add User", "Edit User", "Query Users"


Possible Default-Tasks for stories

  • Clarify Requirement
  • Write test cases
  • design GUI
  • implement core
  • implement UI
  • integrate, debug, refactor
  • test + document

Where to draw the line

The result of a sprint planning should be, in order of importance:
  1. Sprint Goal + demo date
  2. Stories accepted for this sprint
  3. Estimates in all sprint-stories
  4. How to demo filled out
  5. Velocity + resource calculation
  6. Time + place set for daily stcrums
  7. Stories broken down into tasks
If the planning meeting drags on and on, cut it after your defined time-box expired. Brutally. Let the sprint suffer. Adding extra hours to the meeting is not going to help the team to be able to break stories into tasks or clarify them, It is only going to wear everyone out.


How to deal with tech stories
  1. Try to avoid them. Transfer them into normal stories.
  2. Do it as a task in another story
  3. Treat it as a normal story. This will be difficult to sell to PO and users.

Communicate Your Sprint
  • Spam the company.
  • Create a wiki dashboard, keep it up to date.
  • My own addition: make sure people know the backlog, especially management and sales.

Demos

Team members should at least attend the demo, even better: give the demo themselves.


No comments: