Microsoft Project Server Issues around a successful implementation

1
Microsoft Project Server Issues around a
successful implementation

• Dirk Lupien, PMP, MCTS
• dlconsulting_at_swbell.net
• 636-734-1044

2
Why move to an enterprise system

• Able to see resource conflicts
• Team enters their own time
• Reports continually updated
• Less time spent by PM creating reports
• Ability to drill down
• Management can review at any time

3
Is your organization ready for the change

• Do you have processes?
• Are they followed and do they work?
• Is there executive support?
• Does your organization do change well?
• What are the expected timelines and scope of the
  implementation

4
Questions to ask

• Do we have the technical expertise?
• What is our migration window?
• What are we doing with the existing projects and
  workspaces?
• Do we have customization? Where?
• Do we have the right mix of roles, number of
  users?
• Do we have any SRS reports, InfoPath forms or
  Microsoft Project macros?

5
Questions - cont

• Do we have a test environment for the migration?
• How will we train?
• What do we want to capture that we currently
  arent?

6
Getting buy-in

• Change your words to match what the audience
  understands
• Manage the implementation so the users can absorb
  the changes
• Plan the training hands-on
• Walk before you run
• Emphasize the value of the tool/process on being
  more successful
• Management support must be visible
• Seek input from user community on needs

7
Not an upgrade but a migration

• Moving from Project Server 2003 to Project Server
  2007 is a migration, not an upgrade.
• Different platform
• Different data structure
• Built on Windows SharePoint Services 3.0 so all
  SharePoint features are available.

8
Differences between versions

• Windows SharePoint Services (WSS 2.0) Optional
• Project Professional 2003
• Project Web Access
• SQL Server 2000 or 2005
• Microsoft office 2003

• WSS 3.0 required
• Project Professional 2007
• Project Web Access
• SQL Server 2000 or 2005
• Microsoft Office 2003 or 2007

• Project Server 2003

• Microsoft Office Project Server 2007 (MOPS)

9
Differences between versions (cont)

• 1 data analysis cube
• 1 database
• 1 undo step

• 14 data analysis cubes
• 4 databases
• Draft
• Published
• Archive
• Reports
• Unlimited undos (99)
• 3d Gantt charts
• Change highlights
• Visual reports

• Project Server 2003

• Microsoft Office Project Server 2007 (MOPS)

10
New features
11
Time reporting

• 2 step process
• Task status updates
• Timesheet (non-project time)
• Can control process and make Timesheet master

12
Resource Types

• Work labor, can be generic or named
• Material use of raw materials concrete,
  laptops, etc.
• Cost value is different for each usage travel,
  training, etc.

13
Booking types

• Committed definitely assigned to the project
• Proposed used for planning purposes. If you
  dont change from proposed to committed the tasks
  will not appear on the resources task sheet.
• Booking type is defaulted when the resource is
  created.

14
Project Types

• Enterprise Projects
• Proposals used for planning can become a full
  project
• Activities used for personal type projects
  does not require a Project Professional license.
  Can become a full project

15
Project development cycle

• Create a project using Project Professional while
  connected to the server. Project is stored in
  the draft data base and has no visibility in
  Project Center
• Create project team
• Assign resources to tasks

16
Project development cycle - cont

• When project plan is completed, project can be
  Published now visible to all authorized
  personnel via Project Center. E-mail
  notifications are sent out.
• All updates/changes are done on Draft copy and
  are not visible until posted.

17
The formula
18
Demonstration
19
Thank you

• Dirk Lupien, PMP MCTS
• dlconsulting_at_swbell.net
• 636 734-1044