How Scrumban has evolved from its roots as a model for continuous flow into a framework with three potential paths: an alternative approach to introducing Scrum as a development methodology; a set of additional perspectives and capabilities that can help existing Scrum teams overcome common challenges associated with successfully adopting Scrum; and a framework for discovering and evolving new practices and ways of working that work best in a given context.
Though Scrumban is frequently viewed as a “new” framework,it’s actually built upon a great deal of established science. Systems thinking and the holistic understandings that come with it are essential to aligning vision, strategy and decision-making within a team and across the enterprise.
The first line of responsibility for aligning vision, values and purpose across an organization lies with its leaders and managers. Employees, however, have an equal responsibility to seek out clarity when actual alignment is cloudy. Frameworks like Scrumban provide a structured way of discovering what we need to know when .
Scrumban was initially conceived as a continuous flow delivery model representing the “next generation” evolution of Scrum. A review of the thinking behind this origin enables us to appreciate how Scrumban has evolved to help practitioners realize alternative outcomes, as well as the power behind how integrating inputs and outputs from other models leads to better decision-making in our work.
The most successful Scrumban adoptions are those where thoughtful consideration is given to the wide variety of factors that influence success, from what we choose for team size and sprint duration to the approach we take in orienting team members to specific practices and events.
In large measure, we develop ways of working to try and exercise some control over the uncertainty and risk inherent in our work. From queuing theory foundations to the recognition of psychological barriers around change, Scrumban’s principles and practices interact to expose a variety of different ways we can exert more influence and control around our work.
The "plan-do-check-act" cycle is central to Scrumban, and understanding why we measure is essential to measuring the right things. Proper measurements help us understand the health of our undertakings as well as arming us with knowledge that leads to better decision-making.
While teams and organizations will benefit from adopting Scrumban, widespread and sustained success can only be achieved when leadership is invested in reinforcing the vision, values and practices that make it happen. Scrumban goes one step further in also providing a framework that allows teams to achieve clarity where these things are fuzzy, and catalyze necessary change for better performance and satisfaction.
To operate at the highest levels of performance and satisfaction, we need to recognize and manage the invisible forces that constantly seek to move us further away from order toward chaos. Teams and organizations can follow an infinite number of paths as they increase their insights and capabilities with Scrumban.
Software development and IT operations are filled with risk and variability, making it difficult to develop accurate forecasts. Scrumban is an incredibly robust framework teams and organizations can employ to leverage more reliable means of forecasting, with an emphasis on probabilistic versus deterministic models. You determine what level of mastery and sophistication best works for your context.
Summaries of core fundamentals, case studies, additional models, and sample work flow visualizations.
Many firms have adopted Scrum without fulfilling its full requirements—they haven’t changed their context to one that’s truly suitable for Scrum… Ajay Reddy is an experienced Scrum practitioner who has been through the same journey you find yourself on… Let Kanban help you achieve that, and allow Ajay to guide you in how to do it.
Ajay is taking Corey’s ideas a step further, providing some more potential implementations for teams who would rather be successful than blind followers of canned processes. This book will help you to pay attention, to see the work you are taking on, to demonstrate to others the load you are dealing with, and to begin to take control of your work in process. But don’t stop here: Ajay calls it (r)evolution on purpose. Evolving is a continuous process.
Thank You! Your message has been sent.
Something went wrong, try refreshing and submitting the form again.