Structure Work Items in Azure DevOps (Beginners question :) )
Hi guys,
we are using Azure DevOps since few months and everything so far. We are using the Agile Process with Epic, Features, User Stories and Tasks.
So for the main part everything is clear to me, when we add a new feature for our application I create a feature item, a user story to explain the business view with acceptance criteria and tasks for the specific work that needs to be done to implement this.
But now we have some task like refactoring this, developing basic functions in code we can use in different areas of the app, optimize code structure etc.
For that part I am not sure how to add work items that we can track the work, have everything transparent in AzureDevops and following the structure of the Agile Process with Features, User Stores, Tasks etc.
Is it like to have a Feature (Refactoring part xy in app) and a User Story like “As a developer I want to refactor this method in code that we can use it in any other party of the application”. And the creating tasks for it?
So is the user in this case the developer instead of the customer (the end user of the application)?
Would be nice to hear some ideas and your experience, how to handle this! 🙂
Thanks guys!
Flo
Hi guys, we are using Azure DevOps since few months and everything so far. We are using the Agile Process with Epic, Features, User Stories and Tasks. So for the main part everything is clear to me, when we add a new feature for our application I create a feature item, a user story to explain the business view with acceptance criteria and tasks for the specific work that needs to be done to implement this. But now we have some task like refactoring this, developing basic functions in code we can use in different areas of the app, optimize code structure etc.For that part I am not sure how to add work items that we can track the work, have everything transparent in AzureDevops and following the structure of the Agile Process with Features, User Stores, Tasks etc. Is it like to have a Feature (Refactoring part xy in app) and a User Story like “As a developer I want to refactor this method in code that we can use it in any other party of the application”. And the creating tasks for it? So is the user in this case the developer instead of the customer (the end user of the application)? Would be nice to hear some ideas and your experience, how to handle this! 🙂 Thanks guys!Flo Read More