- February 23, 2022
- By Greg Thomas
- In DevOps, Team
- 305
- 0
Whether you are using Agile, Scrum, Waterfall, your own implementation, the last thing you want to be focused on is the collection and aggregation of data as it pertains to your release. The Data The hallmark of any process you are using is that the data should be easily consumable, aggregated, and rolled up into
Backlogs are at the heart of your Product Delivery Strategy. Simply put, they are a story of what happens next. Whether they be bugs, epics, features, or user stories – they are a collection of the ideas, suggestions, concepts, and future of the product you one day will build. When left disorganized, they are a
Software is everywhere, helping us do many things we couldn’t do years ago. Thinking back to the early days with Source Control, VSS (Visual Source Safe) was my first introduction to source control and it looked something like that. Horrific I know, you should have tried branching with it (I said a prayer each time).
When you navigate to the Areas and Iterations section of your DevOps Administration you might have noticed a small blue bar at the top of the screen that indicates whether you would like to customize your work item types. In previous incarnations of Azure DevOps, this was a painful exercise as you had to run
Azure DevOps is a great tool for managing your backlog and what your team is focused on “Now”. And although it’s not a project planning tool per se, many a software development team relies on the metrics that come from these systems to answer the following questions to our teams at large; Who is working