![]() ![]() Planner: while this is not a project management tool, it’s excellent for capturing operational tasks and deliverables.Again, keep it front, center and not just buried in a folder structure. If you’re using an Excel or Word document for requirements, backlog items, etc., pin it as a tab.Pin the OneNote Section Group created for this Channel (keep reading for more on this).Copy/paste them from the SOW so that they remain front, center and not buried in a bunch of text. Wiki: use this as a place to capture in and out of scope items.If appropriate, share the Deliverables folder with project members on the client side. Files: set up a folder for Project Management documents and another for Deliverables.Project Templates: Likely, these sit in a SharePoint Library somewhere on your intranet.Rules can include where meeting notes and deliverables will be stored, when to colleagues and whether weekly syncs should be recorded. ![]() ![]() Wiki: Use this as a guide state why the Team exists, why each Channel exists, who the Owners are, call out any libraries, folders or files that are shared externally and add your rules of engagement.Use this Channel to capture and store information that is true across all workstreams: If Teams is being adopted to improve productivity, avoiding sprawl should be a top priority. Too often, well-intentioned members add every Channel or Tab they think is needed without much regard to scalability and flow. In the settings for the Team, uncheck the options that allow Members to add Channels, Tabs and Apps. This structure grants your account reps and/or program managers easy visibility into their accounts and project status. For this example, we will look at the former. Depending on the security needs and complexity of your projects, you could either create a Team per client and a Channel per project, or a Team per project and a Channel per phase. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |