BHG Infra

Project kinds

Advisory, Implementation and Managed service projects are run differently. Each kind has a playbook, a build product and a hand-off to the next kind.

Every project has a kind. The kind says what the project is, and it decides how Infra runs it: what counts as the baseline, how documents are read, the default phases, how health is judged, what the project builds, and how the project agent behaves. Each kind has a playbook that holds these rules.

The kind is set when you create the project. The offering (for example "Compensation Redesign") is a label within the kind.

The three kinds

AdvisoryImplementationManaged service
What it isBHG studies the client's plans or sales program and recommends changes, ending in a readout and a BRD.BHG builds the client's SPM platform to the signed BRD and takes it live.BHG runs and changes the client's live platform under an hour block and service levels.
OfferingsCompensation Redesign, SPM Assessment, Territory Optimization, Quota Setting, Change ManagementImplementation, System Implementation, Implementation EnablementManaged Service
BaselineThe SOW's deliverables and their acceptance criteriaThe SOW and the signed BRDThe SOW's hour blocks, service levels and support scope
Build productBRDBlue Accelerate blueprintBlueprint changes
Builds onNothingAn AdvisoryAn Implementation
Plan › Scope is calledDeliverablesScopeService
Items › Work is calledWorkWorkRequests
System buildNoneIts own, designed in Blue AccelerateThe Implementation's, inherited (shown as Blueprint)

Training and enablement work runs as an Implementation for now.

How documents are read on each kind

Sync reads documents differently depending on the kind:

  • Advisory: requirements come only from the SOW's acceptance criteria. Analysis workbooks and data are evidence for the findings, kept in Knowledge, not requirements. A recommendation is a decision: a question with BHG's recommendation, waiting on the client.
  • Implementation: requirements come from the BRD and requirements sessions. Plans, components, interfaces and build objects are the system build. Test cases trace to requirements; UAT defects are issues.
  • Managed service: requests, tickets and change requests are work items (tasks), never requirements. A change request names the blueprint item it changes. Hour blocks and service levels are SOW terms.

How health is judged on each kind

Health has three parts: schedule, scope and budget. Each kind reads them differently.

ScheduleScopeBudget
AdvisoryDeliverables and milestones on time.Delivered work accepted by the client; nothing waiting on review.Hours logged against planned hours.
ImplementationMilestones on time, and the project inside its end date.Every requirement traced to a deliverable, nothing waiting on review.Hours logged against planned hours.
Managed serviceRequests answered inside their service level.Change requests reviewed; nothing waiting.Hours used against the purchased hour block.

Phase templates

While a project has no milestones, Plan offers the kind's phase template: Use the Advisory phase template, Use the Implementation phase template, or Use the Managed service quarterly cycle. The template stages its default milestones on Events for review. Nothing is created until the lead approves them. Due dates count in weeks from the project start (or today, if the project has no start date).

A project whose SOW is signed gets milestones only from the signed SOW, so the template's milestones are dropped there.

Hand-offs between kinds

The kinds follow each other: Advisory → Implementation → Managed service.

Advisory to Implementation: the BRD

An Advisory's Overview shows Build product: BRD: where the BRD stands (for example "BRD v2, signed off." or "Draft 3 from Oct 12; not yet the BRD."). When there is a BRD or a draft, the project lead or an admin can click Start implementation from this BRD. This opens New project as an Implementation that builds on the Advisory, with Start from its BRD ticked. The BRD's text is copied into the new project's Knowledge and recorded as its BRD with status draft. It is never signed by the copy: the client's sign-off is recorded by a person.

See Start an implementation from an advisory BRD.

Implementation to Managed service: the blueprint

A Managed service that builds on an Implementation reads that Implementation's blueprint. Its Overview shows Blueprint from the Implementation, with a link to Blue Accelerate. A change request is a work item that names the blueprint item it changes, and the change is staged against that existing item, never a new copy.

Linked projects you cannot open

If a project builds on one you cannot open, Infra shows only its kind, for example "Builds on a project you can't open". It never shows that project's name or content.

The project agent follows the kind

The project agent gets the kind's operating instructions. On an Advisory it treats recommendations as decisions for the client. On an Implementation it checks that requirements trace to deliverables and test cases. On a Managed service it watches the hour block and says so when hours used pass 85% of it. See The project agent.

On this page