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.

Automation | Article
OpenAI’s Data agent could investigate company data and build shareable interactive dashboards. Access controls and source trails needed to follow analysis and action through the workflow.

Project management | Event
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.

Automation | Article
Power BI reports and semantic models became grounding in Copilot Chat and Cowork. Shared chats, synced notebooks and Planner status connected analysis with collaboration.

Project management | Article
Copilot Notebooks and Cowork gained more ways to share project context. Agent metrics and cost controls expanded in the admin centre.

Automation | Article
Copilot administrators gained central controls for consumption-based cost. Purview controls extended to Cowork, and agent metrics could connect with organisational context.

Project management | Article
Federated connectors could retrieve live SaaS data through MCP. Copilot Notebooks gathered project context while Word and Teams gained collaboration features.
Do you have a question or experience to share?
Be the first to contribute.