Building a good Share. Point team site Glyn Cloughs Blog. Recently I was lucky enough to work with a small group of business users who were experiencing Share. Point as more than a document library for the first time. Over a period of about a month we ended up growing our Share. Point 2. 01. 0 Team Site in to one of the better examples that Ive seen since working with the product from the Share. Point Portal Server 2. Share. Point 2. 00. Thinking back on this I was wondering if there was a way of packaging up the approach and techniques that had been successful so that they could be used again and again. Here are my conclusions, followed by some practical advice on things I like to see on a team site. Team Sites. First, to define a Team Site. Well, Share. Point gives us a team site template to build new sites from which includes things like a document library and discussion board but what does this translate to in the real world My view is that a team site is a collection of assets and activities that are united around a common purpose. This can cover a host of scenarios where I think a team site could be needed, e. Sharepoint 2010 Ms Project Site Template' title='Sharepoint 2010 Ms Project Site Template' />A small departmental unit who perhaps work and collaborate around the practices and processes they own within an organisation. A working group consisting of members from various organisational units and office locations forming a virtual team with a particular deliverable or purpose. A classic project team delivering a particular projects goals and aims. And no doubt many more. So, on to the areas which I think contributed to a successful team site. Ive tried to sum these up into the three areas I felt were the most important but obviously this is not intended to be definitive, or that they could apply in every case. In fact, as youll see, one of my conclusions has to be that this cannot be prescriptive The three areas 1 Purpose. For a truly successful team site there needs to exist a reason for being. This is going to be different for every team in every scenario, but common themes could be along the lines of this is where we keep the project documentation or the place to raise issues or get questions answered. I actually see this as the most important area when building a team site. Without this users will simply not return after the first couple of visits resulting in a site that falls quickly into disuse and little value. Decibel Mac Keygen more. Getting the users in, and staying in, has to be one of the key goals. Discovery. I think in the past people have tried to come up with the one size fits all team site template to second guess the users needs and present a team site that will automatically meet those needs. The more and more I work with Share. Point the more I realise that this is a pipe dream. By default, on clicking the SharePoint 2010 or SharePoint 2013 site logo It takes us to the root of the current site or subsite. But you may want to link logo to. Introduction. List validation and column validation is one of the notable feature of SharePoint 2010. We will see how we can set validation to a list and to a column. I use swagger to document my API endpoints. I like the descriptive nature, and find the swagger UI to. All the tools and features exist within Share. Point to meet the majority of a regular teams requirements, but to assume that each team will want a similar configuration of their team site is going to result in whole sections of a team site that fall into disuse, e. Instead, Ive found it a much better option to educate the users and help them to become aware of all the different features and then allow them to discover the features that work for them. Admittedly at first you may end up with the Share. Point equivalent of a kid in a pick n mix sweetshop filling their bag with every available sweet and only really liking the Haribo, but this should settle down over time with some gentle guidance and continued reflection on the success of the site. By allowing the users the freedom to build their own site in this way, not only are you helping ensure that their needs are met, but youre also creating your own band of evangelists who will make sure the team site continues to be a success long after you are gone. Flexibility. This is a key tenet for me to ensure success. Things will change. Users will swap in and out, and the world will keep spinning. Therefore its important not to put your team site up and say right, this is how were going to work from now on. Similar to the discovery piece above, let the users go down different routes and paths and see where they end up. Initially the worst thing that can happen is that the site will end up with some superfluous lists and libraries but hey, so whatThe important thing is that the site continues to evolve to meet the changing requirements and needs. It may be that the site starts out as a simple place to store project documents, but grows into the key collaboration tool to enable communication across a globally disperse team. If so, then be prepared to roll with the punches. A Solid Base. Despite my statement earlier that its simply not possible to create a standard team site template and roll it out, I do think its necessary to have some ideas in your tool box that you can suggest and try out in order to help a set of users get going with their team site. Here are a few things that I think are good conversation starters for a new team site Public and private document libraries depending on the organisation my preference is the opt out approach for visibility hence visitors to a team site should be able to see everything, apart from those things specifically locked down. Recent documents on the home page show the last 5 or 1. Add a note board in SP2. Meet the team web part a simple introduction to the core members of a team site. Calendar the difficulty here is to give this a specific purpose, so that there is no ambiguity when comparing it to individuals personal calendar, e. Useful links a simple Share. Point links list goes a long way to helping folks navigate. Team identity possibly in the form of a written introduction or an image, but something that distinguishes this site at a glance from other sites. Coming up with this identity could also tie into your user adoption strategy. Conclusion. To conclude, my belief is that to build a successful team site there are a few behaviours that can be seen as the success criteria Users returning to the site regularly. Users contributing interacting with the site regularly dependent upon size of teamThe team actively managing and adapting the site themselves. All of the above has been aimed at increasing these behaviours, and as such its about doing whatever is appropriate for the team in question. When working on a smaller scale with a specific team its possible to apply the above ideas and continuously hand hold the users to help answer their questions and listen to their ideas. A real challenge comes when looking to role out the above in an enterprise where there may be hundreds or thousands of team sites required. Thats a much harder area to look into and involves some serious attention being given to user adoption and end user training. My thoughts on that for another post perhaps. Customizing Project Site Template in Project Server 2. Think EPMMore findings I am testing using different user sign ins one as test project manager Test. PC and another as myself fcurrie set as PWA administrator. I just noticed that when I sign out as myself and sign in as Test. PC and click the project schedule from PWA to edit in MSProject, the copy of MSProject on my device is issued to fcurrie and not to Test. PC which Im thinking is causing the problem with how the Status Manager gets set maybe I also created a new project using the default EPT which does not have a project plan assigned and when I open the blank plan in MSProject, it does the same thingSo will rethink how to test this probably missing somethingLet me know if you have other ideas Best,Frances.