Bram De Block: The case for Agile Evolution, Overcoming Dependencies, and Improving Team Collaboration through Product Domains

In this episode, Bram discusses the topic of agile evolution, a process of going beyond adoption, and adapting, and improving their agile methodologies. He explains that his organization used to work in Squads (based on the Spotify Model), each with their own backlog, but found that this resulted in a lot of dependencies and some teams had no “high value” items on their backlog, while others were too busy to deliver on the valuable items they had in their backlog.

He describes how that organization evolved to using Product Domains instead. The change team used MURAL to help visualize the changes, and invited people from every team to join and build a picture of the future with Product Domains. In that process, they went from 17 squads to 7 product domains.

Bram also provides tips on how to make the changes super clear, write down what the teams and organization will STOP/START/CONTINUE, and have follow-up sessions while timeboxing the whole work of defining the “future state”.

He highlights the importance of commitment and timeboxing as a trigger for action, and advises to avoid the anti-pattern of considering the “next change” as the final word. The episode aims to help organizations evolve their agile methodologies, to overcome common challenges and to improve the collaboration and communication within their teams.

As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

 

About Bram De Block

Bram is not an official trainer, consultant nor freelancer. He is just himself, supporting colleagues in applying and growing their own potential and getting stuff done. Bram started as a software developer for 10 years, then grew into a half-time agile coach, and finally, full-time “Global Agile Lead” at Skyline Communications. Something “special” he learned (even if he wishes it wasn’t special): the meaning and impact of “respect”.

You can link with Bram De Block on LinkedIn, or meet Bram face-to-face at this meetup he hosts in Belgium.

BONUS: Incremental Delivery in Business Intelligence (BI) and Data Warehouse projects with Raphael Branger

Raphael has been a guest on our regular show, and in those episodes, we approached the topic of Agile applied to Business Intelligence projects. In this episode, we dive deeper into the concepts and ideas that Raphael mentioned earlier, and we learn how Business Intelligence projects can be delivered incrementally, and in an agile manner. 

Slicing User Stories to enable incremental delivery

We start this episode with a practice that is critical for Agile teams: how to slice User Stories to enable the delivery of incremental value to customers. We discuss several strategies that Raphael uses to be able to deliver valuable functionality even in the first week of a project. 

Taking into account that usually, BI projects are executed by larger, and more traditional firms, his approach brings clarity and ensures that the team and the customer are able to evaluate the product from the first week. This practice is critical in collecting feedback from customers early on and avoiding producing products (dashboards, in this case) that no one will use. 

In this segment, we refer to a blog post by Raphael where he describes his User Story slicing approach in more detail.

#NoEstimates in BI projects

One of the inspirations for Raphael’s work on slicing User Stories was the #NoEstimates book and a few conversations that he and Vasco Duarte had in the early stages of Agile adoption at IT-LOGIX, Raphael’s company.

In Raphael’s perspective, the focus should shift from “sizing” stories to understanding what might be a good experience for the customer: customer delight; and then validating those assumptions directly with customers by delivering possible solutions very early on. 

As a way to apply #NoEstimates, Raphael started to apply the concept of “timebox” (limited time) to each of the User Stories being developed. His own rule is that a User Story should be developed within 1 or 2 days at the most, which pushes the teams to focus on what is critical to provide value to the customer. 

Timeboxing User Stories to validate assumptions

In this episode, we also explore how Raphael came to the realization that User Stories need to be timeboxed, rather than estimated. He shares a story of a project where the team produced a dashboard that did not get used by the customer (they had metrics). That was a transformative point in Raphael’s approach, leading him to focus on early and often delivery. Which led to the #NoEstimates heuristic that a User Story should be given a timebox. 

In this segment, we refer to the episode about a team that Runtastic that is using #NoEstimates, and how that has helped the team focus, and provide value faster. 

About Raphael Branger

Raphael Branger is a Certified Disciplined Agile Practitioner and a pioneer in adapting agile methods in the context of data and analytics projects. He works as a Principal Consultant Data & Analytics at IT-Logix in Switzerland with more than seventeen years of experience in business intelligence and data warehousing.

You can link with Raphael Branger on LinkedIn and connect with Raphael Branger on Twitter

 

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works
A Quick & Practical Guide to Agile Projects for BI
No Spam. Only your book. And you can unsubscribe any time.
Start Reading Now