Bluffing your way though Planning Poker
Estimation is hard and the easy path sometimes a little too tempting.
DevOps - Software Architecture
Better software through software architecture and devops
@jamessnapeEstimation is hard and the easy path sometimes a little too tempting.
A little bit of styling can really help with your process. Using card colours can remove motion waste and save you time searching for things. Highlight, don't hide and run stylish stand-ups.
Tags are the simplest of concepts in Azure DevOps and other work item tracking systems. When you combine them with visual styles they become a powerful user experience feature.
It can be confusing knowing how to represent something in Azure DevOps. Should it be a work item? What about a task or new work item state? Here is my guide for you to classify with confidence.
An early task for your new project it so configure an iteration path. Going a little further than the standard iteration model can help with planning later.
Which process model should you pick for your brand new Azure DevOps project? You can change later but its easier to get it right at the start. Some processes might even cause you issues.
Teaser article for a series on how to do agile without starting from scratch.
Queues are used to load balance work between teams but its easy to overlook a decrease in efficiency they bring.
Metrics are only useful if they help you improve. Code coverage KPIs are most often circumvented. Liberal use of the ExcludeFromCodeCoverage attribute is to be avoided.
If you already know how to code in one language then using GitHub CoPilot Chat can be super helpful as a virtual colleague when you are working in new or unfamiliar territory.
Converting code between Javascript technologies isn't simple but GPT/Copilots can do a lot of the heavy lifting.