For a few months we’ve been starting to use Agile, and specifically Scrum, methods in planning and managing our Web projects at work.
This week we adopted a new practice: planning poker.
Like many teams starting out with Agile practices we didn’t just jump in feet first and adopt every Agile method going; that would have been too much to take in. So we began with a few methods:
- Version control
- Stand-up meetings
- Informative workspace
- Product backlog
- Velocity
The photograph above, taken a couple of months ago, shows the planning board in our office — an information radiator — that shows us at a glance how many tasks are left to do, what’s currently being worked on, what’s in testing, what’s done and (unlike, I would guess, most other Agile boards) what we’re waiting for.