Utarbeidet med KI.
A good work plan is detailed enough to guide the work and high-level enough to be maintained. Here is the approach that strikes that balance, based on the estimate from the sales phase.
Start at a high level: three to six phases that reflect how you actually deliver. The phases are what management and the customer track, so they should be recognizable without explanation.
Aim for tasks that take anywhere from a few days to a couple of weeks. Shorter tasks result in a plan that no one can be bothered to update; longer tasks result in a plan that does not reveal deviations until it is too late.
Plan using roles—senior consultant, developer, architect—not individuals. This allows the plan to be priced and staffed independently of who happens to be available, and ensures it can withstand someone falling ill or switching projects.
Only mark dependencies that are genuine—where task B cannot start until A is complete. A plan full of artificial dependencies becomes rigid, and every delay ripples through the entire timeline for no reason.
Once the plan is complete, add up the hours and compare them with what you sold. If there is a discrepancy, it is better to know now than in week six. This is often the most uncomfortable and most valuable step in the entire exercise.
A plan that isn't updated is a historical record. Set a regular time—for example, every Friday—and stick to it. Fifteen minutes a week is enough, and that's the difference between a plan that guides and one that's just for show.
Still et spørsmål eller del hva som hjalp deg.
Publisert 27.1.2026
ProsessPilotene er blant de første selskapene i Norge som er oppført på Microsoft FastTrack Portfolio Partners List - et kvalitetsstempel til leverandører som leverer komplekse Dynamics 365-prosjekter etter dokumentert beste praksis.
Les merHar du et spørsmål eller en erfaring å dele?
Bli den første som bidrar.
