Our software team has essentially these storyboard columns:
- To Do
Unfortunately, people inside and outside the team often attempt to affect the board to represent pre- and post- states of stories.
This has resulted in a board which now looks like this:
- To Do
- Dev Test
- To Test
While I understand that these are completely reasonable and each team has it's own interpretation of the scrum board, I would like to know if and how anyone running into similar problems has been able to get back to 'pure' columns?
Questions to that end could/would be:
- What is your definition of 'Develop' or 'Test' when in practice each of those can mean potentially 3 different states (waiting for, doing and completed/needs sign off)?
- What is the maximum number of columns a reasonable scrum master should allow on their board, on average?