Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    Multi-week sprints are fine when you're doing product development work where the goal is being approached iteratively. It is not a good model when simple and well-understood tasks need to be performed which don't really take long by themselves. It's possible that a Kanban system may better fit the needs at least on the ops front. Commented Feb 24 at 14:31
  • @Hans-MartinMosner How would a Kanban system wouldn't ensure that someone is free to work the moment you need them? In my mind the choice here is whether or not to formalize and track the design work. Commented Feb 24 at 15:11
  • 1
    There's a difference between "I'll take on this important task right after I finished this other important task" and "We put it on the backlog to be considered for next sprint planning" :-) It's not about getting requests done immediately, but getting them done in a reasonable time. I must admit I'm not truly familiar with Kanban apart from the general impression that its flow-oriented nature makes expedited processing of prioritized tasks easier than the batch-oriented sprint process underlying Scrum. However, at the end of the day, it's a judgement call on how to best avoid waste. Commented Feb 24 at 15:25
  • @Hans-MartinMosner neither system speaks to this at all unless you make doing the design a ticket. Commented Feb 24 at 15:31
  • @candied_orange Scrum can be interpreted to include design under general refinement, or as a backlog item, its flexible that way. Kanban doesn't really have a good answer for design, other than maybe treat it as a work item in its own right. Commented Feb 25 at 22:29