5. blogs.msdn.com/brismith

6. ppmblog.org

26. QUICK DEMO

28. ProjectumDenmarkConsultingDevelopmentSwedenConsultingDevelopment

31. SEE NEXT SLIDE

32. EntityDescriptionSmallMediumLarge 1Projects100500020000 1Tasks171258562503425000 1Average Tasks Per Project 171.25 2Task Transaction History 101001000 1Assignments2226311131254500000 1Average Assignments Per Task 1.3 2/3Approvals506003000 Users10001000050000 Custom FieldsProject (Formula)32025 Custom FieldsProject (Manual)24050 Custom FieldsTask (Formula)61215 Custom FieldsTask (Manual)4810 Custom FieldsAssignment Rolldown 50% Custom FieldsResource102025 Custom FieldsLook up Table Custom Fields 215100 1Timesheets (per year) 520007800008,320,000 1Timesheet Lines510 EntitySmallMediumLarge Projects201005000 Project Sites201005000 % Projects in Managed Mode 0%10%80% Tasks1250250001250000 Average Tasks Per Project62.5250 Task Transaction History10 100 Assignments1625325001625000 Average Assignments Per Task 1.3 Average Tasks per My Site User 502505000 Approvals550600 Resources50100010000 Average Resources Per Project 2.5102 Average Assignments Per Resource 32.5 162.5 Users50100010000 Calendars326100 Issues2040020000 Risks2040020000 Deliverables2080040000 Enterprise Project Types550 Workflows230 Average Projects Per Workflow 50167 Phases550 Phases Per Enterprise Project Type 20 Stages15150 Stages Per Workflow2040 PDPs10100 Custom Fields Per PDP10 Number of Departments100 Average Projects Per Department 50 Average Resources Per Department 100 Timesheets Per Year260052000780000 Status Reports Per Year26000260000

36. The symptom's: PPM deployment projects suffer some of the poorest Project Charters and resource allocation The effect: Leads to confusion, lack of a clear set of goals and often poor technology choices. Focus often shifts to minor issues with a loss of sight to the big issues

37. The symptom's: Other key stakeholders are not engaged The effect: Frustration and turf wars and often loss of access the skilled people who could add leverage to a successful deployment

38. The symptom's: Focus is often on delivery dates without the corresponding functional mapping completed The effect: Morale can be impacted as the realisation of an inability to complete on time becomes clear, often bad news is held back to avoid confrontation

39. The symptom's: Six months into a operational system, performance, functionality, reporting or integration become troublesome The effect: The system needs to be rebuilt, frustration builds up and blame gets thrown around when

40. The symptom's: Colleagues are not adopting the new environment, old habits (Excel, free-standing plans) are re-emerging The effect: The new systems lose accuracy, management lose faith, even ‘good’ citizens revert to the old ways

41. The symptom's: Unexpected problems arise such as not meeting management reporting needs, integration with systems that weren’t foreseen The effect: Additional cost to transform the system to allow for integration, unhappy management who thought ‘they could get anything reports’ they wanted.

42. The symptom's: Different departments demand incompatible structures, deployment decision are not consistent with any structured pland The effect: Deadlines are not met, unnecessary complexities creep into the PPM environment, it all turn a bit ‘ugly’

43. The symptom's: Six(?) months after an adoption decision has been taken little or no progress is visible The effect: IT can be reticent in bringing in Process, Technical and other external SME’s, losing impetus and frustrating the business.

47. MyPC fill out evaluations & win prizes! Fill out session evaluations by logging into MyPC on your laptop or mobile device. Evaluation prizes daily! Claim your prize at the Registration Desk on Level 1. www.msprojectconference.com After the event, over 100 hours of resources; including all of the PPT decks and session videos will be available.