5 ms·
Poor scrum. It gets so maligned. If you have a high functioning, well gelled team with well developed communication habits and rituals, you don't need scrum. Bu
by madhadron 6y ago
Poor scrum. It gets so maligned. If you have a high functioning, well gelled team with well developed communication habits and rituals, you don't need scrum. But, guess what, those are few and far between, and scrum is an excellent starting point.
Whenever I see a complaint it's usually because someone involved has violated some part of scrum. It's run by the developers. They set what they're planning to work on. No one else should be talking in scrum meetings, and certainly not making decisions based on scrum meetings. It's totally fair to evict everyone else.
Take the hard problems thing. You can tackle hard problems. Saying, "I'm going to try working out this prototype idea and do a literature review of this topic" is perfectly reasonable as a plan for a week or two.
- Scarblac 6y agoWhere I work, we can choose what we work on, as long as it's one of the backlog tickets the product owner wants done for the next release. The way they are formulated means there is very little room for solving hard problems (of the type that could result in fifty tickets not being necessary anymore), let alone making prototypes for things if they aren't guaranteed to releasable results for any of the tickets.
- madhadron 6y agoSo your product owner doesn't understand their role in scrum. It's a fairly common pathology.