The Princeton Project Office


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • What has worked at Princeton over the past 1 1/2 years according to our project managers? It is essential to follow a proven methodology in managing projects. A strong executive sponsor is critical. It was Ray Clark who, as the Ex. Sponsor on the Coeus project, was able to get stakeholder buy in and consensus on the project. Active Project Sponsor -- it was Van Williams acting as the STRipes project sponsor who played a key role as the project champion. He attended team meetings and sent email congratulating the team for completing milestones as the project unfolded.
  • Technical staff in place -- UFINSI was interviewing for 3 technical positions when the project had already begun. Have people hired and in place ready to go when project officially starts. Backfill -- may not be able to backfill certain positions by hiring new person (since they won’t know how University works). May have to give pieces of job to a group of individuals and hire clerical person to pick up pieces. Be creative when backfilling. Plan for space where individuals backfilling can work. Production support -- have adequate resources trained and taking the lead in central offices. This should be individuals, such as Assistant Directors or Managers, who will be project champions and can make certain that new processes and work procedures are in place to accommodate the new system. Plan for a strategy of applying fixes. There can be a lot of them. Plan for redesign and “production mock up” -- When testing try to have the environment simulate the production environment as realistically as possible (data, security, customizations, schedules).
  • At the beginning (Initiation Plan) its difficult to know effort required on project. Won’t really understand until complete scoping (what are our business processes;what are our priorities /prototyping (how does this fit with PeopleSoft) how long project will take. Give date ranges up front. Get understanding from sponsor that critical milestone dates can be adjusted once complete prototyping. Control phase bleed over by holding post phase assessment at end of each phase. Isolate, analyze, monitor and control tasks that are bleeding over. Review scope periodically -- do at least quarterly to make sure staying on track and that there isn’t scope creep (UFINSI wrote once and never revisited).
  • UFINSI and STRIPES hold weekly team meetings to keep project on track UFINSI found detail planning in two month segments worked well and was manageable UFINSI used consultants to help keep project on track since they had good people management skills Oral status reports were ofen more efficient for project manager to put together and worked effectively with sponsor Stripes & UFINSI recommends looking at critical milestones and then analyzing what is absolutely essential to do, prioritize those tasks, and determine who does what when.
  • UFINSI and STRIPES hold weekly team meetings to keep project on track UFINSI found detail planning in two month segments worked well and was manageable UFINSI used consultants to help keep project on track since they had good people management skills Oral status reports were ofen more efficient for project manager to put together and worked effectively with sponsor Stripes & UFINSI recommends looking at critical milestones and then analyzing what is absolutely essential to do, prioritize those tasks, and determine who does what when.
  • Team building -- take team on retreat if they haven’t worked together before (Kim is doing this with Student project); build memories (pictures in scrap book, mugs, t-shirts) Stripes team had lots of parties -- pizza parties, cakes celebrating milestones, orange and black stripes halloween party, to build team spirit. Other suggestions: Build team memories (t shirts
  • The Princeton Project Office

    1. 1. Project Management: A Critical Skill for Princeton Presented by Hetty Baiz Princeton Project Office OIT, Princeton University
    2. 2. Background <ul><li>Multiple Projects </li></ul><ul><li>Cross-functional </li></ul><ul><li>Mutually Interdependent </li></ul><ul><li>Success and failure is no longer within the total control of that project. </li></ul>
    3. 3. What’s A Project?
    4. 4. What’s A Project? <ul><li>A “project” </li></ul><ul><li>Will deliver </li></ul><ul><ul><li>Business and/or technical objectives </li></ul></ul><ul><li>Is made up of </li></ul><ul><ul><li>Defined processes & tasks </li></ul></ul><ul><li>Will run for </li></ul><ul><ul><li>Set period of time </li></ul></ul><ul><li>Has a budget </li></ul><ul><ul><li>Resources and $’s </li></ul></ul>
    5. 5. What is Project Success?
    6. 6. What is Project Success? The 'Golden Triangle' of Project success occurs when we have: and Objectives Time Cost Project Success     A delighted client (expectations met) Delivered the agreed objectives Met an agreed budget - $, resources etc. Within an agreed time frame  Done it all professionally & without killing the team
    7. 7. Why Do Projects Fail? <ul><li>Changing scope </li></ul><ul><li>Insufficient planning </li></ul><ul><li>No risk or issues management </li></ul><ul><li>Poor communication </li></ul><ul><li>Lack of commitment and responsibility by stakeholders </li></ul>
    8. 8. Who Are Stakeholders? Project Academic & Business Units Outside Groups (Vendors) Team Members Information Technology Steering Committee Clients & Users Senior Mgmt Interdependent Projects
    9. 9. Project Management A Maturity Model seat of the pants Success rate less than 30% aware e Success rate of 30 to 45% Success rate of 45 to 75% Success rate better than 75% best practice best practice competent seat of pants aware aware
    10. 10. Seat of Pants <ul><li>Projects happen without correct initiation </li></ul><ul><ul><li>Planning is insufficient </li></ul></ul><ul><ul><li>Benefits are unknown </li></ul></ul><ul><ul><li>There is often inadequate buy-in </li></ul></ul><ul><li>Communication is poor </li></ul><ul><li>Interdependencies are not managed </li></ul><ul><li>Standards, if any, are poorly defined or unenforced. </li></ul>Seat of pants Success rate less than 30%
    11. 11. Aware <ul><li>Projects are formally initiated & plans endorsed but with varying standards and few disciplines </li></ul><ul><li>Methodology has been introduced </li></ul><ul><li>Stakeholders support projects overall </li></ul><ul><li>The number of projects is rationalized </li></ul><ul><li>Projects are explicitly associated with business planning </li></ul>aware Success rate of 30 To 40%
    12. 12. Competent <ul><li>Methodology and standards are well established and supported </li></ul><ul><li>Stakeholders understand and accept roles </li></ul><ul><li>Discrete measures support good management </li></ul><ul><li>Projects are set up and managed end-to-end </li></ul><ul><li>Risks are clearly defined and controlled </li></ul>competent Success rate of 45 To 75%
    13. 13. Best Practice <ul><li>Improvement programs are formal </li></ul><ul><li>Good measurement enables optimization </li></ul><ul><li>Level of confidence sees organization taking on high risk projects successfully </li></ul><ul><li>Respect and support of projects and project managers </li></ul>best practice Success rate better than 75%
    14. 14. Why Should We Care? <ul><li>To Increase the likelihood that projects will : </li></ul><ul><ul><li>be done on time and within budget </li></ul></ul><ul><ul><li>meet people’s expectations </li></ul></ul><ul><ul><li>be done well </li></ul></ul>
    15. 15. Project Office Mission <ul><li>To enable the successful implementation of OIT initiatives in a way that establishes a project management culture so that we deliver projects on time, within budget and with expected results. </li></ul>
    16. 16. How? <ul><li>Define a Princeton Project Management Methodology (PPMM) </li></ul><ul><li>Support and Mentor </li></ul><ul><li>Offer Training </li></ul><ul><li>Facilitation, Audit, Review </li></ul>
    17. 17. P2K Project Office Methodology Consulting/Mentoring Education/Training Continuous Improvement
    18. 18. Project Management Process Initiation Plan Detailed Plan Status Report Post Project Review Report Initiation Complete & Assess Tracking & Control Reporting Review Planning
    19. 19. Management Techniques <ul><li>To increase the likelihood of project success you must manage: </li></ul><ul><li>Stakeholders </li></ul><ul><li>Risks </li></ul><ul><li>Issues </li></ul><ul><li>Change </li></ul>
    20. 20. How to Manage Stakeholders <ul><li>A stakeholder is any person or group who, if their support were to be withdrawn, could cause the project to fail. </li></ul><ul><li>- Get them involved </li></ul><ul><li>- Keep them informed </li></ul><ul><li>- Gain their endorsement </li></ul>
    21. 21. How to Manage Stakeholders <ul><li>Identify stakeholders </li></ul><ul><li>Involve in planning </li></ul><ul><li>Establish expectations / accountabilities </li></ul><ul><li>Formal communication </li></ul><ul><li>Gain sign-off </li></ul><ul><li>Change and issues resolution </li></ul><ul><li>Project reviews </li></ul><ul><li>Define project completion </li></ul>
    22. 22. Risk Management <ul><li>What is “risk”? </li></ul><ul><li>Any factor capable of causing the project to go off track. </li></ul><ul><ul><li>Develop and monitor a Risk Plan </li></ul></ul>
    23. 23. Issues Management <ul><li>Unresolved issues will drive a project towards failure and consume a significant part of a project manager’s time. </li></ul><ul><li>Stakeholders play key role in issues management and resolution </li></ul><ul><li>- Establish Issues log, review, escalation process </li></ul>
    24. 24. Change Management <ul><li>Uncontrolled changes to a project will probably account for up to 30% of a project’s total effort. </li></ul><ul><li>If these changes are not managed, the project will be viewed to be over time and over budget. </li></ul><ul><li>- Establish a Change management process </li></ul>
    25. 25. PPMM Summary Overview <ul><li>The Process </li></ul><ul><ul><li>Initiation </li></ul></ul><ul><ul><li>Planning - Track/Control - Report - Review </li></ul></ul><ul><ul><li>Completion and Assessment </li></ul></ul><ul><li>Management Techniques </li></ul><ul><ul><li>Stakeholder Management </li></ul></ul><ul><ul><li>Risk Management </li></ul></ul><ul><ul><li>Issues Management </li></ul></ul><ul><ul><li>Change Management </li></ul></ul>
    26. 26. PPMM Deliverables <ul><li>Project Plans </li></ul><ul><li>Status Reports </li></ul><ul><li>Audit & Review Report </li></ul>
    27. 27. PPMM Tools <ul><li>Office 2000 </li></ul><ul><ul><li>Word </li></ul></ul><ul><ul><li>Excel </li></ul></ul><ul><ul><li>Access </li></ul></ul><ul><li>MS Project 2000 </li></ul>
    28. 28. For more information…... <ul><li>Call the Princeton Project Office at </li></ul><ul><li>8-6335 </li></ul><ul><li>Send e-mail to </li></ul><ul><li>Visit our web site at… </li></ul><ul><li> </li></ul>
    29. 30. Recommended Best Practices <ul><li>Project Planning and Management </li></ul><ul><li>Follow proven methodologies </li></ul><ul><li>Active Executive/Project Sponsor </li></ul><ul><li>Identify / revisit “critical success” factors </li></ul><ul><li>Document assumptions </li></ul><ul><ul><li>Business process change vs. customization </li></ul></ul>
    30. 31. Recommended Best Practices <ul><li>Project Planning and Management </li></ul><ul><li>Have technical staff in place at start-up </li></ul><ul><li>Plan for backfill </li></ul><ul><li>Involve Steering Committee early </li></ul><ul><li>Plan production support in central offices </li></ul><ul><li>Plan for applying fixes </li></ul><ul><li>Plan for “end of project” </li></ul><ul><li>Plan for vacation/sick time </li></ul>
    31. 32. Recommended Best Practices <ul><li>Scheduling, Tracking and Control </li></ul><ul><li>Break large projects into phases </li></ul><ul><li>(no > 18 - 24 months total) </li></ul><ul><li>Control phase “bleed over” </li></ul><ul><li>Post phase assessments </li></ul><ul><li>“ Go/No Go” decision points </li></ul><ul><li>Sponsor sign-off </li></ul><ul><li>Review Scope periodically </li></ul>
    32. 33. Recommended Best Practices <ul><li>Scheduling, Tracking and Control </li></ul><ul><li>Building learning curve into plans </li></ul><ul><li>Weekly team meetings </li></ul><ul><li>Detail planning in 1-2 month segments </li></ul><ul><li>Define and manage to “critical path” </li></ul><ul><ul><li>What’s important </li></ul></ul><ul><ul><li>Prioritize </li></ul></ul><ul><ul><li>Who, what, when </li></ul></ul>
    33. 34. Recommended Best Practices <ul><li>Reporting </li></ul><ul><li>Establish monthly status reporting </li></ul><ul><li>Hold monthly status reviews with key stakeholders </li></ul><ul><ul><li>Oral status reports are effective </li></ul></ul><ul><li>Keep users of system (middle managers) informed </li></ul>
    34. 35. Recommended Best Practices <ul><li>Resourcing </li></ul><ul><li>Resource Plan </li></ul><ul><li>Cross functional teams work </li></ul><ul><li>Co-locate teams </li></ul><ul><li>Projects are full time job </li></ul><ul><li>Complete training before prototyping </li></ul><ul><li>Have full team train together </li></ul><ul><li>Leverage investment </li></ul><ul><li>Build team spirit </li></ul>
    35. 36. Recommended Best Practices <ul><li>Managing Expectations </li></ul><ul><li>Communication Plan </li></ul><ul><li>Make major policy decisions up front </li></ul><ul><li>Don’t make promises to users up front </li></ul><ul><li>Monthly status report and review </li></ul><ul><li>Monthly / bi-monthly presentations </li></ul><ul><li>Articles, web pages, newsletters </li></ul><ul><li>Special communications from sponsor </li></ul><ul><li>Focus groups, demos, town meetings </li></ul>
    36. 37. Recommended Best Practices <ul><li>Promoting the System </li></ul><ul><li>Focus Groups during gap analysis </li></ul><ul><li>Demos for every user after first release </li></ul><ul><li>Active Executive Committee showed support </li></ul><ul><li>Town meetings to endorse system </li></ul><ul><li>Major presentation to users </li></ul><ul><li>“ Pretzel stick” advertisement </li></ul>
    37. 38. Recommended Best Practices <ul><li>Methodology </li></ul><ul><li>Follow proven methodologies </li></ul><ul><li>Consolidate methodology ( pre-kick off ) </li></ul><ul><li>Functional reps go to all prototyping </li></ul><ul><li>Use standard report formats </li></ul><ul><li>Co-locate developer with tester (short term) </li></ul>
    38. 39. Recommended Best Practices <ul><li>Managing the Consulting Partner </li></ul><ul><li>Selection criteria should include </li></ul><ul><ul><li>Ability to transfer knowledge </li></ul></ul><ul><ul><li>Help organize team </li></ul></ul><ul><ul><li>Follow proven methodology </li></ul></ul><ul><ul><li>Provide good implementation tools </li></ul></ul><ul><ul><li>Ability to form good working partnership </li></ul></ul><ul><ul><li>Higher Education experience </li></ul></ul><ul><ul><li>Work locally (near by or on-site) </li></ul></ul>
    39. 40. Recommended Best Practices <ul><li>Managing the Consulting Partner </li></ul><ul><li>Take time to define contract </li></ul><ul><ul><li>Terms and conditions / Statement of work (metrics) </li></ul></ul><ul><li>Review by Legal, tech., bus., purchasing </li></ul><ul><li>Veto power to select / reject resources </li></ul><ul><li>Fixed price gives University more control </li></ul><ul><li>Tie payments to acceptance of deliverables </li></ul><ul><li>Review quality plans </li></ul><ul><li>State that the University has methodology </li></ul>
    40. 41. Recommended Best Practices <ul><li>Managing the Consulting Partner </li></ul><ul><li>Form partnership - make part of team </li></ul><ul><li>Have single point of contact </li></ul><ul><li>Build one project plan </li></ul><ul><li>Consultant defines phase objectives </li></ul><ul><li>Build in reviews with decision points </li></ul><ul><ul><li>Meet expectations / Go-no go decision </li></ul></ul><ul><li>Plan for early transition of knowledge </li></ul><ul><li>Implementation done by Princeton </li></ul>
    41. 42. Recommended Best Practices <ul><li>Managing the Vendor </li></ul><ul><li>Have single point of contact </li></ul><ul><li>Include RFP responses / bind vendor to meet </li></ul><ul><li>Cap maintenance fees (post impl. Phase) </li></ul><ul><li>Don’t presume product works from day 1 </li></ul><ul><ul><li>Fixes required? </li></ul></ul><ul><li>Review Quality Plans </li></ul>
    42. 43. Recommended Best Practices <ul><li>Managing the Vendor </li></ul><ul><li>Know package after prototyping (not sales) </li></ul><ul><li>Include vendor milestones in project plan </li></ul><ul><li>Build “decision points” into plan where tight vendor dependencies </li></ul><ul><li>Have contingency plans in place </li></ul>
    43. 44. For more information…... <ul><li>Visit our Web site at… </li></ul><ul><li> </li></ul>