I utilized SharePoint when I establish the DevU website to help make a more user friendly experience for team members. We anticipate as the project grows there will be a large number of stakeholders over the life of the project, so we needed a way to keep things as easily acceptable as possible.

Within Teams, I establish spaces for files to cut down on clutter and I regularly sweep through the documents to maintain their integrity. I also keep a backup of all the key team documents in my own OneDrive.

The Team Notebook (Using OneNote) functions as a great way to maintain all meeting notes, and allows the project manager a second private section for their own notes. OneNote is one of my most frequently used tools - it's unbeatable in its flexibility for creating lists, keeping track of notes and basically keeping my desk free of a 1000 papers, post-its and notebooks.

The project charter helps document guides the agreements of all stakeholders on the project and clearly lays out our necessary OKRs and goals. This is an outline I reference for the project charter/kick off meeting.

I have utilized this Kanban style multiple times across many projects. The Planner/Tasks integration allows me to assign tasks to team members. Using Lists is another way I have managed team tasks, and when coupled with the Approvals app I can send any necessary items directly to the supervisor/gatekeeper for approval. Either method helps me track progress, and you can quickly flip from a Kanban style board to a timeline or task list,. Each of the cards also allows team members to create checklists for the task, post comments and add attachments if needed.

Another tab which functions using Lists' calendar view - a simple way to schedule all meetings, milestones and deadlines so everyone can a bird's eye view.

I often default to Excel for a Raci Matrix, but have utilized Lists (shown above) as well.

Using MS Forms, I launch stakeholder pre-project surveys and post mortem surveys right within the SharePoint site.