A good estimate for a DevOps task requires considering several factors, not just the development time itself. Use this approach when creating a new task, and always involve the person who will carry out the work.
Clearly describe what the task is intended to accomplish so that the estimate can be based on a specific scope.
Include the time it takes to design and define the requirements for the task, not just the development itself.
Estimate how long it will take to complete the task.
Allow time to test the task, document the work, and update training materials if necessary.
Include time to lead the work, deploy it to production, and attend the necessary meetings.
At a minimum, assess the estimated work and the risks involved in the task, and discuss the key figures openly with the customer, as they affect the price.
If the task does not have approved parameters in the work package, a change notification must be submitted before work begins.
Add the estimate to the task along with the category and owner, so that it is visible to the entire project team.
Update the remaining work continuously, and notify the project manager as soon as a deviation of more than 10% from the estimate becomes apparent.
Once the task has been completed, it is handed over to the test team, which tests the work and either approves or rejects it.
Ask a question or share what helped you.
Published 1/27/2026
ProsessPilotene is among the first companies in Norway to be included on the Microsoft FastTrack Portfolio Partners List—a mark of quality awarded to providers that deliver complex Dynamics 365 projects in accordance with documented best practices.
Read more
Published 9/29/2025
Jets Group was looking to modernize its business systems and planned to start with ERP. Along the way, it became clear that the foundation for growth lay not in the technology, but in understanding and improving customer processes.
Read moreDo you have a question or experience to share?
Be the first to contribute.