Hi Community
After building a business case for SP2013 , my next tasks to ensure I capture the business requirements across the various departments without the need to product reams of documentation ( which nobody reads anyway!}
My cunning plan (!) is to get the Home site and department template requirements documented ensuring they meet overall corporate aims that are well documented. Keep a Governance Doc running on going, to ensure I am covering my bases ( sat though John T’s suguk presentation to put the fear of god in me on that one)
I have started uploading a set of project documents into a old SP2010 site some are initial draf others I would like some advice on:
- Requirements for Home and Dept Site templates inc Wireframe modelling: Requirements analysis kit for SharePoint 2010 collaboration site templates. I haven’t done my wireframes and thinking of trying Balsamiq but would be interested in the opinions of others inc Balsamiq community support for SharePoint 2013 design: http://flucidity.azurewebsites.net/2013/02/sharepoint-2013-balsamiq-mock-up-template/
- A worksheet listing: Site columns, content type and any parent content types, views. separate sheet for the terms. Educating my users to edit this themselves with some guidance
- TODO: a template for user stories / tests …
- TODO: Scrum / Project man lite tool: Something like https://www.kanbanpad.com/ .( we haven;t the TFS visualiser before someone mentions this.)
- TODO: Support / dev tasks management probably do this in SharePoint lists / project site template as no TFS
I am trying to avoid downloading and playing with unnecessary tools, just the ones that will really help me meet my deadlines.
Daniel
Paul
I stood up the client’s brand new SharePoint 2013 farm on Thursday morning, using the awesome AutoSPInstaller – all looking good . I have a meeting today to sort out the Site collections verses sites and forward looking zone for my apps domain.
I like that task management App. I will give it a try and see If I can tailor it to
- apply categories to tasks – bug or requirements
- link tasks under a id so testing task may be linked a a requirement
- group tasks with a release.
Mark’s suggestion is good but want to get the users focused on only on SharePoint so they adopt it with even know they are doing it 😉
