Project Server 2010 provides an overview of Project Server and Project Web App (PWA) for managing projects. It allows sharing project plans across a team using a shared database rather than individual files. Project Server integrates with SharePoint for collaboration features. PWA allows viewing and basic editing of projects through a browser. Project Professional provides full project management capabilities from the desktop. The document discusses using Project Server with the IEE Project Plan strategy of single-owner plans, master plans, and cross-project dependencies to improve project management.

1. GLOBAL SOFTWARE
Project Server 2010 Overview with Project Web App
January 2013

2. INTRODUCTION
» Purpose: Overview of Project Server and Project Plan Model
» Part 1: Project Plans; and Part 2: SharePoint
» How does this relate to you?
» Agenda
• Overview of Project Server
• PWA Environment
• Project Professional Environment
• IEE Project Plan Model
• Future Plans

3. OVERVIEW
» Project Server vs. MS Project
• Database vs. file
• Connect through SharePoint or Project Professional
• Enterprise resource pool
• SharePoint infrastructure
- Excel Services
- Visio Services
- Lists & Document Libraries
- Dashboards
- Performance Scoring

4. OVERVIEW
» Requirements
• MS Project Professional to connect from desktop
• PWA license to connect through SharePoint

5. OVERVIEW
» Architecture

6. PROJECT WEB APP
» PWA Environment
• Start Page
• Project Center
• Ribbon
» Limitations
• Editing master projects is not supported
• Non-standard calendars aren't supported
• Spaces (blank tasks) aren't supported
• Closing browser does not check-in projects
» Recommendation: use Project Pro to edit your projects

7. PROJECT WEB APP
» Editing in PWA
1
2
3

8. PROJECT WEB APP
» Closing in PWA
1
2
3
4

9. PROJECT PROFESSIONAL
» Connecting with Project Professional

10. PROJECT PROFESSIONAL
» New IEE Project in Project
Professional
» Template includes
SharePoint layout for IEE

11. PROJECT PROFESSIONAL
» Closing in Project Professional

12. IEE PROJECT PLAN STRATEGY
» Project and Release Plan Model
» Resource Planning
» Baselines

13. PROJECT AND RELEASE PLAN MODEL
» Project and Sub-Project Strategy
» Single-owner/single-discipline plans
» Master Plans for project managers and release managers
» Cross project dependencies (linked tasks)
Project and Sub-Project

14. PROJECT AND RELEASE PLAN MODEL
» Project and Sub-project Strategy
• Benefits
- Single-owner plans
- Reduce or eliminate check-out conflicts
- Reduce multiplication of task entries
- Consolidates reporting at each level
Project and Sub-Project

15. PROJECT AND RELEASE PLAN MODEL
» Single-owner/single-discipline plans
• One owner of each plan
• Dev, QA and Doc plans remain separate but share dependencies at
higher level
» Master plans consolidate release project plans into larger objectives
» Master plans create task dependencies (e.g., finish to start
predecessors)
Project and Sub-Project

16. PROJECT AND RELEASE PLAN MODEL
Detailed Level
Project Plan
Owner: R&D Mgr
Project Plan (Department
Level)
Owner: R&D or Proj Mgr
Project Master Plan
(Release Plan)
Owner: Release Manager
Project / Sub-Project Relationship

17. RESOURCE PLANNING
Resource Pool

18. RESOURCE PLANNING
Resource Pool

19. RESOURCE PLANNING
» Other resource tools:
• Resource Leveling
• Substituting

20. PROJECT BASELINES
» Snapshot current project plan
» Snapshot plan at different stages of the project
» Run comparison reports between original plan and actual performance

21. UPCOMING
» Do we have the need for detailed training?
» Request licensing for project leads
» Request administrative permissions for IEE/Raleigh
» Enable portfolio reporting dashboards
» Enable Performance Point services
» Bi-monthly update presentations as functionality developed and rolled
out

22. Questions?

23. THANK YOU
www.itron.com

24. START PAGE
Back

25. PROJECT CENTER
Back

26. PWA RIBBON
Back
Project Center
Project
Project Task