Mixing the Backlog and Sprint board together… gulp!

I’m trialling a new version of an Agile board for longer running projects. Ones that don’t have masses of tickets and set defined sprints, but are more on-going support work.

Because, normally I keep a separate backlog board with any number of columns, (whatever the Product Owner feels is easier). And then we create a board per. Sprint with these headings.

Sprint:

  • Iteration Contenders
  • Backlog
  • Blocked
  • In Progress
  • QA Failed
  • QA
  • Done

But trialling the new type, it will be,

Support Board:

  • Wishlist
  • Scheduled
  • Blocked
  • Doing
  • Done

This will be easier for the staff to interpret as their exposure to Agile so far has been understandably minimal. Also, we will require fewer boards as there’s less work.

Author: Dan Course

Dan Course, E-Learning Development at Warwick University (WMG). Agile Scrum trained and full-stack development. Interested in E-learning, Democracy, Politics and Tech. All thoughts are mine and not of my employer.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s