Writings and ramblings on SharePoint for those who are addicted to it!
The following are the key high-level aspects to be aware of when moving to a SharePoint environment:
1) Explain why such a change is needed
2) Communicate the benefits of the environment change to SharePoint
3) Manage end users concerns about the SharePoint environment
4) Provide the needed SharePoint resources for learning the environment
5) Reward those that are part of the SharePoint environment success
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
These aspects maybe good to include in a consulting project plan:
1) What are the outcomes of the SharePoint project?
2) What SharePoint actions need to be done?
3) What is the schedule for the SharePoint actions?
4) Who is going to implement the SharePoint actions?
5) What SharePoint resources and tools are required?
6) What are the risks of the SharePoint project and how will they be managed?
7) What's not included in the SharePoint project?
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
While working in SharePoint, it's important to have a sponsor to help with the following:
• Making sure that the SharePoint project is evangelized as important to the organization
• Helping avoid SharePoint project scope creep
• Providing cross-organizational SharePoint support and resources
• Speeding up core and key SharePoint decisions
The following are six high-levels aspects to adhere to for any of your SharePoint projects:
1) Preparation - agree on a approved SharePoint project plan
2) Requirements and readiness analysis - agree with customer on SharePoint process based requirements
3) Analysis - review how work is done today with how work can work in the future
4) Improvement design - agree on new improved SharePoint process
5) Rapid implementation - use an Agile process to deploy SharePoint solution
6) Evaluation and decision on the next phase - plan for the next needed SharePoint tasks
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
