Kartic's Musings on Corporate Information and Knowledge Management

July 2, 2008

SharePoint Projects – Success Criterias

Filed under: SharePoint — Tags: , — kartickapur @ 1:09 am

I have been engaged with some very successful SharePoint Projects and can proudly say that project managers I have worked with, adhered to most of the aspects mentioned by Adam in his post below: 10 Steps To Effective SharePoint Project Management

His other strong views on relevance of Project Management in successful SharePoint project are mentioned here: Why SharePoint Projects Fail

Ofcourse, as senior developer who has been involved with various sharepoint projects, Adam gives a biased view from developer’s perspective. I would be glad to hear from Business Analysis and Project Management perspective.

Although, I agree that Project Manager has the biggest part to play in the success of the projects, I would also like to put forward other criteria for successful project:

1. Business Analysis – Requirements, probably the most misused word in our industry — rarely describe anything that is truly required. Nearly everything is negotiable. I can never emphasise the importance of requirements management enough.

2. Developers – Importance of involvement of Solution architects and delivery team in the planning stage is often overlooked. This results in lack of Ownership of the project amongst the developers. This is a formula for disaster.

3. Key Success Criterias – Metrics and measures for software products have no atomic units. Economic performance more typical in service industries (value as observed by the users vs. cost of production) has proven to be the best measure of success. Most aspects of quality are very subjective, such as maintainability, reliability, and usability. There is often less than satisfactory emphasis on ‘Key Success Criterias’ during the implementation stage. To wait for it until the testing stage normally spells disaster and tremendous frustration for the development team. Every team member should measure the Requirements, Solution Design, Code and Test Cases against the Success Criterias.

4. Quality control: Testing of demonstrable releases is a first-class, full life-cycle activity. As opposed to a subordinate, later life-cycle activity.

Project Management again – One reason for the low success rate of software-intensive projects is that traditional project management approaches do not encourage the steering and adjustment needed to reconcile significant levels of uncertainty in:

  • The problem space (what the user really wants or needs)
  • The solution space (what architecture and technology mix is most appropriate)
  • The planning space (cost and time constraints, team composition and productivity, stakeholder communication, incremental result sequences, etc.)

Here is the summary of 10 success criterias for any software project:
1. User Involvement
2. Executive Management Support
3. Clear Statement of Requirements
4. Proper Planning
5. Realistic Expectations
6. Smaller Project Milestones
7. Competent Staff
8. Ownership
9. Clear Vision & Objectives
10. Hard-Working, Focused Staff

I am sure there are dozens of more success criterias. Feel free to leave comments.


Blog at WordPress.com.