Using tools for Agile Software Development

A simple explained overview and glossary for AzureDevOps users

Sprint

A journey of work, with a strict duration predefined. Usually, it lasts a pair of weeks, in the end it should deliver some value to the final project. These items that deliver some value are called Deliverables.

It is very important note that a deliverable does not require something that the customer will see, it can be a part of a set (as a feature), in this case, it should be called Increment. A deliverable that can be used by customer are called Release.

Work Item

All activity are Work Item. They can be, Epic, Feature, Backlog, Task, Bug, a Test Case or an Impediment.

Below, an example hierarchy:

Epic
|_ _Feature
|_ _|_ _ Product Backlog
|_ _|_ _|_ _ Task

|_ _|_ _|_ _ Bug
|_ _|_ _|_ _ TestCase
|_ _|_ _|_ _ Impediment

Epic

Optional. A huge collection of Work Item. You should use it, only if you have a group of items that can not be develop apart and it will takes a couple of sprints to complete it.

It can be considering a Release. I supose you should avoid considering an Increment.

Feature

A new characteristic or capability of the product, that, usually, aggragate some value for end-user. As add a way for users buy some product by your system, a new payment method, a chat for support or FAQ area, are some examples of Features.

It can be considering a Release, if no one pending project depends it. Other way, it should consider it Increment.

Product Backlog

It have an acceptance criteria (DoD), need to be approved (DoR), it duration is mensurable by points effort and its value for the business, proposed by the Product Owner, who defines its Backlog Item development priority.

XP developers may know it as User Story. UML designers can call it User Case.

It can be a Increment or Release.

Task

A specific, minimum and independent implementation, it starts on ToDo state, goes to WiP and it final state is Done.

There a lot of task activity types, they’re Requirements, Documentation, Design, Development, Testing and Deployment

Bug

It’s a type of task, but, it’s specific for investigation or correction of a issue, eventually, added by a task previously, it starts on ToDo state, goes to WiP and it final state is Done.

TestCase

Impediment

An difficulty or incident that stop the expected flow to complete the work. It can be a hindrance, infrastructure failure like a slow network or eletricity off, people relations, etc. Normally, it’s treated by the Scrum Master, or an equivalent team leader who have the experience and responsibily to deal with those risk conditions.