3 SharePoint Project Goals

The following are 3 goals for SharePoint projects:

1)      What is trying to be accomplished

2)      Why is what is being asked important

3)      How will the goal be best accomplished

SharePoint - Role

The following are SharePoint dictionary words of the day related to role:

Role identifier

Integer which uniquely identifies a role definition within a site or process.

 

Role type

Predefined role description.

SharePoint - Representational State Transfer (REST)

The following is a SharePoint dictionary word of the day:

Representational state transfer (REST)

Transference of XML data between processor systems. REST supports four application methods: Get, Post, Put and Delete.

8 Key SharePoint Task Management Items

The following are 8 high-level items for SharePoint task management:

1)      Define project phases

2)      Assign tasks

3)      Estimate tasks

4)      Schedule phases

5)      Review assigned work

6)      Track work status and adjust as needed

7)      Report task status

8)      Manage tasks and changes

SharePoint Decision Making

The following are some high-level decision-making items for SharePoint projects:

1)      Identify and define the problem

2)      Develop alternatives

3)      Evaluate alternatives

4)      Select alternatives

5)      Implement decisions

6)      Evaluate and control the environment

 

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.