Every new project gets a SharePoint site built to your methodology.

Your PMO sets up each project methodology once in Vedetta, an app inside your SharePoint. Whenever a team starts a new project, Vedetta creates its SharePoint site from that methodology in under a minute, with the right folders, templates and guidance already in place.

How it works

Illustrated example
  1. The PMO sets up a methodology

    Once, in Vedetta: define the stages and deliverables, and add your own templates.

  2. A project lead starts a project

    Also in Vedetta: choose the methodology, name the project, and create it.

  3. Vedetta creates the project site

    A new SharePoint site with its folders, your templates copied in, and a guidance link.

Illustrated example in three steps. One: on the PMO’s SharePoint site, the PMO sets up the Technology development methodology in Vedetta, an app on that SharePoint page: three stages (Define, Develop, Launch), four deliverables with their guidance, and the PMO’s own template attached to each deliverable. Two: on the same page, Jordan, a project lead, chooses Technology development, names the project Sensor development and chooses Create project. Three: Vedetta creates Sensor development as its own SharePoint site. Its Project documents library has a folder for each stage and each deliverable, with a copy of each template in its deliverable folder, and the site’s navigation links to the methodology’s guidance.

Try the real app in your browser: it runs on a simulated SharePoint, with nothing to install.

Why it helps

Your process is written down. Each project still starts its own way.

You have defined how each kind of project should run. But every new project starts from an empty SharePoint site, and each team sets it up its own way. Some follow the process closely, others less so: a deliverable goes missing, folders don’t match, and handing a project over takes more explaining.

Today

Each project goes its own way

Three projects of the same type, set up three ways. A missing project brief here, an outdated template there.

Sensor development
  • Business case
  • Business case (2).docx
  • Misc
  • Project brief – old.docx

Outdated project brief template

Battery module
  • 1. Planning
  • Templates – Copy
  • Business case.docx

No project brief

Charging dock
  • New folder
  • Notes.docx

No deliverable folders yet

With Vedetta

Every project starts the same way

The same folders and templates in every new project of that type, from one methodology set up once.

Sensor development
  • 01 Define
  • 01 Business case
  • Business case.docx
  • 02 Project brief
  • Project brief.docx
  • 02 Develop
  • 03 Launch

Same methodology

Battery module
  • 01 Define
  • 01 Business case
  • Business case.docx
  • 02 Project brief
  • Project brief.docx
  • 02 Develop
  • 03 Launch

Same methodology

Charging dock
  • 01 Define
  • 01 Business case
  • Business case.docx
  • 02 Project brief
  • Project brief.docx
  • 02 Develop
  • 03 Launch

Same methodology

For the PMO

Your process doesn’t stop at the handbook. Each project gets what it needs to follow it, including any risk and decision logs.

For project teams

Less time building folders and looking for templates. They open the files and start.

For every new project

A consistent starting point, in the SharePoint your teams already use.

What to expect

What Vedetta does, and what stays with you.

Does Vedetta read our existing process documents?
No. You build each methodology in Vedetta, once for each type of project, working from your existing material. You attach your own template files.
Are the templates filled in for the team?
No. Each new project gets its own copies to start from. The team fills them in.
Does every project get every deliverable?
Only the ones it needs. Mark a deliverable optional, and whoever starts a project chooses whether to include it. Required deliverables are always there.
Does Vedetta make teams follow the process?
No. It gives each new project the intended starting point. How the work is done stays with the team.
What about projects that already exist?
They stay as they are. A site’s owner can connect one: Vedetta adds the missing folders and the guidance link, and leaves existing files where they are.
What happens when we change a methodology?
New projects get the change. Projects already running keep their folders and templates, and see the updated guidance through their guidance link.
Where do teams work?
In SharePoint, with ordinary folders and files, in the SharePoint they already use.
What does our IT need to do?
Add Vedetta to your SharePoint. Your Microsoft 365 administrator installs it, and we walk you through what that involves. IT & security answers the questions IT usually asks.

Bring one of your processes.

Book a walkthrough and we will show you what you would set up in Vedetta, and what a new project would receive in SharePoint.

Book a walkthrough