Scrum

Estimation Alternatives, Part 1: Feature Budgets

by
A metal pail filled with hundred dollar bills.
A powerful estimation alternative is to treat project funding as a budget and charter teams to spend it effectively.

The most common question on any project is, “How long with this take?” This question isn’t too difficult to answer when the work is small – a few minutes to a few days. Problems start when someone wants an estimate for a chunk of work you can’t complete in just a few days. Requests for estimates like this come from a need to make higher-level planning decisions. But estimates aren’t the only way to make these decisions. Over the last fifteen years of working with agile teams, I’ve seen value in exploring estimation alternatives. Two, in particular, come to mind, the first of which I’ll describe here: Shifting conversations about estimating to budget discussions.

Continue Reading→

Antique key in a keyhole

The Secret to Backlog Refinement (and Five Bonus Tips)

by

Antique key in a keyhole“What’s the secret to backlog refinement?”

Eighteen pairs of eyes turned to look at me, waiting for my answer to this product manager’s question. I’d spent the last two days with the group working through the challenges they faced using Scrum in their company. We discovered that most of their delivery problems stemmed from the teams not understanding what was needed. They’d identified with the story I’d told about the team that hated Sprint Planning and hit the reset button on their process. They knew they weren’t doing refinement and could see the effect. They wanted to know how to make it work for them.

Continue Reading→

Water flowing over rocks in a mountain stream.

How to Improve Transparency and Flow in Your Team’s Work

by
Water flowing over rocks in a mountain stream.
Teams should expect surprises to happen – even if they don’t know exactly what or when. Agreements about how to manage challenges when they do occur can keep them from disrupting the team’s flow.

The team was struggling. They were working on an industrial motion control product, porting a legacy code base to a new hardware platform. Parts of the code were decades old, and many of the original developers no longer worked at the company. They kept getting stuck trying to figure out how the code worked and what they needed to do to make it work in the new system. Neither the engineers nor the product manager had visibility into what was taking so long or how to help.

Continue Reading→

Global Listening When Remote

by

Many people are working from home at this point and this will obviously continue for a while. Many organizations had already been working remote. I’ve worked on a number of remote teams and with a number of remote organizations well before the current situation we are in. I’ve done remote work as a coach, trainer, product manager, and team member well before the current situation we are in.  Each of those instances I found myself enjoying some aspects of the work and also wishing for aspects to be in person. One of the most challenging things to do remotely is to listen.

Continue Reading→

Scrum Commitment or Forecast

by

I’ve been training, talking, coaching, and writing recently on the topic of commitment and realized that anytime that comes up, it reminds me of the old (seems old – but not really that old!) discussion on commitment or forecast. I still find there are many questions on this topic. It certainly has not been put to bed. The approach I like to take is to step back and ask “what is the real problem?”  Is a word stopping you from succeeding or is something else causing the problem?  What am I talking about? — I’m talking about when the Scrum Guide was updated to change commit to forecast.

Continue Reading→

Agile Safari – Best Agile Project Management Software

by

No, I don’t hate agile project management software — it can serve a purpose. At issue is if there is an actual purpose and if it is misused. Often the software stalls progress or worse, move us backwards. For any readers who are not familiar with agile or don’t work in software — the idea here is that instead of using the monitor to display some type of software tracking tool, the new scrum master just used sticky-notes and stuck them on the monitor. What is the simplest thing that works in your world? 

Continue Reading→

Agile Safari – What’s Not Being Said?

by

Have you been in a situation where no one would bring up the problem that everyone knew was “in the room?” I’d guess that everyone has been there. So often, we don’t bring up the “elephant in the room.” For anyone who has not heard of this, the elephant in the room is a saying for the real or obvious truth that is not being addressed. Given an elephant in a room would be hard to miss, when people ignore it, they are typically pretending it is not there.

Continue Reading→

The Real Baseline Agile Retrospective Format

by

I always considered this six question format to be the Baseline Agile Retrospective Format.  I say baseline instead of standard because a baseline is something to build on, not an ‘always the way’ standard (I know I’m splitting hairs here).

I believe the six question baseline agile retrospective format is a solid way to teach people how to do an agile retrospective. They can see, relatively clearly, the different parts that should be included. It can be a useful starting point to address additional questions and challenges.

Continue Reading→