Carsten Lützen: A step by step journey to #NoEstimates

In this episode, we explore the story of a team that started to question the way they did estimates. The PO would use the estimations provided by the team to make a certain number of assumptions and reports that just did not correspond to reality. In the quest to solve that problem, the team started to experiment with different approaches, and naturally evolved to a #NoEstimates approach. Carsten explains the steps the team went through as well as the insights at each step. A self-organized change story on adopting #NoEstimates!

In this episode, we refer to the #NoEstimates book

About Carsten Lützen

Carsten is an Agile Coach at the LEGO Group. Before that a Scrum Master for different teams. He has a deep love of graphical facilitation and professional coaching. Besides his full-time job, he shares weekly tips on YouTube and LinkedIn on Agile, Facilitation, and Coaching.

You can link with Carsten Lützen on LinkedIn and connect with Carsten Lützen on Twitter.

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

 

BONUS: #NoEstimates in practice, interview with the Runtastic app team

In this episode, we interview Andre, Fabian and Aleksandar, team members at one of the Runtastic App teams. At the time of recording, they had 5 months of experience with #NoEstimates at the team level, and that led us to explore how they applied #NoEstimates; what prompted them to change their way of working; and many other practical questions related to the use of #NoEstimates approaches in their product development work.

The path to #NoEstimates

Continue reading BONUS: #NoEstimates in practice, interview with the Runtastic app team

BONUS: The Agile Wire hosts interview Vasco Duarte on #NoEstimates – Jeff Maleski & Jeff Bubolz

This is a BONUS episode on the topic of #NoEstimates. The Agile Wire podcast hosts Jeff Bubolz and Jeff Maleski interview Vasco Duarte.

Some of you might have heard about #NoEstimates, and want to know more, and for others, it might be the first time you hear about it. Either way, in this episode we talk about the origins of #NoEstimates and why you may want to consider it when helping your teams. 

This is a shared episode with a fellow Agile podcast The Agile Wire, where hosts Jeff Maleski and Jeff Bubolz interview Agile practitioners. Both Jeff Maleski and Jeff Bubolz have been guests here on the Scrum Master Toolbox podcast.

About Jeff Bubolz and Jeff Maleski

Jeff Bubolz is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.

You can link with Jeff Bubolz on LinkedIn and connect with Jeff Bubolz on Twitter.

Jeff Maleski is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.

You can link with Jeff Maleski on LinkedIn.

BONUS: Marcus Hammerberg on predicting Software development without estimation

Marcus wrote a blog post about predicting progress in ‘well-defined’ projects. He used a simple example where uncertainty was very limited. You can read the details in the blog post. However, even when uncertainty about the work was low, the predictions he was able to do (and he collects quite a few metrics in that story), was limited. 

In this episode, we explore the limits to prediction, and how that affects how we should look at prediction in our own software projects. 

Embracing uncertainty and what that means in practice for software projects

Continue reading BONUS: Marcus Hammerberg on predicting Software development without estimation

2 major challenges I faced as a product developer

When I started developing software as a team member, and later as a project manager, I started to face some of the challenges that you are probably familiar with.

With the little experience I had, these challenges proved to be difficult to solve. During part of my journey, they even felt impossible to solve. I know better now…

The first and most important challenge for me was the need to meet a strict deadline.

We ended up calling it the Christmas problem.
Continue reading 2 major challenges I faced as a product developer

BONUS: Allan Kelly and Vasco Duarte on #NoProjects and #NoEstimates the latest trends in the Agile community

This is an episode about #NoProjects, #NoEstimates and introduces a unique, and 1-time-only workshop by Allan and Vasco that will take place in London in February 2019. Check out this page about the #NoProjects and #NoEstimates Workshop to know more.

In the past few years a few new trends have emerged in the Agile community that have challenged some of the basic assumptions of how software should be delivered. The first one, #NoProjects is challenging the idea that software work is best managed as a project. As Allan puts it in this episode: “Successful software does not end. It continues. And projects are for temporary endeavours, that have a known start and fixed end. That’s now how software is developed today.”

With that start to the episode you can expect that many unconventional (and inconvenient?) ideas will be shared in this podcast focused on the latest trends in how to manage software development.

Read more… Continue reading BONUS: Allan Kelly and Vasco Duarte on #NoProjects and #NoEstimates the latest trends in the Agile community

Jella Eifler on Change as the operating model for Agile organizations, and how to reach #NoEstimates

Change is a big scary word in many organizations. But why is that? In this episode we talk about change in a different way. We explore what change would be, if it were the basic operating model of the organization. We talk about Nils Pflaeging’s work, about Complexity and how it affects the way organizations work in reality (as opposed to theory). As Jella says: “Change should be like adding milk to coffee.”

In this episode we mention the book #NoEstimates, How to Measure Project Progress Without Estimates, and Jella’s own journey to #NoEstimates.

About Jella Eifler

Jella has a background in linguistics (totally non-tech) and calls herself “agile native” (having never worked any other way, at least in software development). She works as a Scrum Master since 2014 at Qudosoft in Berlin. She has worked with both colocated as well as distributed teams.

You can link with Jella Eifler on LinkedIn and connect with Jella Eifler on Twitter.

BONUS: Mary and Tom Poppendieck on Lean Software Development, Business Agility and how autonomous teams enable adaptability

Tom and Mary Poppendieck have authored several books over the years about what needs to change in how we develop software to be able to meet the demands of the market, competition, and the growth in complexity of technology businesses. A recurring pattern they have witnessed is that people keep trying to discover a “silver bullet”. We explore why that is a bad idea and some of the changes in product development that make it an impossible quest.

Read on for the details, and all the links shared during the show.

Continue reading BONUS: Mary and Tom Poppendieck on Lean Software Development, Business Agility and how autonomous teams enable adaptability

BONUS: Erwin van der Koogh, #NoEstimates as seen by a CEO

Does your company need estimation? Listen to Erwin’s take. He’s a CEO. He should know.

Erwin has his own company and invests his own money in that company. For him, #NoEstimates solves a clear problem: too much time wasted estimating, instead of producing.

He challenges us to investigate how much money and time we already invest in that process, and then to measure the benefits. Are we getting enough return on the time and money we invest on estimation?

We learn about Erwin’s story of adoption. How he started with gradually larger projects, even at larger clients, and what he learned about the dynamics that push companies to make larger and larger decisions. Those larger decisions look like they require estimates, but why aren’t we questioning the need to make large decisions (large batch)?

Continue reading BONUS: Erwin van der Koogh, #NoEstimates as seen by a CEO