ScrumBan: Best of both worlds - A Fertile Hybrid
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.
Outline/structure of the Session
- Scrumban : what is it and where it can be used?
- Scrumban : A fusion
- A brief journey to Scrum & Kanban
- An MNC case Study : The Problems which leads to selection of ScrumBan
- Case Study: How concepts like Triage & Featurpe Freeze are used inside the teams
- ScrumBan Flow
The participants shall be able to learn about Scrum, Kanban, Fusion Princples, applicability, Usability and Pros / Cons of using scrumban
All Agile Practitioners, Enthusiasts, Thinkers and Fence sitters
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Scrum Dev : An effort towards Developer Friendly Scrum PracticesJaya S
schedule 1 year agoSold Out!
When faced with some challenge we try various things and finally find one silver bullet. Further we make use of the same silver bullet by incorporating it as part of Process and make it a rule to follow.
SCRUM as a framework has originated in similar situations and become the silver bullet for avoiding the ills of waterfall method. Scrum is successful and now widely used within multiple organizations.
Since SCRUM is almost 20 years old and 20 years of usage must have generated enormous feedback for the framework itself. Maybe it’s time to look at those feedbacks and do a retrospective on the way we’re using SCRUM.
My experience with multiple scrum projects taught me that one of the biggest de-motivating factor of working with scrum sprints are their monotonous nature of work. The sprint cycles with sprint planning and retrospectives becomes too repetitive to keep up the initial momentum.
We use the word “Just for change” quiet often for our own well being and happiness. SCRUM Dev is the same “Just for change” development practices incorporated within sprints.
These sprints contain unplanned working to themed based working which breaks the monotonous cycle of work and help maintaining the team momentum. At the same time it also benefits the product and its quality.
Transformation - The Devil is in the ExecutionJayaprakash Puttaswamy
schedule 1 year agoSold Out!
This talk is an experience sharing session about what it takes to realize business benefits in a large-scale (beyond 100 people) agile transformation. Having driven more than 4 large-scale transformation initiatives (of scales 160 to 700 people) over last 5 years, I would be sharing a couple of case-studies where I worked recently and I would discuss various challenges of implementing large-scale transformation and possible approaches to handle them. Participants would be engaged through interactive discussions on mutual experience sharing with a focus on key dimensions of agile execution.
As the title reveals, the talk would focus more on execution challenges and approaches to handle them at all levels of stakeholders involved in a transformation. Levels include developers, architects, managers (project/engineering), senior management (delivery/program management, directors) and CXO's. More details in Outline section.
The key dimensions to be covered include
- Building and sustaining learning culture (approaches include Community of Practice, Guilds and Joint Workshops)
- Causing the mindset shift in engineers (different approaches for developers, architects and engineering managers)
- Enabling managers to create and nurture agile engineering culture (approaches include effective metrics about quality of code, tests, application and build)
- Inverting the Test Pyramid (approaches include test automation strategies, BDD, dealing with Legacy using Strangler pattern, Component Guardian pattern)
- Leadership Agility (approaches include catalyst style of leadership, risk driven decision making, leading the change)
Lean Scrum - The need of the hour
The 2015 state of scrum report published by Scrum Alliance states that the outlook of scrum is highly favourable. Virtually all consider it likely that their organization will use scrum in future. While this is good, the survey also noted one of the key challenges observed by survey respondents as “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices”. Thus, although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address this gap.
Keeping scrum values at the core, scrum methodology is mostly visible to teams on the ground in terms of three pillars (1) Scrum roles (2) Scrum artifacts and (3) Scrum events. While Scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum. Scrum prescribed guidance on scrum events with clear purpose, frequency, maximum duration and recommended attendees. It recommends teams to learn the art of performing scrum events through their experience stating “scrum is easy to understand and difficult to implement”
While some scrum teams mastered this art, I find most of the scrum teams are still struggling in this process. I come across situations where teams are not finding scrum events interesting primarily because they find these events unproductive. The result is that we see less interactions and cooperation from the teams during scrum events. This is impacting basic agile manifesto “Individuals and interactions over processes and tools". In net, there is no surprise when product owners and teams were just not willing and/or enthusiastic about Scrum best practices.
Lean Scrum is the need of the hour. As part of lean scrum, we will adopt scrum methodology at the core and we implement lean framework to address the pain areas witnessed by teams
As part of this talk, I will share my experiential insights on
- Outlook of scrum is highly favourable. Although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address these gaps
- While scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum events. Are we keeping these events lean and Valuable?
- Lean scrum – The need of the hour
- What is Lean Scrum
- Anti-Patterns/Most frequently faced challenges/ wastes experienced by scrum teams in each of the scrum events (case findings based on my experience)
- Where do the scrum teams stand on "expected scrum patterns" in each of the scrum events (case findings based on my experience)
- Leverage "Lean Framework" to craft scrum events towards value generation. How to draw "AS-IS" and "TO-BE" Value stream management maps for two scrum events.
- Leverage "Lean framework" to help scrum teams to learn the art of performing scrum events through realizing value and enhancing their reach on "expected scrum patterns".
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software” The term value is increasingly becoming starting point of what we do. We need to keep questioning everything we do using customer value generation as the yard stick
Unless, we drive scrum events towards value generation by continuously eliminating waste/ anti patterns, there is no surprise that “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices” as observed by "The 2015 state of scrum" report.
This is where Lean-scrum could prove to be powerful...
How to measure the outcome of Agile transformation?Rahul
schedule 1 year agoSold Out!
With many organization moving to Agile environment, it is important to have a model that can help us identify if the Agile Transformation is resulting in the expected outcome. This session would present different measurement models to measure the outcome of Agile transformation in an organization.
The paper covers various measurement models that can be used during different phases of Agile transformation. The session also presents outcome of a survey conducted by the author on how different organizations, Agile coaches & leaders are measuring effectiveness of their Agile implementation. It would present a research on how different organization perceive success of Agile adoption, what are the parameters used by different organizations and how different people present the changes observed by adopting Agile environment.
e.g. 20% respondents each said ‘Delivery cycle time’ & ‘Delivering business value’ as the key parameters. And other 20% mentioned ‘Working Software’ / ‘Customer Satisfaction’ & ‘Reduction in defects, waste & risks’ as the parameters for measuring success of Agile.
The session also presents a case study of Agile transformation where these different effectiveness measurement models were applied successfully. It covers various aspects like Business case definition of Agile implementation, Agile Transformation roadmap, Agile readiness assessment, Agile current state assessment, Agile effectiveness evaluation and ROI of Agile implementation.
The session would also include an Agile Innovation Game, where the attendees would brainstorm with their peers on how they currently capture the changes brought by implementing Agile in their organization.
Building Cross functional teams by example.
Cross functional team (CFT) as a whole has all the skills needed to build the product, and that each team member is willing to do more than just their own thing. Agile methodologies recommend long lived CFTs to implement agile manifesto and principles effectively. CFTs have become more popular in recent years for many reasons that include but not limited to:
- They improve coordination and integration
- They are flexible to adapt to changing market needs
- They develop innovative products more quickly
- They span across organization boundaries
- They improve problem solving and lead to more thorough decision making
To be precise, we are not fully agile if we do not nurture CFTs. Not far from now, you will see digital enterprises trying to compete with each other in developing and releasing their apps every 5 days. CFTs will become one of the fundamental pillars for agile methodologies to adapt to such aggressive future needs
Building CFTs is an art and nurturing collaboration among CFTs is even more challenging. In this talk, I will explain about
(1) Building Cross Functional Teams by Example
(2) Nurturing Cross-functional Team Collaboration
(3) Imperative elements that need to be considered for succeeding with cross functional teams. Without proper attention to these elements, any cross-functional team will be fighting an uphill battle to succeed.
Ineffective release planning makes teams oscillate instead of iterate
Although agile methodologies have greatly increased productivity, Agile is not without its problems. Agile recommends adaptive planning through its multi-level planning events. Agile planning is expected to remain relevant in guiding teams till their destination as it incorporates the then risks, issues, assumptions and constraints into consideration while planning at last responsible moments.
While it appears good on paper, I find challenges involved in this approach. Scrum teams on the ground may mostly focus their efforts on their team specific daily and sprint targets. They lack common understanding of team expectations on what is probable product that they think is possible at the moment with the list of the then risks, assumptions, constraints and dependencies. To be precise, teams on the ground lack this bottom up view of the integrated probable product in next 2 to 4 months
On the other hand, enterprises spend efforts and money for their strategy, portfolio and product planning exercises. The result is that these planning events tell the top down view of “Where Product owner want to take the product to be?”
When top down view and bottom up view are not properly balanced with proper discussion among stakeholders during release planning exercise, we see teams oscillating instead of iterating witnessing below symptoms.
- Teams slips on their release forecast
- Cross team dependencies are detected towards end of the release and there was not much time available to resolve those dependencies within the release
- Key decisions that were supposed to be taken during release planning exercise, would be taken up towards final sprints.
- Risks are identified towards the end and this gives less room to mitigate the risks
When these symptoms recur periodically, as an enterprise, we would not be in position to provide the expected functionality to the end users. This may ultimately hit team’s morale and enterprise brand. Part of this chaotic pattern may be attributed to agile planning events.
This can be overcome if we perform release planning exercise effectively. But surprisingly, not much literature is available on how to perform release planning exercise even though everybody underlines its importance. In result, we see anti patterns keep creeping and they derail release planning objectives.
In this talk, I will be listing potential probable anti patterns that can derail teams from achieving their expected outcomes. I will introduce each pattern in the format
- Potential Impact
- How to address this anti-pattern
If performed well, release planning exercise makes stakeholders meet together and discuss the challenges involved in unifying the top down understanding of “What the product Owner wants the product to be” with the bottom up understanding of “what the development teams thinks as the possible product scope that can be accomplished”. This inturn will be input to upcoming product planning events. Release planning thus acts as a guide post to baseline current understanding of team expectations on what is probable product that they think is possible at the moment with the list of the then risks, assumptions, constraints and dependencies.