Visual Requirements Management with Kanban

There is a lot of attention given to Lean/ Agile product development teams around the work done and the (Lean/ Agile) processes adopted in by the Dev team once a set of features (backlog items) have been identified for a set of sprints (scrums) and/ or Releases.

However, how do those features get to the team, nicely bunched up in Releases and Sprints?

There is a lot of upstream effort by Product Management that goes in ‘herding the cats’ – defining and maintaining the Product Roadmap with input from myriad and often conflicting sources, abstracting features and requirements at the right level, getting stakeholders to agree on their priority, and then decomposing them so that the Dev teams are continually churning out quality code and product features in a ‘just-in-time’ manner.

The work that the Product Management team does is at a different cadence than the Dev team. Most organizations and teams have not yet understood the criticality of managing this upstream work well, nor the effort that needs to be put in so that the Dev team is continually supplied with User Stories at the right time and stakeholders are satisfied the right work is being done at the right time.

This presentation provides some insights into how we solved this problem using Kanban (and of course, SwiftKanban!) – Visual Requirements Management with Kanban.

I hope you like it. If you do, please don’t forget to share this post!


Other popular posts on Nimble!

Comments are closed.

Get Notified!

Get tips straight to your inbox!

Subscribe To Our Newsletter

Get updates and learn from the best