Microsoft project methodology in 6 steps

Frequently asked questions

Frequently asked questions about our method.

Another question? Write to us.

• Do the six steps apply to a small engagement?

  Yes, in a lighter version. On a 20-hour engagement, assessment and planning fit into one meeting and a one-page document. What stays constant, whatever the size: the documentation delivered at the end, and the fact that you own it.

• How long does the assessment step take?

  One to two weeks for an environment under 200 users, three to four for a multi-site organization. It produces a quantified picture of the current state and a priority list: deliverables that belong to you, whatever comes next.

• Who runs the project day to day?

  A named io4 project lead, plus the technical specialists brought in. You get a single point of contact for progress and budget, and direct access to the experts on technical questions.

• What tracking tools do you use?

  Microsoft Project for the schedule, Azure DevOps for technical tracking, Teams for day-to-day collaboration, SharePoint for documentation. Follow-up is weekly by default, with a governance review each quarter on recurring engagements.

• What does the delivered documentation contain?

  The target architecture, the configuration decisions and the reasoning behind them, the operating procedures, and the access. The goal: your team, or any other provider, takes over the environment with full autonomy.

• Do you train our teams at the end of the project?

  Yes, that is the fifth step. Training is built per persona: leadership, IT, end users. Each audience gets a session tailored to its questions and the time it has available.