Technical Work and Epic

Last post 04:41 pm May 18, 2021
by Daniel Wilhite
2 replies
03:25 pm May 16, 2021

We are putting together our hierarchy in the "product" mindset.  Epic (product) --> Feature --> User Story --> Task.  We are using Azure DevOps.  I was wondering when you have technical work (like creating tables, creating data model for Power BI), should I create them as user story and put it in underneath feature?  Feature is something like Weekly Financial View...  If you have technical work that is common across multiple features, how would that work? Is there any best practice in doing this not necessarily in the way that I mentioned earlier?  Any advise appreciated...  Thanks.

03:24 am May 18, 2021

This sounds like something the team should be doing when they refine the Product Backlog. In the team's view, how much of this detail needs to be added at all, so work is deemed ready for Sprint Planning?

04:41 pm May 18, 2021

should I create them...

You don't mention your role in the team or even if the team is using the Scrum framework but I ask why would you be creating them? If you are following the Scrum framework, @Ian Mitchell makes a great point. The developers should decide how to handle these type of activities in a way that makes the most sense to them since they are the ones that will be doing the work. 

And even if you are not following the Scrum framework, that advice still makes perfect sense.  Don't get caught in process, instead focus on getting the work done.