On the other hand, I´m using kanban in predictive projects to manage specific phases of the project with many tasks to be coordinated in a daily basis, but with a Gantt chart in a higher level.
Are you asking on which projects a Kanban continuous flow-based approach would be preferable to a sprint-based approach? That really comes down to understanding the workflow itself. Sprint-based approaches work well when dealing with teams which are new to agile delivery, where work items can be decomposed sufficiently that they can be completed within a sprint, and where the team truly collaborates on completing work items. When you are in a situation where work items regularly span more than one sprint or where the work being done is more of a workflow with work items passing from one role to another then Kanban might work better. Kanban can also be incrementally introduced - start with visualizing workflow, then introduce WIP limits and so on...
Kiron
Thanks Kiron.
Can any project be tried on trial and error basis in Kanban, even Scrum projects as well?
...
1 reply by Kiron Bondale
Dec 21, 2018 8:55 AM
Kiron Bondale
...
Milind -
I'm not a fan of the term "trial and error" when it comes to changing how people work as there is a human impact if we don't take it seriously. However, if we embrace the agile tenet of inspect & adapt, then yes, if the team wishes to adopt certain Kanban practices and adapt them based on empirical evidence over time, that's fine.
As far as incorporating Kanban into other methods, yes, Scrumban is just one framework that covers this.
Can any project be tried on trial and error basis in Kanban, even Scrum projects as well?
Milind -
I'm not a fan of the term "trial and error" when it comes to changing how people work as there is a human impact if we don't take it seriously. However, if we embrace the agile tenet of inspect & adapt, then yes, if the team wishes to adopt certain Kanban practices and adapt them based on empirical evidence over time, that's fine.
As far as incorporating Kanban into other methods, yes, Scrumban is just one framework that covers this.
Kiron Saving Changes...
Justus NScrum Master| BCBSTXArlington, Tx, United States
Our research and development teams use Kanban since they don't produce working software in Sprints like other Scrum teams do
...
1 reply by Sergio Luis Conte
Dec 21, 2018 10:32 AM
Sergio Luis Conte
...
There is no line in Scrum, there is no statement in Scrum, that said that Kanban, User Stories, Story Point, and other must be used. That is the power of Scrum. Unfortunatelly it has been jeopardized for people that understand things as they like to understand for their convenience.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 21, 2018 9:20 AM
Replying to Justus N
...
Our research and development teams use Kanban since they don't produce working software in Sprints like other Scrum teams do
There is no line in Scrum, there is no statement in Scrum, that said that Kanban, User Stories, Story Point, and other must be used. That is the power of Scrum. Unfortunatelly it has been jeopardized for people that understand things as they like to understand for their convenience. Saving Changes...
On the other hand, I´m using kanban in predictive projects to manage specific phases of the project with many tasks to be coordinated in a daily basis, but with a Gantt chart in a higher level.
