one reason bad ScrumBut happens (e.g., we're not finishing our stories at the end of a sprint so let's go to Kanban) is that we're focused on a practice - completing a story - instead of flow itself (short cycle time, proper WIP). If we realized the right issues we'd do better 1/
doing better might be don't allow devs to start stories until testers have completed theirs, or go to 1 week sprints. Or, it may be to use kanban if that gets focus on completion. our focus should be on improving our methods, not improving how we follow an approach 2/
imagine you're doing this - attending to Flow, WIP, ... (a good thing) and someone injects into the conversation - "But then wed not be doing Scrum" would that be a good thing or not?
One reason boundaries around an approach can be detrimental 3/3
One reason boundaries around an approach can be detrimental 3/3
@threadreaderapp unroll
