- Identify the problem
- Identify stake holders
- Do a enterprise needs analysis
- Define Business requirements
- Identify technologies to fulfill business requirements and Design proposed solution
- Review/approve proposed solution
- PROJECT PLAN
- Deploy proposed solution in iterations in accordance with the project plan!
Ideally these are the principles that I would like to follow, but in the real world it is seldom the case. However, I do not see why these steps cant be followed when implementing a SharePoint solution. In most cases SharePoint deployments fail because there's no Governance Board. We need more information managers, project managers and Business analysts instead of IT People on this Governance Board. Lest us not forget the Business owners and actual data users. Naturally when one mentions ECM, taxonomies are sure to be mentioned somewhere in that topic. This too, is a problem! There's no taxonomy design in place but yet Organizations want to start managing data more effectively and implement content management solutions. SharePoint is merely the technology behind ECM, hence content needs to be structured first before even thinking of implementing SharePoint...
I think I have said enough for now - otherwise I will go on forever!
It's funny how you have to force yourself to stop typing hey. :) Good and valid points raised, I agree with you, of course getting this put into practise is another story altogether. Good luck with your blogging, I think you started off great.
ReplyDeleteVeronique.