Hot answers tagged

3

You Have More Choices Than You Think We can't move items backward in Kanban. Of course you can! Whether or not you should will depend on what "additional work" means within your current process. In most cases, it either means: Your process failed to complete or expose all the work needed to get a task to the Definition of Done for a given ...


2

The fact that Team A uses Kanban and Team B uses Scrum is probably incidental to the situation. Fundamentally, the two teams have a different attitude towards quality of their work and its impact on their customers. Besides impacting Team A's performance, they may also be impacting their external customers, which management may not even be aware of. The ...


2

TL;DR Assess the impact on the Sprint Goal, and then allow the Product Owner to fulfill her function accordingly. The Scrum Process for Handling Incomplete/Uncompletable PBIs [T]he story cannot be done...Should this problematic story be moved to Done, marked as cancelled and then resurrected in a later sprint[,] or should we simply mark it as blocked ...


1

I don't know of any official agile guidelines around this. There are a few things that common practice would dictate though: 1) It sounds like your team and business had exactly the right conversation about what to do when they discovered it was much bigger. Great Job! 2) The story was started and you stopped working on it. I would not move it to done - ...


1

So following good agile practices, I would recommend that you ask the Product Owner for the other team where your item is on their backlog. Request an estimate for when they think it will be committed to a sprint. If your dependent on a waterfall team then I would make the request to the project manager and functional manager for that team. In either ...


Only top voted, non community-wiki answers of a minimum length are eligible