October 20, 2010

Been asked a lot for a Project Planning Template in Microsoft Project format (versions below) showing the flow of a SharePoint 2010 / 2013 / 2016 implementation, so I’ve crafted a format you can use. I’ve purposely made it generic, so you can modify and detail the relevant tasks associated with your implementation of SharePoint and its version.

Note – this template bears no direct relationship to any implementations I have managed, neither do the people assigned directly match and I would strongly suggest that you review the plan with the client to ensure their requirements are encapsulated.

Project 2007 version:  Project 2007 Version

Project 2010 version: Project 2010 Version

Project 2016 version: Project 2016 Version

Of course, this template works in close conjunction with my books: Managing and Implementing Microsoft SharePoint 2010 Projects and Microsoft SharePoint 2013 Planning for Adoption and Governance.

You May Also Like…

SharePoint Copilot Governance and Beekeeping: A Buzz-Worthy Comparison

SharePoint Copilot Governance and Beekeeping: A Buzz-Worthy Comparison

🐝 SharePoint CoPilot Governance and Beekeeping: A Buzz-Worthy Comparison. In the world of digital collaboration, SharePoint is the hive—teeming with activity, rich with resources, and vital to collaboration. But just like a real hive, it doesn’t thrive on chaos. That’s where governance comes in. And oddly enough, the best way to understand SharePoint governance might just be… beekeeping.

Thoughtless SharePoint Site Provisioning: The Hidden Cost of Convenience

Thoughtless SharePoint Site Provisioning: The Hidden Cost of Convenience

In the age of rapid collaboration and cloud-first strategies, provisioning SharePoint sites has never been easier. But with great power comes great potential for chaos. When sites are created without proper analysis, planning, or governance, companies often find themselves buried under a mountain of sprawl, broken workflows, and compliance nightmares.