Created with AI.
Use this routine when taking responsibility for a work package. Make expectations, progress and exceptions understandable to the project manager and colleagues, using Project Operations where relevant.
Continue in the business-area learning path
Describe the outcome and how the recipient will verify it. Agree assumptions, boundaries and acceptance ownership. An activity such as 'work on the report' is not a sufficient deliverable.
Record: recipient / deliverable / acceptance criteria / dependencies / deadline. Ask the recipient to confirm that the criteria demonstrate the need is met.
Break uncertain work into smaller parts and record estimate assumptions. Check dependencies and capacity before promising a date. Include verification and documentation as work.
Create an initial estimate and identify what investigation would improve it. A justified range can be more useful than one unsupported number.
Update what is ready, what remains and what blocks you. Record actual work following project routines and update remaining effort separately. Time spent does not show how close the deliverable is to completion.
Use: completed / remaining / risk / decision needed. Avoid reporting '90 percent' for several weeks without explanation.
When a customer asks for something new, assess the impact and raise it with the project manager. Distinguish clarification within agreed work from changed scope. Do not commit the project to extra work or dates without authority.
Practice case: A new export needs six hours and displaces testing. Present alternatives and consequences to the project manager; do not hide the effort under the original task.
Demonstrate the result against criteria. Explain usage, limitations and open items. Agree acceptance and ownership of further work. Remaining risks must accompany the deliverable.
A useful handover lets a colleague use or verify the result without you present. Ask them to test the explanation and correct gaps.
The working routines and fictional examples above are ProsessPilotene learning material. Use the official product documentation below for product context; availability depends on your organisation's setup.
Ask a question or share what helped you.
Use this routine when taking responsibility for a work package. Make expectations, progress and exceptions understandable to the project manager and colleagues, using Project Operations where relevant.
Power BI reports and semantic models became grounding in Copilot Chat and Cowork. Shared chats, synced notebooks and Planner status connected analysis with collaboration.
Copilot Notebooks and Cowork gained more ways to share project context. Agent metrics and cost controls expanded in the admin centre.
Copilot administrators gained central controls for consumption-based cost. Purview controls extended to Cowork, and agent metrics could connect with organisational context.
Federated connectors could retrieve live SaaS data through MCP. Copilot Notebooks gathered project context while Word and Teams gained collaboration features.
Microsoft published April news for manufacturing, Power Platform, Planner and Power BI. Together, the releases show how automation and analytics can support field work when project accountability, data quality and human control are clear.
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.
A user story describes a need from the end user's perspective, using simple, non-technical language. Use this approach when describing a new feature in DevOps so that the team understands why they are building it, what they are building, and the value it creates.
A task describes in technical terms how a user story should be implemented and does not need to be explained from a user perspective. Use this approach when a user story is set to “ready” and needs to be broken down into actionable tasks.
Acceptance testing is often the final quality check before a delivery is approved, where end users test the system against the customer's requirements. Use this approach in the final phase of a delivery, or earlier in the project to identify risks along the way.
Do you have a question or experience to share?
Be the first to contribute.