Writings and ramblings on SharePoint for those who are addicted to it!
The following are six key SharePoint project product realization keys:
1) Define and execute production activities.
2) Generate and manage requirements for all needs aspects.
3) Utilize effectively the differences between verification testing and validation testing.
4) Consider all customer, stakeholder and technical requirements.
5) Analyze potential incompatibilities as early as possible.
6) Understand and analyze test data for trends and anomalies.
The following are the top seven core and key items when closing out a SharePoint project:
1) Document the project and supporting processes
2) Document the lessons learned
3) Create a final management level report of the project (includes all needed overview aspects and metrics)
4) Archive any needed data
5) Have one last technical review of all needed aspects and how they work
6) Document all technical activities
7) Document and have final report of success criteria, support model and ideal usage
The following are ten serious risk factors that will effect a SharePoint project:
1) Having inaccurate metrics
2) Having inadequate measurements
3) Having schedule-based pressure
4) Having management issues
5) Having inaccurate cost estimates
6) Having the need to have everything perfect before launching
7) Having a creep in user requirements
8) Having low quality content and code
9) Having low productivity from core team members
10) Having the project cancelled
The following are three key and core SharePoint stakeholder and key personnel aspects for a project:
1) List and define the individuals and organizations involved in the SharePoint project.
2) List individuals and organizations roles in regard to the SharePoint project execution.
3) List all of the high-level tasks assigned to the key personnel for the SharePoint project.
The following are key aspects for a SharePoint scope for a project:
1) Define the scope of the SharePoint project
2) Define what is not in the SharePoint scope for the project
3) List the detailed SharePoint service level requirements
4) List the SharePoint resources, expected dates and high-level tasks
The following are seven core and key aspects to clarify before starting a SharePoint project:
1) Know the purpose and justification for the SharePoint project
2) Know the measurable objectives for the SharePoint project
3) Know the deliverables of the SharePoint project
4) Know the acceptance criteria of the SharePoint project
5) Know the critical success factors of the SharePoint project
6) Know the constraints and assumptions of the SharePoint project
7) Know the proposed budget and scheduled goals of the SharePoint project
These aspects maybe good as a typical structure for a SharePoint consulting project plan:
1) SharePoint objectives, scope, and budget
2) SharePoint organization and management
3) SharePoint project schedule
4) SharePoint communication and collaboration
5) SharePoint documentation
6) SharePoint risk management and contingencies
7) SharePoint project closure
The following are some aspects that a SharePoint project manager should report on in regard to their project weekly:
• Overview on the status of the SharePoint project
• Amount of money and other resources spent vs. approved budget for the SharePoint project
• Time that was spent vs. scheduled for the SharePoint project
• Results vs. requirements for the SharePoint project
• Project risk and management issues that should be known for the SharePoint project
• Project health and overall standing of the SharePoint project
The following are seven key items that a short SharePoint project proposal should contain:
1. Background and scope of what will be obtained with SharePoint
2. Goals and results of the SharePoint project
3. Staffing in regard of the SharePoint project
4. Work plan of the SharePoint project with high-level tasks
5. Budget and fees of the SharePoint project
6. Other provisions of the SharePoint project
7. Schedule of the SharePoint project
Clarify the following with the relevant stakeholders and team when starting a SharePoint project:
1) Purpose and justification.
2) Measurable objectives.
3) Deliverables.
4) Acceptance criteria.
5) Critical success factors.
6) Constraints and assumptions.
7) Proposed budget and schedule goals.
Real working thought:
It’s important to have a realistic scope in regard to what a SharePoint project will encompass and output. I've been a member of a few projects where the scope was not realistic and on one occasion needed new technology to be built until the proper outcome could be met. This therefore led to potential cost overruns in the budget.
The following are 6 key points to consider for a SharePoint project:
