Do you do bad practice Scrum or you Scrumban?
5 signs you should go Scrumban, rather than Scrum or Kanban
Learn that doing “Bad Scrum” might be a new best practice.
What is Scrumban?
Scrumban is an Agile methodology that mixes principles from Scrum and Kanban.
The main principles Scrumban takes from Scrum are:
- Short Iterations
- Sprint Planning
- Sprint Review
The main principles Scrumban has from Kanban are:
- Limit work in progress
- Take always the highest priority task and get it done
- Flexible scope
Are you actually using Scrumban without knowing?
Here a list of 5 signs that should raise you some questions:
- Keep on moving the meetings as the sprint progresses
- You adapt to change in your backlog
- The scrum metrics don’t tell much to you
- Tight deadlines rather than when it can be done
- There is no specific Product Owner role.
While you see this list, they might look like bad practices on Agile, but you are actually adopting a new methodology without knowing!
Lear more about Scrum, Kanban and Scrumban and when to use them in this video from my YouTube Channel, where I release a new Agile video every Tuesday.
You might be interested in:
How to define Features in Agile Methodology?
In Agile methodologies, the features represent a chunk of functionality that delivers considerable business value.
Remote Feature Mapping Workshop
Feature Mapping is a technique that helps Product Owners, Product Managers, and teams to visualize the big picture of…
Seven things you shouldn’t miss during your PI Planning Meeting
Program Increment Planning meeting aims to bring together all actors that contribute to the Agile Release Train work…
11 Ideas for Innovation Sprint of Scaled Agile Framework
The last sprint of the Program Increment is the Innovation and Planning Sprint. Most of the clients I work with they…
How and why the personas must be the starting point of our user stories to build better products
This week I started a new project — CooLab. We need to create an application which helps cooks to reach more people…
Hamburger Method to Split User Stories from Dev team perspective
The main reason why I use the Hamburger Method to split user stories is to coach the teams to transit from the…
Nine user story metrics I care about while coaching Scrum teams
Goal: put in numbers the team performance. Numbers talk to everyone. When we see 98% performance there is no…
Why Velocity Works Better than Man Days Effort Estimation?
What is the velocity metric?