A naukri.com initiative
Medium
1M
98
Image Credit: Medium
Continuously right-sizing your Azure DevOps Features using Power Automate
- Right-sizing is a flow management practice to ensure work items are manageable. Teams often use historical Cycle Time data to determine a Service Level Expectation (SLE). Teams use Work Item Age to manage the flow of in-progress work.
- Teams will use data to proactively check ‘open’ Features to ensure they are right-sized. This guide covers the use of Power Automate to continuously automate right-sizing features. This tool is used to optimise features and foster a culture of continuous improvement and efficiency.
- First, add a new field into the ADO process template called Rightsized. We’ll set this up for Features. Each time using the field for different work item types will require a repetition of the same process.
- In the second stage, Power Automate tool creates a cloud flow to run every day at a specified time before work. The next step is to create two ADO queries for automation both for ‘closed’ and ‘open’ Features several months old. Then, Power Automate initialized various variables to enact the right-sizing of Features.
- The process involves applying the HTTP step with a GET method and adding in personalized Access Token details. Complicated steps such as the application of Parse JSON apply to each, Apply to each, and sorting variables are included in the process. The last step will be an update work item step to update Features based on whether they are or are not right-sized.
- Automated right-sizing in Azure DevOps using Power Automate can lead to faster feedback loops, reduced delivery risks, and improved predictability.
- In order to implement continuous right-sizing, teams would have to focus on maintaining manageable work sizes. The tool will ensure the data remains visible and actionable empowering teams to stay proactive.
- Once this tool is implemented, it not only optimises features but fosters a culture of continuous improvement and efficiency. Stay tuned for upcoming articles exploring the application of this principle to Epics in Jira!
Read Full Article
5 Likes
For uninterrupted reading, download the app