With Agile, It’s Not What You Do. It’s What You Do Next.

With Agile, It’s Not What You Do. It’s What You Do Next.

I’ve been writing a series of tips about product owners, exclusively for my subscribers.

It got me thinking about the times I’ve seen teams and product owners obsessing over their entire product backlogs instead of getting started creating value for their customers.

You do not need to have your entire product backlog figured out to make progress towards your goals.

You only need to know what to do next.

Do the highest priority thing. See how your users and customers respond. Then let their feedback guide what to do next.

The Journey to Agility Happens One Step at a Time

The same thing holds true for transitioning to agile.

You don’t have to have it all figured out to start your journey. You just have to know what to do next.

Build a self-organizing team and give them a challenge.

Ask them to meet that challenge in a short, time boxed iteration (or sprint), during which they meet daily to quickly synchronize their efforts.

The team starts that first iteration by planning what they will accomplish. At the end they demonstrate what has been accomplished and reflect on how well they worked together to achieve it. And then they do it all again.

That's it. Anything else---release planning, burndowns, and so on is optional. Stick to the above and find the local optimizations that fit your environment.

Elements of Agile Survey

I can hear you asking, but what if I’m not sure what to do next?

When there are so many things you could do to improve agile, how do you know which effort will get the best results?

One answer is to take the free Elements of Agile survey on our site. You’ll receive a custom report that tells you:

  • How well you and your team are doing agile today
  • What you can improve next (and in what order) to help you get better agile results

I hope you’ll take the first step, and check it out.

Erik Kraa

Scrum Master. Mijn woorden zijn van mij, die gebruik ik op privé titel.

2y

No its who you are and how you treat people first

Like
Reply
Neelam Anand

VP RTE - ICP-ACC,SPC 6.0, RTE 6.0, LPM 6.0, CSM, 6 Sigma Green belt, PMP, Safe Agilist 4.5, PMPO, Rally/Jira

2y

Very deep meaning, says a lot ;)

Angela Spring, CSM®

Product Focused | Experience Rich | Agile Mindset

2y

If you don't try, you will never fail - First Attempt In Learning

Troy Benton

Ruthlessly Positive | Head of Operations at Plottr.

2y

What you do next indeed! Love this!

Victor Bonacci

Certified Scrum Trainer, YouTube Barista, Personality Hire

2y

iterative and incremental with intentionality #callyourshots

To view or add a comment, sign in

More articles by Mike Cohn

  • Issue 1: The What and Why of User Stories

    Welcome to Agile in Practice — a newsletter for people seeking to build and nurture high-performing teams. Each issue…

    11 Comments
  • You Don't Need a Complicated Story Hierarchy

    Consultants and tool vendors seem to have a penchant for making things complicated. It seems the more complicated we…

    7 Comments
  • Agile Teams Need to Balance Specialists and Generalists

    There's a mistaken belief that to be agile, every team member must become a generalist. What I find surprising about…

    28 Comments
  • Product Owners: Quick Action Isn’t Always the Right Course

    I’ve been doing a back-to-basics tip series, exclusively for my subscribers. This past month’s weekly tip focus has…

    14 Comments
  • What Happens When During a Sprint

    Successful Scrum implementations involve a handful of important sprint events (also called sprint meetings or sprint…

    2 Comments
  • What Are Agile Story Points?

    Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully…

    14 Comments
  • Don’t Equate Story Points to Hours

    I’m a huge proponent of estimating in story points. (You can get a full overview of how to use story points from…

    49 Comments
  • Epics, Features and User Stories

    I’ve been getting more and more emails lately from people asking, “What is an epic, a feature and a user story in…

    6 Comments
  • Nine Agile Halloween Costumes for Scrum Teams

    It’s time to start thinking about an appropriate costume you can wear to the many agile-themed Halloween parties you’ll…

    4 Comments
  • 5 Ways to Split User Stories: The SPIDR Method

    Splitting user stories. It’s something I get asked about every day.

    45 Comments

Insights from the community

Others also viewed

Explore topics