Home

SharePoint project sites vs PWA project sites

%3CLINGO-SUB%20id%3D%22lingo-sub-21021%22%20slang%3D%22en-US%22%3ESharePoint%20project%20sites%20vs%20PWA%20project%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-21021%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20large%20number%20of%20existing%20project%20sites%20in%20SharePoint%20and%20now%20would%20like%20to%20manage%20those%20projects%20in%20Project%20Online.%26nbsp%3B%20We%20see%20that%20we%20can%20add%20the%20SharePoint%20project%26nbsp%3Bsite%20to%20PWA%20and%20then%20Activate%20it%20to%20manage%20the%20tasks%20via%20PWA.%26nbsp%3B%20We%20are%20trying%20to%20decide%20whether%20to%20continue%20in%20this%20mode%20or%20to%20create%20future%20projects%20in%20PWA%20and%20use%20the%20PWA%20project%20site%20for%20future%20projects.%26nbsp%3B%20Would%20like%20some%20input%20on%20which%20approach%20would%20be%20most%26nbsp%3Bbeneficial%20from%20a%20Portfolio%20and%20Resource%20(Engagement)%20Management%20perpective%20across%20projects%2C%20or%20whether%20the%20location%20of%20the%20project%20site%20really%20matters%3A%201)%20All%20project%20sites%20within%20PWA%202)%20All%20project%20sites%20wihthin%20SharePoint%20Online%203)%20Hybrid%20-%20SharePoint%20for%20older%20projects%2C%20PWA%20sites%20for%20new%20projects%20going%20forward.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-22945%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20project%20sites%20vs%20PWA%20project%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-22945%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Drew%2C%3C%2FP%3E%3CP%3EFrom%20a%20portfolio%20view%2C%20of%20course%2C%20I%20would%20recommend%20to%20include%20all%20active%20projects%20that%20have%20active%20resource%20engagements%20in%20Project%20Online%20to%20have%20a%20complete%20overview.%20So%20you%20can%20already%20exclude%20projects%20that%20are%20inactive%20or%20already%20closed.%3C%2FP%3E%3CP%3ENow%20comes%20the%20technical%20part%3A%3C%2FP%3E%3CUL%3E%3CLI%3EIn%20Project%20Online%2C%20from%20a%20support%20perspective%2C%20all%20project%20sites%20need%20to%20reside%20in%20the%20same%20site%20collection%20as%20the%20PWA%20instance.%20So%20you%20might%20have%20to%20move%20your%20%22SharePoint-based%20sites%22%20first%20to%20a%20single%20site%20collection%2C%20if%20they%20are%20dispersed%20and%20you%20want%20to%20integrate%20them.%3C%2FLI%3E%3CLI%3ETo%20manage%20your%20portfolio%20and%20resource%20engagements%2C%20a%20project%20site%20is%20not%20required.%20But%20it%20helps%20if%20you%20want%20to%20aggregate%20risks%2C%20issues%20and%20other%20SharePoint%20data%20for%20your%20portfolio%20reports.%20On%20top%2C%20you%20provide%20your%20users%20a%20single%20entry%20point%20to%20find%20their%20project%20documentation%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20hope%20this%20helps%20you%20going%20further.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Drew Van Houten
Occasional Contributor

We have a large number of existing project sites in SharePoint and now would like to manage those projects in Project Online.  We see that we can add the SharePoint project site to PWA and then Activate it to manage the tasks via PWA.  We are trying to decide whether to continue in this mode or to create future projects in PWA and use the PWA project site for future projects.  Would like some input on which approach would be most beneficial from a Portfolio and Resource (Engagement) Management perpective across projects, or whether the location of the project site really matters: 1) All project sites within PWA 2) All project sites wihthin SharePoint Online 3) Hybrid - SharePoint for older projects, PWA sites for new projects going forward.

1 Reply

Hi Drew,

From a portfolio view, of course, I would recommend to include all active projects that have active resource engagements in Project Online to have a complete overview. So you can already exclude projects that are inactive or already closed.

Now comes the technical part:

  • In Project Online, from a support perspective, all project sites need to reside in the same site collection as the PWA instance. So you might have to move your "SharePoint-based sites" first to a single site collection, if they are dispersed and you want to integrate them.
  • To manage your portfolio and resource engagements, a project site is not required. But it helps if you want to aggregate risks, issues and other SharePoint data for your portfolio reports. On top, you provide your users a single entry point to find their project documentation

I hope this helps you going further.