I’ve “done” scrum at my last job. I even led the implementation of it for a project. We sorta figured out what we were doing and got into a productive rhythm. But only recently, when starting it at my current job, did i actually read the official Scrum Guide. I was surprised to find out some of the things i thought were required were not mentioned at all.
- Scrum does not require have user stories. It does make you have a backlog of work to be done
- Scrum does not make you use points as estimation. It does make you have all items in the backlog be sized
- Scrum does not make you do estimation poker. It does require the backlog to be "well groomed"
- Scrum does not mention velocity. It does mention that you should pick tasks from the product backlog and do those tasks in an increment (what is commonly referred to as a sprint)
- Scrum does not mention the cone of uncertainty. It does define how long an increment should be, and that all work should be completed within the timeframe of the increment
- Scrum does not differentiate between bugs and features. It does require a definition of done, and everything must meet the team’s definition for it to be included in the increment
- Scrum does not use a task board of "not started, doing, done". It does define all the meetings, who is in them, and what should happen in them
The most surprising things to me were number 3 and 7 – those are artifacts that are commonly associated with the development methodology, but can be completely omitted if you’d like.
No comments:
Post a Comment