Tasks - Do you know when to check in code and associate it to a task?

Last updated by Jernej Kavka (JK) [SSW] about 2 months ago.See history

In Scrum you work only on tasks in a Sprint, and the task must belong to a committed PBI. As such, when you commit code in Azure DevOps (was TFS), you should associate it with the task you are working on rather than the PBI.

The reason behind this is that doing so provides a better way to track change sets in a Sprint and give full traceability for work done during the Sprint.

Change set 123 was associated to PBI 'As an end user I want to be able to lookup customers'

Bad Example - The change set was associated to a User Story not a Task

Change Set 123 was associated to Task 'Create database fields for customer' which is part of PBI 'As an end user I want to be able to lookup customers

Good Example - The change set was associated to a Task

We open source. Powered by GitHub