Planning/Reporting with BAU style workload

Steve Stevens_mxxuu4

My team uses Epics to collect Stories/Issues under Key Deliverable features which are goal orientated. ie, Deliver Product X to production.

But we also have to manage Business As Usual (BAU) requests, such as creating new SFTP accounts.

We want to start reporting more clearly the progress of an Epic and its Stories and have setup a "Releases" page to highlight the progress on these items.

However, we are unsure how to manage the BAU tasks as the "epic" is continuous.

It doesn't make sense for us to "COMPLETE" the BAU epic, as requests will appear adhoc, so it is never truly closed.

It also doesn't make much sense to leave the Epic "IN PROGRESS" because all the known tasks are likely complete.

 

Does anyone have any suggestions for this type of work so that we maintain visibility to the business without misrepresenting the work?

Lime Trees

Hi,

There's a lot of possibilities in Jira - it all depends how you would like to see these BAU tasks from your perspective.

You can create whole new project, especially for all BAU tasks.

You can add special user story for each Epic representing particular goal and then collect sub-tasks with BAU activities.

You can also make one user story for the project which will contain all these BAU things.

From our point of view and experience in project management and reporting, all of these solutions have its pros and cons - it would help if you could share some more information - are BAU tasks connected with particular product/goal? Are they repeatable? etc.

Regards,

Lime Trees Support Team

More about us