![Prepared by: ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
En vedette
En vedette (6)
Similaire à Project Portfolio Management at SF State
Similaire à Project Portfolio Management at SF State (20)
Dernier
Dernier (20)
Project Portfolio Management at SF State
- 1. Success ∝ Collaboration: Case Study on the PMO at SF State University's Division of IT Session #29629 March 28, 2011
- 3. Director of Information Systems Projects and Project Management Office, Division of IT
- 7. The challenges we were up against
- 8. Incoming! – How we handle project requests
- 10. Show me! – Reporting for management and team members
- 11. One source of truth
- 12. The information you need, when you need it
- 13. Staying on the same page
- 14. On-line tools for collaboration
- 15. Where to now?
- 16. Next steps for continued roll-out
- 18. Part of the CSU system
- 19. CSU
- 20. 412,000 students
- 21. 43,000 employees
- 22. SF State
- 23. 30,000 students,
- 26. Non-profit
- 27. Success ∝ Service to Campus Community and beyond
- 28. Campus dependency on legacy systems
- 29. Campus wants new technology to streamline operations
- 30. Limited resources for investing in new technology
- 31. IT organization overwhelmed by incoming requests
- 33. High volume of project requests
- 37. High volume of project requests
- 38. Managing priorities across organization
- 39. How we dug our way out
- 40. Streamline process for project requests
- 41. Single source of truth for project requests
- 42. Workflow for gathering feedback/buy-in
- 44. Customer feels left in the dark
- 45. Developers spend too much time providing updates
- 46. Information is out of date the moment it is reported
- 47. The information you need, when you need it
- 49. Grouped based on customer needs
- 50. Dashboards for quick overview
- 51. Drill-down for more detail
- 52. Single source of truth for project status
- 54. Single repository for project artifacts
- 55. Easy to access
- 56. Change history
- 57. Ability to go back to pervious version
- 58. Don’t make me go look for everything!
- 59. Tools for effective collaboration
- 60. Single, accessible home page for each project
- 61. Embedded document management system
- 62. Centralized task and issue tracking
- 63. Personalized reports – what I need when I need it
- 65. Streamline request process using workflow
- 66. Accommodate various levels of project management process maturity
- 67. Provide support for non-IT projects
- 68. Create portfolios for colleges and departments
- 69. Create reports to show past accomplishments by employee - performance review at a click
- 71. This presentation and all Alliance 2011 presentations are available for download from the Conference site atwww. heug.orgwww.psugonline.orgwww.federalusersnetwork.com Presentations from previous meetings are also available
Notes de l'éditeur
- Caveat – we built our process based on SharePoint with a project management plug-in from BrightworkThis presentation is focused on process, not technologyBe happy to discuss the solution in more detail after presentation
- Fair amount of maintenance requiredLimited resources at the best of time – now, there is a budget crisis to contend withMany-to-many relationship between technical team and campus customers
- Not just about taking the time up front to make sure everybody are on the same pageAlso need to keep everybody on the same page as we go alongRequirements will change underway
- Make it easy for the customer!Fill out one simple formE-mail it to the systemSign-off by customer and project team – buy-inKeep original request form in project library
- Word of mouth can only get you so farFocus for portfolio if project prioritiesPushing information to customers through regular e-mailsEverything in one place
- Disclaimer – of course we have no managers like this at SF State!Customers and IT management focus primarily on portfoliosProject members need a single place to go for project workLack of trust leads to local copies and thus increased risk for errorsAgain – the focus is not on the tool, but the kinds of information we maintain on a project-by-project basisProcess is standardized with extensive use of templatesIf I have worked on one project, I know what I can expect and were to find it for the next project
- These are some of the next steps we are considering for our project management officeIt’s all a matter of resources and priorities!