Item: Azure DevOps Services
Rating: 8
Author: Chris Studebaker

Overall Satisfaction with Azure DevOps Services

Use Cases and Deployment Scope

We use Azure DevOps to coordinate our implementation of development changes and technical processes (configurations / setups) for Business Central. First we create a master document listing all the modifications / extensions from a functional standpoint (master), then have individual tasks with tech design and hours assigned. Each time code with Git is sync'd and merged between one or more developers for the monolith extension app, it is tracked with the task assigned. Finally, as each task is worked through the status is updated and sync'd with the time keeping system (F&O) with PowerAutomate. This gives insight into the progress vs. hours consumed vs. original estimate in real time.

Pros and Cons

Pros

Utilize Git as a repository to share work between multiple users
Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
Track status of each task
Integrate with Git to utilize branches, merging, approvals, history, etc.

Cons

Have better project management to also be used with functional implementation rather than just development
Have the ability to integrate with a customer facing interface to give visibility into the project status and components.
Smoother integration into time keeping systems such as F&O or Business Central for overall project management reporting / accounting

Return on Investment

Allows us to have multiple developers workflow seamlessly
Allows for code validation / testing at each deployment
Track progress for individual tasks real time.

Usability

It has great flexibility and breadth of features, but it is very poorly documented. Like all really complex architectures, there needs to be expert staff on hand to make the most out of it and to support others. It is born of a specific need (VS Code Framework) and is slowly evolving into a more generic product but is missing features found in more horizontal packages such as screen capture testing, general project management, and reporting features for management / customers.

Alternatives Considered

Atlassian Jira

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Key Insights

Do you think Azure DevOps Services delivers good value for the price?

Yes

Are you happy with Azure DevOps Services's feature set?

Yes

Did Azure DevOps Services live up to sales and marketing promises?

Yes

Did implementation of Azure DevOps Services go as expected?

Yes

Would you buy Azure DevOps Services again?

Yes

Other Software Used

Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Marketing, Microsoft Dynamics 365 Finance

Likelihood to Recommend

DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.

Comments

Please log in to join the conversation

DevOps helps our dev team coordinate deploy and saves us money