In this example, you will find how Teamhood marketing team applies Scrumban practices on day to day basis. If a refreshment of knowledge regarding Scrumban is required, check our post about what is scrumban?
We call it Scrumban because we intentionally do not apply all Scrum practices and focus on throughput (Kanban system). It’s a mix of techniques that is far from final and still is in the polishing mode. Lastly, we do not state that this is a perfect Scrumban definition, but more like a transition towards something else. Eventually, it can become a textbook Scrum or a textbook Kanban System.
Get more Scrumban inspiration from these Scrumban board examples.
We at Teamhood focus mainly on the digital side of marketing. We have divided responsibilities and tasks based on functional areas as such:
Initially, we had dedicated classes of service (Kanban swimlanes) for each area on our Kanban boards. But as we moved towards a fully centralized prioritization workflow, we no longer care that much regarding work type but focus on which area can deliver the most. People can switch areas and help each other if possible or necessary.
Our prioritized backlog is usually around 30 items and is limited to an absolute maximum of 40. Our unprioritized backlog currently has 67 work items and is unlimited. That makes a total pipeline of 107 work items.
For prioritization, we use RICE methodology which comes from the product management field, though we find it useful and applicable in marketing as well. A simpler alternative could be ICE, just we find better flexibility with 4 parameters instead of 3, as digital marketing spans across a variety of specific task types. Read more about the comparison of RICE vs ICE.
Below you can find two examples how our backlog changed from class of service to streamlined prioritization.
Prioritization board before RICE scoring: Marketing Backlog
Prioritization board with RICE scoring: Marketing Backlog with Rice
Prioritization is transparent and work type no longer affects priority. A separate backlog board gives better focus during sprints. Planning is clearly separate from execution. One week is the shortest possible iteration, could be worth exploring two weeks after some time. Another thing to add is to define sprint goals, so we can ensure that our output iterations are focused on the higher business goals. For example “Increase organic conversions count”. It would mean that sprint goal is a supporting prioritization tool when cherry-picking from RICE scored backlog.
We have also just started checking our agility metrics to see if we are getting better or not. This will serve as a baseline tool to continuously evaluate and trigger improvements.
Scrumban in marketing delivered for us and we know how to progress forward. It is just a mix of practices and one can freely choose the best fit for each case. It is about sharing lessons learned and best practices discovered.
If you would like to experience the same journey and need a tool – check what Teamhood can offer.