SharePoint Online - Project Management Aspects

SharePoint Online has some great simple project management features to be aware of:

1) It can be utilized as a central repository for project documents

2) It can be utilized to store and link to project plans (via Planner or via those created via a list)

3) It can be utilized to store calendar based information

4) It can be utilized as an issue log using out of the box list templates

5) It can be utilized for timesheet management via stored documents or created lists

6) It can be utilized to store project tasks via links to Planner, stored documents or via created lists

7) It can be utilized to store documents and make them manageable via a proper meta-tag-based strategy by type of document

7 Aspects Before Starting a SharePoint Project

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

8 Requirements for a Director of SharePoint Project Management

The following are eight requirements for a director of SharePoint project management: 

1. Accountable for managing, directing and leading the SharePoint project management team

2. Evolve and deliver SharePoint training material

3. Enlist and develop SharePoint instructors for training

4. Supply mentor advice to SharePoint project managers

5. In charge of management meetings involved with SharePoint project management

6. Establish SharePoint project management improvements

7. Bring forth positive SharePoint work relationships

8. Be strategic in SharePoint business plans, human resource planning, business analysis and business management

4 SharePoint Scheduling Standards

The following are four benefits to having scheduling standards:
1)     Uniformity in the development and implementation phase.
2)     Help identify needs between project managers and technical teams.
3)     Consistency for scheduling planning for mid-size to large projects.
4)     Documented agreement for project management purposes.

5 SharePoint Project Task Standards

The following are 5 SharePoint project task standards:

1)      Project summary – start each project schedule with a project summary line – basically a high-level item of what the project is. Example: SharePoint 2016 to SharePoint Online Migration.

2)      Phase summaries – each project has phases – so mapping them out is key. Example: definition, design, develop, deploy, maintain.

3)      Tasks and durations – list out each task in possible order it should be completed along with duration in hours/days needed for each task. If using an agile method – don’t use more then 40 hours allocated per task.

4)      Task closure – once a task is closed mark it completed as such.

5)      Dependencies of tasks – denote which task/tasks have a dependency on one another.

SharePoint - High-Level Project Aspects

SharePoint - High-Level Project Aspects

The following are the high-level aspects that make-up the reasons for a SharePoint project:

Problem – defining the problem to be solved.

Options – Think of ways that can help to improve or even solve the problem that is identified.

Experiment – Select one of the ideas from those brainstormed and apply it.

Review – Review the outcome.

SharePoint - 3 High-Level Project Planning Aspects

3 High-Level Project Planning Aspects

The following are some 3 high-level project planning aspects to utilize with any SharePoint based project:

Vision

During the vision step, the following is vetted out:

·         Scope of the project

·         Who is on the project team?

·         Who are the project sponsors?

·         What are the critical success factors of the project?

Design

The design is the phase in which the project goals and objectives, are aligned with the technical capabilities and a solution is architected.

Implementation

Implementation is the phase in which the results of the design are exercised in a development or test-based environment/site. Once tested and signed-off on then they are migrated to production to be utilized.