An Introduction to Scrumban for Agile Marketing - 0 views
-
Scrumban was designed for more mature agile teams, those working in an unpredictable environment where plans and requirements constantly shift, and/or teams who are supporting existing products rather than creating new ones.
-
In a nutshell, Scrumban is driven by events and demand rather than a pre-established schedule. It focuses on minimal planning, providing just enough of a backlog to give the team enough important work to do next.
-
Scrumban also ignores the focus on egalitarian, cross-functional teams that Scrum emphasizes. Instead, it embraces specialized roles within the team (a more realistic way to handle marketing skill sets).
- ...6 more annotations...
-
Individual WIP limits govern the workload for each team member as well as for the team as a whole. This is vitally important, because it protects your team’s sanity as well as the quality of its work:
-
you don’t spend hours planning or estimating task size every other week just because it’s time to do that. Instead you only plan projects when your team reaches the pre-determined minimum threshold of new projects on their list.
-
In Scrumban you don’t have timeboxed iterations as you do with Scrum, so you need strict limits on how much work can be in each category (planning/doing/testing/promoting/etc.) to keep your teams from becoming overworked or scattered.
-
Kaizen basically means continuous improvement or change for the better, and on agile teams it should be a major focus.
-
Team members should be able to “call a Kaizen” anytime they feel that the process is breaking down, and you can also schedule them to occur when particular conditions are met.