Thematic Sprints and Why It’s Useful

Photo by Jonathan Chng on Unsplash

In my current role we plan sprints based on user needs — we look at priorities and items that will add value quickly. There is of course some part of user/customer with the loudest voice (not literally), that results backlog items to trickle into the sprints. And then there is just pure business critical items.

But imagine this — you are a product manager for a B2B software, let’s say a CRM solution…

--

--

--

A product management professional building digital experiences that connect customers with brands.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

5 Steps to Write a Scope of Work Document

Your Go-To Guide to Agile Workflow

Ultimate Tips for Product Managers on How to Embrace Uncertainty

Product Roadmap Is Not Product Strategy

How product engineers build new features at TransferWise

Importance of Project Design in Project Management

How Working Backwards Backfired At Us And What We Learned From It!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Fareed Huda

Fareed Huda

A product management professional building digital experiences that connect customers with brands.

More from Medium

Product— Business, Data, Tech, and MMA

What is Project Management Star Tool, the Gantt Chart?

Agile vs Classic Project Management Principles

Top Myths of Product Management