2. About KMA
• Founded 1995
– 29 employees
– 4 partners, including 2 co-founders
• Principal lines of business:
• Professional Services
– SharePoint Consulting
– SharePoint Managed Services
– Custom Application Development
• Software Product
– Mekko Graphics advanced charting
software
• Roots in academia (MIT,
Harvard, BU)
3. Chris McNulty
• KMA SharePoint Practice Lead/Manager
• Working with SharePoint technologies since
2000/2001
• 20 years consulting and financial services
technology (Santander, John Hancock, GMO,
State Street)
• MBA in Investment Management from
Boston College Carroll School of
Management
• Write and speak often on Microsoft IW
technologies (blogs & books)
• Microsoft MCSE/MCTS/MSA/MVTSP
• Hiking, cooking, playing guitar, colonial
history, photography
• My family: Hayley, three kids (16, 7, 4) and
my dog Stan
6. Amy Talhouk
• KMA Associate focused on Project
Management, Business Analysis and
building our PMO
• Boston University School of
Management
• BA in Finance
• Masters in Management
Information Systems
• 15 year IT Professional focused in
Financial Services Software
Development and Consulting
• Supported and promoted SharePoint
and Project Server in various
capacities since 2004
• Avid cook and mother of 15 year old
twins!
7. Why should we care?
• Too many projects
• Different audiences needing different information
• Don’t know what people are working on, what we can
deliver and when
• Regenerating the same data over and over manually
(email a spreadsheet around)
• Resources teams don’t know what to work on next
• No two project plans look alike
• Every estimate is different
• Process can’t grow to accommodate more demand
• No history of what issues we can learn from
• No common understanding of project constraints
(resource, time, cost)
8. Agenda
• Six stage maturity model relative to 2010
• Project Server Platform Overview
• Dashboards and Reporting
• Project Server Architecture and Design
• Questions & Answers
• Summary, resources and next steps
9. Terminology
• EPM – Enterprise Project Management
• PWA – Project Web Access
• SSRS – SQL Server Reporting Services
• SSA – Shared Service Application
• CAL – Client Access License
• SSAS – SQL Server Analysis Services
• BI – Business Intelligence
• OWA – Office Web Applications
• PMO – Project Management Office
• VORP -- Value Over Replacement Player
10. Six Stage Maturity Model
Portfolio
• Formalized project
approval
Management • Detailed Resource
Planning planning, capacity,
• Financial
management of and optimized
• Standardized forecasting
maintenance of project activity
Collaboration across multiple
project plans, tasks,
• Web-based resources and projects
collaboration for schedules • Centralized issue
Tracking project teams on and status reporting
tasks and
• Simple tracking
documents
systems to define
list of active
None projects, shared
folder for
• No systems documents
or process,
no control
over what
projects are
active
http://blogs.kma-llc.net/microknowledge/2009/08/project-management-evolution-and-microsoft-sharepoint-solutions.html
11. Maturity Level - Tracking
• Simple tracking systems
• SharePoint List
• SharePoint Document Library
13. Project Maturity Level - Planning
• Standardized maintenance of project plans, tasks,
resources and schedules
– Project 2010
– SharePoint Team Site
• Enhanced task/Project synchronization in SharePoint
2010 SP1
– 1 Plan = 1 Task list
– “Free-form” resource definitions and security
• Project Server (maybe?)
14. Enhanced Collaboration and Reporting
SharePoint Sync to Project Server 2010
SharePoint
Task List
• Lightweight collaboration through SharePoint
Tasks list
• Sync SharePoint Tasks into Project Server to
drive enterprise Resource Management and
Reporting
• Take advantage of richer Project
Management capabilities using Project Server
Project Server 2010
Project Plan
15. Project Maturity Level - Management
• Financial
management
• Portfolio level
reporting
• Centralized issue
and status
reporting
– Project Server
2010
– SharePoint
Team site
– Dashboard
17. Project Server – Why or Why Not?
The decision whether to move to Project Server
2010 is related to the following factors:
– Maturity
– Complexity
• 10 projects, 30 lines
– Portfolio size
• Rule of Thumb >$5m
– Resource management
• Need to allocate 25% for maintenance and firefighting?
– Dashboards and reporting
– Governance!!!
18. Microsoft Platform Overview
• Overview
• Project 2010 Investment Areas
– Unified Project and Portfolio Management
– Simple and Intuitive User Experience
– Enhance Collaboration and Reporting
– Scalable and Connected Platform
19. Microsoft SharePoint 2010
Ribbon UI
SharePoint Workspace
SharePoint Mobile
Office Client and Office Web App Integration
Business Connectivity Services Standards Support
InfoPath Form Services
External Lists
Workflow
SharePoint Designer
Sites
Tagging, Tag Cloud, Ratings
Visual Studio
Social Bookmarking
API Enhancements
REST/ATOM/RSS
Composites Communities Blogs and Wikis
My Sites
Activity Feeds
Profiles and Expertise
Org Browser
PerformancePoint Services
Insights Content
Excel Services
Chart Web Part
Visio Services
Web Analytics Enterprise Content Types
Search Metadata and Navigation
SQL Server Integration
PowerPivot Document Sets
Multi-stage Disposition
Social Relevance Audio and Video Content Types
Phonetic Search Remote Blob Storage
Navigation List Enhancements
FAST Integration
Enhanced Pipeline
23. Microsoft Project 2010
Unified Project & Portfolio Management
Single server with end to end
PPM capabilities
Flexible project capture and initiation
Enhance governance through workflow
Powerful portfolio selection analytics
24. Microsoft Project 2010
Simple and Intuitive User Experience
Ribbon UI and Backstage view
Intuitive Excel-like behavior
Timeline and Team Planner views
Web-based project editing
25. User Experience
Web-based Project Editing brings the power of
Project Professional to the browser
Easily create schedules and conveniently update
projects online
Flexible scheduling puts you in control
of the plan
Add more than 100 tasks and assign multiple
resources per task
Gain insight through multi-level undo
and change highlighting
26. Microsoft Project 2010
Enhanced Collaboration and Reporting
Sites Built on SharePoint Server 2010
Connect teams with SharePoint Sync
Composites Communities
Better time and status reporting
Easily create reports and dashboards
Insights Content
Search
27. Collaboration and Reporting
Simplified single entry mode for time reporting
and statusing
• Improved user experience
• Single entry mode to unify timesheet entry
and task statusing
• Consolidated Approval Center
• New User Delegation
28. Collaboration & Reporting
Simply create powerful reports and dashboards
• Quickly create reports from predefined
and localized best practice templates
• Customize in Excel and render through
Excel Services
• Create powerful audience based dashboards
to monitor portfolio performance
29. Microsoft Project 2010
Scalable and Connected Platform
Extend Interoperability
Simplified Administration
Rich Platform Services
Developer Productivity
30. Simplified Administration
• Centralized administration – One stop
console for managing both project and
portfolio management capabilities
• User Delegation – Easily specify
colleagues to act as your delegate when
out of the office
• Departmental Fields – Provide a level of
autonomy while maintaining enterprise
standardization and control
• Cube Administration – Enhanced
administration interface to visualize
status and manage cubes
31. SharePoint 2010/Project Server
Summary Highlights
• Demand management and workflow
• Web-based editing of plans
• SharePoint sync for light plan
publishing
• Integrated timesheets/status
• PerformancePoint/Excel Services BI
integration
• Simplified administration
• SharePoint Enterprise – BI, search,
profiles, workflow, ECM, InfoPath,
MMS, OWA, scale, etc. all integrated
32. DEMO – Project Server
• Demand Management
• Plan Creation
• Task Updates
33. EPM Business Intelligence Goals
• Answering the known
questions about our
project portfolio
• Allowing users to self-
discover patterns and
answers to questions
we haven’t yet been
asked
37. Database relationships
SharePoint Sites
Publish
Cube Rebuild
Draft Edit/Save/Publish Published Publish Reporting
Ad Backup
mi
nB Cube Rebuild
ack
up
Archive Analysis
Services
40. Server design
• Install SP Enterprise first, then Project Server
• Use SQL 2008 R2
• Install Reporting Services – SharePoint
Integrated
• Project Server CAL costs more $$$$
41. Sizing - Medium Farm
• Typical Roles:
• 100-10,000 users
• 10,000 – 1MM documents
• Scenarios
• Enterprise Project Management
• Enterprise portal
• Large scale collaboration
• Broader applications platform
• Larger external search pool
• Mix and match internal external
front end servers on common
content databases
42. Top Level Logical Components
• Farm level
• Web applications
• Independent top Web Applications
level URLs
• Run inside IIS pools Site Collections - PWA
•
http://intranet
Consume shared
services and admin
from the farm or
Site Hierarchies
Sites - Projects
other farms
Lists Libraries Pages Web Parts
• Site collections - PWA
http://centadmin Single Sites
(MySite)
• Security, branding,
database frontier
• Contain single sites
or site hierarchies
• Sites
• Group related
SharePoint elements
(lists, libraries,
pages, web parts)
• One for each project
43
43. Shared Service Applications
• The 2007 Shared
Services Provider User Profiles
has been broken Search Metadata
up; each of its
elements is now Excel Calc
a Shared Service Project
Application
• Mix and match as
needed
• In 2010,
administration
can be delegated http://globalweb http://itportal
– Unlikely to
delegate Project
SSA outside IT!
44. Project SSA Console
• Set up PWA site
collections
• Unlikely to delegate
Project SSA outside IT!
48. Best administration practices
• Write once (Project 2010), read many (PWA)
• Share edits with PWA, Tasks instead of sharing
the full plan
• Project Server Accounts (Project Client)
• Patching
• Admin backups
50. Project Server Tips
• Enterprise Fields ≠ Managed Metadata
• SharePoint Security Groups ≠ Project Security
Roles
• Check in, check out
– Force check-in (PWA Settings)
• Cache clear (Project)
– Its hidden for a reason!
– Don’t exit w/o saving
51. Patching
• Release Cycle
– Major Service Packs 6-12 Months
– Aggregated Cumulative Updates every two months.
• Announcements
– Microsoft usually announces them on the SharePoint Team
MSDN blog, http://blogs.msdn.com/b/sharepoint/ and
consolidates the latest patch news at:
http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx
– Also, I tabulate all the patch versions and build numbers on my
blog at http://blogs.kma-llc.net/microknowledge/version-build-
numbers/
• Service Packs are usually directly available for download.
• For Cumulative Updates, you have to supply an email
address, and you’ll be sent a link to a password encrypted
download file.
• Platforms:
– SharePoint Foundation 2010
– SharePoint Server/Project Server 2010 ***
52. Patching – High Level Process
• SharePoint Foundation
Patch
• SharePoint Server – Project Server
Patch
• Run SharePoint Products and Technologies Wizard
• (Or psconfig)
• Sequential Application to Central Admin, Application Server(s), Web Front
Deploy End Servers
54. Project Server Success Factors
• What is a project?
• What are my projects
• How do we run projects?
• Who’s on my team?
• What tools and templates do I want to use?
56. Resources - General
• From Microsoft:
– EPM: http://www.microsoft.com/project
– SharePoint 2010 site: http://sharepoint.microsoft.com
– SharePoint Team Blog: http://blogs.msdn.com/sharepoint/default.aspx
– Project Blog: http://blogs.msdn.com/project
• From KMA (www.kma-llc.net)
– Monthly webinars on SharePoint 2010 (EPM, upgrades, etc.)
– White papers, blogs, presentations, news, and events
• Chris
– SharePoint Saturday the Conference August 11-13 (MMS, BI, EPM, IT, Adoption)
– Connecticut SharePoint User Group August 10 (Business Intelligence)
– New Jersey SharePoint User Group September 14 (Business Intelligence)
– SharePoint Saturday NH – September 24, 2011 (Business Intelligence)
– KMWorld DC October 2011 (IT)
• Amy
• SharePoint Saturday NH – September 24, 2011 (Project Server)