A Sprint Retrospective is a time-boxed session that comes at the end of a sprint and examines how the previous Sprint went — what things worked and what didn't. It’s also an opportunity for the team to devise strategies for improving the quality and effectiveness of future sprints.
In this article, I demonstrate how to conduct a Sprint Retrospective using Azure DevOps.
Before beginning, you might want to check my earlier article about getting started with Azure DevOps boards.
In the top right-hand corner of Azure Boards, click the shopping bag icon and select the Browse Marketplace option.
You might think that NASA astronauts spend most of their time trying to break records for the longest spacewalk. Of course, you’d be wrong. The vacuum of space is fraught with dangers, so astronauts spend most of their time going through checklists — lots and lots of them.
Checklists are essential for mitigating common problems and are used in all kinds of scenarios. For software engineers, a Pull Request (PR) checklist ensures that everybody’s PRs satisfy a standard set of quality assurance rules.
In this article, I discuss my Top 10 checks I do before raising a pull request.
Setting up unit test initial conditions can quickly become long, complex, and hard-to-read unless development teams adopt a consistent approach. This article explains why you should consider using builder methods in your unit tests, constructing more understandable business scenarios.
Let’s assume we’re writing software for an online sandwich shop, allowing customers to choose their fillings and dressings to build up their ideal sandwich.
Create these enums to represent the kinds of fillings you can have:
} enum LettuceType
} enum BaconType
} enum ChickenType
Before we cover Planning Poker and the PlanITPoker application, let’s first recap how a sprint planning meeting works in a typical development team.
In an Agile project, a sprint planning meeting is held to discuss backlog items that have been prioritized by the business. The backlog can have just about anything in it, such as bugs reported by application users or new features that are queued to be developed.
The team has a Scrum Master — or moderator — who introduces each user story to the group, providing a high-level summary of the requirements. This is an opportunity for the…
Don’t get nervous at the thought of delivering a presentation, particularly these days when talks are increasingly delivered over webinars and within the comforts of our home.
There’s no magic 🔮 involved — all you need is a single document to read from and the ability to sound confident, using your voice as your instrument.
In this article, I share how I prepared a careers webinar that I’ve given to students at colleges and universities. I’ll take you through the delivery and follow-up process, setting up visual aids, and circumventing obstacles.
I use Google Slides for my presentation.
This tutorial will show you how to get inspired to produce simple, stylish, and professional compositions for your abstract paintings.
Randomly make marks on a piece of card using a variety of materials. In the following picture, I used acrylic paints, pens, colored pencils, and oil pastels.
Every evening it seems these days, I’m looking forward to getting my work done then learning some more painting. I promise you — I will get back to software blogging sometime after summer 😂.
In this article, I’ll share with you how I painted a rainbow canvas in acrylics with the help of masking tape.
Place the board on paper (ideally an old newspaper if you can find one) and place six…
A re-runnable — or idempotent — SQL script means that no matter how many times you run it, you always get the same outcome. This means, for example, that you won’t get an error when you attempt to add the same table or drop a column that no longer exists.
This article will show you how to put checks in place to ensure you’re re-runnable SQL scripts are executed without hiccups.
n.b. Indexes are coming shortly!
You can use the EXISTS operator to find out if a record exists.
IF EXISTS (SELECT 1…
When attempting to resolve bugs, we sometimes don’t always have all the information we need, especially when dealing with urgent production issues. In these cases, we often clarify missing bug details through phone conversations or instant messaging, and helpdesk email channels.
However, in all other cases, you should raise bugs detailing as much as you can, including:
In this article, I explain how you can enforce those best practices in Azure DevOps using Templates.
To create a template: