In the wake of increasingly complex IT architectures that are prevalent in companies, the cost to control medium and large IT projects increases disproportionately as integration, interfaces and requirements become more time consuming and non-transparent. To counter this trend requires standardized development and especially a project management methodology with defined interfaces, input and output artifacts and a best practice model. One solution is the SharePoint Project Management as a Service (SPaaS) approach, which combines the flexibility of a catalog-based approach to the security of a fixed price offer.
Your must know this checklist for leading a project to success.
This FREE eBook contains excerpts from Chapter 1 Product Kickoff from the book ‘SharePoint 2010 for Project Management 2nd Edition’. SharePoint 2010 for Project Management 2nd Edition: If you were to analyze your team’s performance on a typical project, you’d be surprised how much time is wasted on non-productive tasks. This hands-on guide shows you how… READ MORE
After spending the first 15 or so years of my career largely in Project Management roles, I’m sort of a PM junkie when it comes to books and tools and methodologies of how to move something from ideation (PM wonk term for idea creation, or initiation phase) to delivery and, ultimately, support. When Arpan Shah moved from the SharePoint product team at Microsoft over to Project Server (he’s now working on Office365), I shared some advice with him (which I’m sure he doesn’t remember): don’t try to solve too many problems at once, but simplify the tool. As I got to know Christophe Fiessinger on Arpan’s team over the past couple years, I told him the same thing. So when I met with members of the revamped Project team a couple weeks back to talk about SharePoint 2013 and roadmap for SharePoint Online and Office365, I expected to have much the same conversation.