Updated: Nov 7
Hello Agile aficionados,
Microsoft Teams Ticketing is a versatile tool. You will read here below how to transform a ticketing instance to support an Agile Scrum project.
First thing first, a short introduction to Scrum
What is Scrum?
Scrum helps people and teams deliver value incrementally in a collaborative manner. If you are just getting started, think of it as a way to get work done as a team in small pieces at a time, with experimentation and feedback loops along the way.
Main Artefacts in Scrum
A product backlog is a list of everything that needs to be achieved on a project, broken down into individual items. This is where the baseline requirements of every feature needed for the end product are prioritized by the product owner for the scrum team.
The product backlog is made up of three different types of items.
User stories, which are high-level descriptions of a feature, told from the perspective of the end-user of the product.
Bugs are problems that arise that the product owner wants to be fixed.
Tasks, which are assigned to the scrum team to complete.
Herebelow is the propose configuration of Microsoft Teams Ticketing to support an Agile Scrum Project
Create Agile Scrum using Microsoft Teams Ticketing
In the setting of Microsoft Teams Ticketing, we will then create different tags to easily capture this information.
So that we have different colors for different tags, we will create different tag categories
We have also created a Sprint and populate it with Backlog and 2 sprints
Because we wont use some standard fields, we will deactivate them
In the Agile Software Development framework, flexibility and adaptability are key to managing the iterative and incremental development process. Custom workflows in a ticketing system allow Agile teams to define and adjust their processes dynamically to accommodate various Agile practices like Scrum, Kanban, or XP (Extreme Programming). This flexibility ensures that the ticketing system can support the fast-paced and evolving nature of Agile projects.
Typical custom statuses in an Agile workflow might include:
Backlog: Tickets representing new features, user stories, or tasks that are prioritized for future sprints.
Planned: The ticket is scheduled for a current or upcoming sprint.
In Development: Active work on the ticket is underway.
Testing: The feature or fix is undergoing testing to ensure it meets acceptance criteria.
Review: Code or feature is in peer review or awaiting approval from stakeholders.
Blocked: Work on the ticket is impeded by external factors or dependencies.
Done: The work has been completed and meets the Definition of Done (DoD).
Accepted: The completed work has been reviewed and accepted by the product owner or client.
Deployed: The feature or fix has been deployed to production or a staging environment.
Rejected: The ticket has been declined, often requiring it to be revisited or reworked.
Once done, our ticketing instance is ready to use.
Managing Agile sprint using Microsoft Teams Ticketing
You can then create all your tickets and use tags to associate them to sprint and type of artefact (Bug, Task, User Story)
Using filter, you can then see the content of your sprint