4 ms·
I've yet to see anyone actually do Agile where the tasks were broken up into reasonable increments. All of my Agile experiences involve a project manager throwi
by XorNot 8y ago
I've yet to see anyone actually do Agile where the tasks were broken up into reasonable increments. All of my Agile experiences involve a project manager throwing a sentence up on the board for what they want done and saying "yeah I think it'll fit in this sprint" for something which no one has any idea how long it'll take because the scope is unknown and no preliminary investigation has been done (a process which would take maybe a week).
"Task estimation" for sprints never seems to involve any actual data on which to base the estimates.
- rusk 8y agoI’ve experienced scrum done “right”. Company I was with made it a strategic thing and set aside time and money for the org to make the transition. It actually worked quite well in the end but it was a lot of work. It’s an outlier though - I’ve never come across a company before or since that would go to this much effort. Usually the conversation with management about implementing agile ends at the point where they realise the upfront costs.
- hippich 8y agoThere is a concept of "spike" work. Basically, when you do not know what it takes to implement something, you work on a "spike", the result of which will be new stories better describing what needs to be done.
- jasonlotito 8y agoWhat happens when the spike is done early in the sprint. Do you just hold off a week or so until you can report back? And who works on those follow up tickets? The person who did the research? They've had the most experience, so that makes sense to me, but I've been told everyone should be able to pick and choose, and if I don't grab the tickets fast enough, I'm sol.
- MBCook 8y agoPart of the spike should be documenting the results so that anyone else can use them if there are the person who picks up the next ticket. If the person who does it just remembers it themselves and doesn’t do anything to help the other developers then they haven’t completed the spike.
- jasonlotito 8y ago> Part of the spike should be documenting the results so that anyone else can use them Do you have other people on the team review this? Or do you just trust that it's complete? Sorry for all the questions, I just feel like these are things that are never answered adequately.
- MBCook 8y agoI would think it would be presented/discussed with the team. I’m not sure what I’m used to at my job is correct, so I’m trying to stick to my understanding of how I think it’s supposed to work.
- closeparen 8y agoThere’s nothing worse than having to execute someone else’s minute breakdown of work. People should be responsible for executing their own ideas. Then you get feedback on what was and wasn’t correct, and have only yourself to blame. Having that ownership stimulates a much greater level of craftsmanship and skill growth. Documentation is great, but the idea that a spike author and implementor should be different people is awful.
- MBCook 8y agoThe spike doesn’t define HOW the later work is done, only the information it was supposed to research. How to do something would be sorted out during grooming or perhaps when adding the story to the sprint.