4 ms·
It seems that those places are not taking Scrum seriously (as much as I hate this expression) > just weird conversations about when feature X is fully ready i
by raverbashing 12y ago
It seems that those places are not taking Scrum seriously (as much as I hate this expression)
> just weird conversations about when feature X is fully ready in which sprint,
What stories compose that feature? How are you going to plan the following sprints? (are there other stories or only those?). Prioritize.
> features that were done getting new "improvements"
Yes, you can split stories into 2, or create a new story for something that you want changed/improved. Create a story, put it through the system and do it
> and getting sprints replanned in the middle of execution.
It happens. But it shouldn't be frequent.
> Oh, and the famous feature requests disguised as bug reports for the features that didn't make it out of the backlog.
Well, that's not really an Agile problem, that's scope creep (and shouldn't be allowed)
It seems your problems are due to people implementing "half agile" or just using the buzzword without the important elements. Especially in small teams.
(been there, done that)
- pjmlp 12y agoI could have replied to myself the same way you did. My point is that I have never seen any company doing agile as their founders created it. Trying to push for agile way since 2006.
- raverbashing 12y agoAh yes, me neither (and I'm not interested in the nooks and crannies) But there are some places that managed to "get it".