Q:chi

Deployment Timeline

This is a typical example of a Q:chi deployment timeline.

2-4

weeks

Definition of Objectives and Behaviours

Click to toggle

Define core business objectives and reporting requirements

Identify users, types and responsibilities

Identify division of users, budgets, functions

Define processes, workflow

2-4

weeks

Map Q:chi Configurations

Click to toggle

Maps budget Divisions, Financial Periods and Codes

Map Form Fields, logic and Controls

Define Dashboard Layout, Prompts, Emails, Alerts and Resources

Define User Members, Teams and Hierarchies

2-8

weeks

Q:chi build and UAT

Click to toggle

Build-out Hosting, Security and Q:chi Configurations

Build-out Forms, Documentations and Videos

Build-out SSO, Dashboard and Systems Integration

Q:chi/Client UAT with Agile Scrum Iteration

2-4

weeks

Q:chi Deployment

Click to toggle

Q:chi client site launch internal communications

Team training and guidance

Soft launch with any Scrum iteration

Launch financial period with active controls

Ongoing

Support & Review

Click to toggle

Track against milestones

Review uptake and usage

Identify issues and challenges

Plan and schedule any adjustments

Q:chi planning & spend control, approvals, reports & integrations.

Deployment Timeline

TRUSTED BY GLOBAL ENTERPRISE MARKETING TEAMS

I’d be lost without Q:chi. I’d have to hire another team of people to be able to operate anywhere near as effectively.

Deployment Timeline

TRUSTED BY GLOBAL ENTERPRISE MARKETING TEAMS

I’d be lost without Q:chi. I’d have to hire another team of people to be able to operate anywhere near as effectively.

Q:chi planning, spend control, approvals, reports & integrations.

Before you go...