“Cinderella, dressed in yella Went upstairs to present her charter With multiple teams, had to add scope How many requirements (for her SharePoint 2010 Records Governance Plan) were eventually wrote?
SharePoint Training Session(S) Before any go-live of a new SharePoint 2010 platform or future SharePoint release, you first have to ensure successful training as well as identification of Power Users \ Super Users
When you think about using a technology platform like SharePoint to facilitate the management of things like strategic planning and the project management process, there are a few different levels to consider: 1
It happened again this weekend while presenting my session 'How SharePoint 2010 Stacks up to Your End User Social Media Requirements' at the 3rd annual SharePoint Saturday Los Angeles event
SharePoint 2010 can provide a relatively simple way to track and manage project schedules, deliverables, and collaboration. Now, this is not meant to be a SharePoint commercial, and indeed there are a number of other solutions that can do this as well. I picked SharePoint for two reasons: it's probably already in use at your organization, and we have a course on how to use SharePoint as a collaboration platform
Unlike the waterfall approach , which stresses strict adherence to project plans, the agile method focuses primarily on adjusting to iterative change once a project is underway. This fluid approach to completing work, however, does not mean that agile proponents should throw upfront planning out the window. Strategic planning at the outset ensures that the right tasks get plucked from the backlog and assigned to the team. When it comes to strategic technology planning, I must say that I was impressed by MaineGeneral Health ’s presentation at HIMSS
I was reading Daniel Antion's post entitled Make SharePoint Simple , which made me think about my own transition into the topic of SharePoint productivity this past year. In his article, Dan shares some experience he's had recently with customers and students who are beginning to use SharePoint, and the feedback he has received consistently is that "SharePoint is too complicated
Increasingly, SharePoint has become a platform for change management. While few companies have yet to embrace Project Server, many companies have built out their own project management utilities on the platform, and gravitated toward the out of the box templates in SharePoint 2010 (I expect to see big improvements here in the next version of SharePoint, if not through partner solutions)
In presentations on migration and planning best practices for SharePoint, I often remark that every new SharePoint project begins as a Business Analyst activity. What is the role of the Business Analyst, and how does it fit into a successful SharePoint strategy?
I believe that the BA role is critical for any successful deployment of any type of ECM (in addition to Sharepoint)
I've given a number of presentations of late on the idea of building productivity into SharePoint planning, always beginning my talk with a short history lesson in collaborative tools and platforms