ScrumBan: Best of both worlds - A Fertile HybridJaya S
schedule 1 year agoSold Out!
We're living in the days of fusion where fusions have created extremely useful products. There are fusions like western music with Indian classical, Pizza with Indian dishes like Paneer etc to name a few.
Scrumban is also a fusion generated by combining the best practices of Scrum and Kanban. Scrum is an excellent framework for delivering the software by using iterative incremental way while kanban "Just in Time" technique enables us to handle on demand agility for frequently changing and dynamic working environments.
Scrum framework consists of artifacts and roles while kanban is a visual board which deals with Work in the form of Work in Progress limits. There are situations where our product development environment faces ever changing priority and requirements.
ScrumBan is an effort to combine the iterative development and role based responsibilities of Scrum along with capability to handle the adaptive dynamics of Kanban.
Scrumban can be used effectively for product development as well as for maintenance purposes. In scrumban we do a Release Planning but not sprint planning. Planning on Demand is the characteristics of Scrumban where based on the items on the Scrumban board we decide to do planning or product demonstrations.
Scrumban also imbibes some new concepts of release planning called Triage & feature freeze which greatly improves the product quality.
Agile Metrics: Identifying the Good, the Bad, and the Ugly
Getting good information about how your teams are doing can be challenging. There are some very traditional metrics that we use in Scrum to see team progress, but are you getting the entire picture? Are your teams actually doing badly but you can't tell? Where can they make some improvements? Your metrics should be able to tell you - at a glance - what's going well and what's going badly.
In this workshop, we'll review, discuss, and create several different metrics you can use to track your team's progress. Are they on track? Are they lost in the weeds? What kinds of metrics are most useful for the kind of agile methodology your teams are using? For instance, Kanban requires a whole different way of measuring team accomplishments than Scrum. After taking this workshop, you should understand the different kinds of metrics, which metrics are most useful for which methodologies, which metrics you aren't using will help identify anti-patterns, and how to identify teams that are on track or off the rails.
Scrumban - Best of Flow and the CadenceApeksha
schedule 1 year agoSold Out!
An Organization change is sustainable when its evolutionary instead of revolutionary. Organizational change using Scrum is disruptive and may yield results quicker. However it may encounter lots of resistance and may cause few heartburns as well. Kanban on the other hand is not disruptive and evolutionary. However, it needs to disciple to sustain continuous improvement. Organizations incur same amount of pain with bot the approaches but at different rates and times.
This talk is about making best use of both aproaches to bring in revolutionary changes at a sustainable pace with a story.