1 / 29

Project Server 2010 Deep Dive v2.0 Presentation for MPUG

Project Server 2010 Deep Dive v2.0 Presentation for MPUG. Mark E. Read Principal Sequence Advisors, Inc. Agenda. Review Architecture Assess Key Updates and Implications Think about Implementation DESIRED OUTCOME: Get excited and afraid, all at the same time. Sequence Advisors, Inc.

neal
Download Presentation

Project Server 2010 Deep Dive v2.0 Presentation for MPUG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Server 2010 Deep Dive v2.0Presentation for MPUG Mark E. Read Principal Sequence Advisors, Inc.

  2. Agenda • Review Architecture • Assess Key Updates and Implications • Think about Implementation DESIRED OUTCOME: Get excited and afraid, all at the same time

  3. Sequence Advisors, Inc. • Founded in 2003 • Bringing database best practices to Project Management on the Microsoft platform • Reporting, Development, Integration Services • Training, Training, Training • Contact: Mark Read 510 406-4645 mark@sequenceadvisors.com

  4. 2010 Physical Architecture

  5. 2010 Logical Architecture

  6. Software Landscape

  7. Program DNA

  8. Portfolio Server Integration • Cost and Resource Portfolio Analysis, Business Drivers and Prioritization • Very helpful to have a mature portfolio management process in place first!

  9. Business Drivers • Strategic Initiatives, Key Goals, etc.

  10. Business Driver Impact Statements • Quantifiable • Quantifiable • Quantifiable

  11. Prioritizing Projects

  12. Portfolio Dependencies • Dependency: Select primary project and other projects that are required by the primary project • Mutual Inclusion: Select the projects that are ALL dependent on each other. If one project from the set is executed, all other projects from the set must also be executed • Mutual Exclusion: Select the projects that are ALL exclusive to each other. If one project from the set is executed, all other projects from the set must NOT be executed • Finish to Start: Select primary project and other projects that must start after the primary project finishes

  13. Workflows in Phases and Stages • Project Detail Pages associated with an Enterprise Project Type determine workflow phases, stages and custom fields • Built in workflow is simple, others require VisualStudio and LOTS of planning. • SharePoint Designer is NOT supported

  14. Project Detail Pages • Capturing multi-line custom fields about projects! • Can vary by department

  15. Sample Workflow • Out of the box • Modify with VS • Approval under $1M • Broken down into phases and stages

  16. Department Field • More powerful than RBS but NOT security-related • Group sets of custom fields for different “departments” • Project Professional displays Custom Fields by Department • Cubes grouped by Department • No Department means ubiquity • Very helpful for larger deployments

  17. Lots of Reporting Options • Excel Services • Performance Point Server • SQL Reporting Services • 64-bit clients and Power Pivot increase dataset limits

  18. Choose the Data Source • Decisional (Analysis Services Cubes) • Relational (Reporting DB) • Up-to-date data • Superset of data available in the AS cubes • No drilldown required in report • Aggregation across dimension(s) • Efficient for reports on time phased data • Key Performance Indicators

  19. Out of the box reports

  20. Excel Services Considerations • Permissions more flexible than before, but not integrated, meaning more work • Custom Fields NOT added to Data Connection Objects automatically, meaning more work • You may want SQL or MDX knowledge before wandering into frustration land…

  21. Excel Services –> Author and Consumer Report Consumer • Excel Client does not use Secure Store Service (SSS) • Requires direct authentication against SQL • Setup author group with db_datareader rights to RDB • Excel Services uses Secure Store Service (SSS) • Setup app profile in SSS with service profile that has db_datareader rights • Authenticate the security group of users to use the profile Report Author 21

  22. RDB : Combined Work Contours • In Microsoft Office Project Server 2007, calculating the exact work assigned to a resource involved decoding application logic in the SQL statement and resulted in complex, non-performant queries • Project Server 2010 has improved storage of time-phased work in RDB • “Combined Work” value in the AssignmentbyDay_UserView • availability = capacity (from resourcebyday) – combined work (from assignmentbyday) • Eliminates need for complex SQL joins to calculate work

  23. Team skills required to implement • Project and Portfolio Analyst • Scheduler • Visual Studio Developer • Workflow Architect • Database Analyst • Trainer

  24. Implementation Considerations • Training, Training, Training • Months and Years, not Hours or Weeks • More important than ever to have a competent partner • Your Information Architecture is crucial to your success

  25. Implementation Considerations • Physical Architecture • Team and Organizational Maturity Assessment and Subsequent Training Plan • Project Plan Evaluation • Resource Pool Data Collection • Logical Architecture / Custom Codes • Workflows / Project Detail Pages • Conversion from Excel/SharePoint into Project • Reporting Requirements

  26. WORK=DURATION * RESOURCE UNITS BROKEN? Sort of but not really • 2010 tries to make it better but Gantt chart display isn’t sufficient: You need Task Usage and Peak Units ?

  27. More On Assignment Units • http://blogs.msdn.com/project/archive/2010/04/29/assignment-units-in-project-2010.aspx • “Brian, your explanation is very thorough, however the Microsoft made a wrong design choice in my mind. Microsoft decided that the Assignment Units field should now always reflect what you manually entered. To the user this will appear as if the formula does not work any longer because it does not recalculate the Units any longer as it did in EVERY previous release. Thousands of people have been using this formula and manipulating their schedules with it. Knowing and using the formula gave a sense of mastering the tool. • What should Microsoft have done to solve the issue with the actual hours driving the Assignment Units? Microsoft should have calculated the Assignment Units based on the Remaining Duration part of the task instead of on the entire Duration. This would have taken care of the problem without causing such an upheaval among people who monitor and rely on the formula to manipulate their schedule. I hope Microsoft will still reconsider its poor design choice.” -- ERIC UYTTEWAAL

  28. Conclusion • This release is awesome, and that cuts both ways • It’s the one we’ve been waiting for, pushing for, preparing for… • Shared code base with 2007 means more stable than the last release • You now have a great deal of capabilities, and with that, potential • We can help

  29. Questions? Comments? • Thank you!

More Related