9 ms·
> horribly broken JIRA installation That's the first thing I'd scrap. Software to control the process doesn't help unless the team understands and wants the pr
by Symbiote 10y ago
> horribly broken JIRA installation
That's the first thing I'd scrap. Software to control the process doesn't help unless the team understands and wants the process, otherwise it's just an annoyance.
My path towards Scrum started after a pointless and long meeting. I found some coloured memo squares and some drawing pins, and cleared everything from an old noticeboard. (This is nicer than using post-it notes on a whiteboard.)
I copied out the tasks, making a rough go at splitting them into reasonably-sized things, and making my own estimates in days. I made "backlog", "this week" and "completed" columns.
The resulting mess showed that the project wasn't under control, which itself was valuable. The PM and the 'customer' were then able to ditch half the requirements, and the developers could concentrate on the highest priority tasks.
This wasn't Scrum, but it worked well, and led to buy-in from almost everyone that we should try Scrum.
(The most important things I missed on the first go: acceptance criteria and team estimation.)