Azure DevOps Processes: Part 1

To me, setting up a DevOps implementation is akin to a customer engagement project. In both instances we need to understand the current processes being used by stakeholders, identify the minimal viable product and design and build according to the identified requirements/needs of the business.

Most businesses have a standard process they already adhere to. Whether it be a clearly defined and well known methodology e.g waterfall or scrum, a hybrid (e.g for lack of a better term “wagile”) or a custom methodology that their consultants or project team are familiar with.

Azure DevOps provides 4 processes as standard. When creating a project, the default process is Agile. However, by browsing to Advanced, you will be prompted to choose between the available processes.

Azure DevOps Standard Processes

Basic: This is the simplest process provided by Azure DevOps. The basic process tracks tasks from not started, doing and done and only tracks three types of work items. These are epics, issues and tasks. In part two of this blog, we will review the differences between these work items.

CMMI: The Capability Maturity Model index closely relates to a standard waterfall methodology. It includes work items which allows a formal change management process as well as work items which allows the project team access to Risks, Issues and Decisions from within Azure DevOps.

Agile: The agile process is, as you’d expect it to be, a process which adheres to Agile principles. The terminology used to define work items as well as the functionality available makes this process quite popular for projects running an agile methodology.

Scrum: Scrum is a variation of agile with different terminology. Azure DevOps, similarly with the agile process has terminology specific to the Scrum process.

You may question having both Agile and Scrum processes and be confused about the differences. One of the main differences that you’ll encounter is that within the Agile process, tasks can be tracked by there original estimate, remaining work as well as completed work. However, if using the scrum process, tasks can only be tracked by the task’s remaining work.

Future blogs will go into detail about each of the standard processes available within Azure DevOps.

2 thoughts on “Azure DevOps Processes: Part 1

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.