DevOps helps our dev team coordinate deploy and saves us money
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
- 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
Alternatives Considered
Atlassian Jira
Other Software Used
Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Marketing, Microsoft Dynamics 365 Finance
