UCI PMC 2014-2015 Project Plan
The following is a work-in progress project plan for the UCI PMC for the 2014-2015 year
2014-2015 Objectives
- Design, implement, test and use a project approval process/workflow in ServiceNow that can be used for any type of OIT project
- Collect, refine and communicate PM tools, resources and best practices
- Provide consultative PM support for any identified OIT projects
Workstream Activities
- Project Approval Framework and ServiceNow Workflow
- Review current OIT project approval processes being used my larger groups (Eric P)
- Design approval process and framework that can apply across OIT groups (All)
- Discuss ServiceNow implementations with other UC campuses
- Train PMC members on ServiceNow PM and workflow basics
- Define the OIT Project Approval Process workflow in ServiceNow
- Maybe start after Thanksgiving 2014
- Exercise the process and ServiceNow workflow with a small project
- Refine the ServiceNow workflow as needed
- Develop and execute a communications plan for OIT groups to begin using the process and ServiceNow workflow
- Collect, Refine and Communicate PM Tools, Resources and best practices
- Review Eric P's survey results to ID any existing tools and best practices to promote
- Inventory existing tools and resources
- Review, discuss relevance
- Identify tool/resource gaps re: PM best practices
- Identify pain points - things we commonly struggle with where a template or something else could help
- Estimation model, Brown-bag lunch talks, etc.
- Consider "lessons learned" from some of our past projects
- Identify pain points - things we commonly struggle with where a template or something else could help
- Build out the PMC Tools and Resources wiki pages
- Develop additional required tools/resources and link to the PMC Tools and Resources wiki pages
- Develop and execute a communications plan for informing the broader OIT community about these resources
- PM Consultation for Identified OIT Projects
- Identify projects in need of PM consultation support, including the project lead and stakeholders (Kian)
- PMC members ID or OIT Sr Mgrs ID
- Meet with project lead to explore what consultative support would be helpful
- Connect available PMC members as peer-support to those project leads
- Track any essential support activities for later evaluation by the PMC to determine if/how this model could continue/improve
- End-of-year review of any PM consultative support activities and make PMC recommendations for 2015-2016
- Identify projects in need of PM consultation support, including the project lead and stakeholders (Kian)
General
- PMC members work on related activities in addition to their primary work
- Use the wiki and email for effective communication
- Monthly meetings for collaboration and as checkpoints for ensuring progress on activities
Schedule/Plan
Workstream: Project Approval Framework | |||||
---|---|---|---|---|---|
Item # |
Activity |
Assignee | Target/Actual Start Date | Target/Actual End Date |
Notes |
1 | Review current OIT project approval processes bei9ng used by larger groups | Eric P | 9-19-2014 | OIT SDLC is primary process Most OIT Teams support business units get local business unit management approval, but it's less formal in many cases | |
2 | Design approval process and framework that can apply across all OIT Groups | Eric T (All) | 1-26-2015 | ||
3 | Discuss Service Now implementations with other UC campuses re: PM processes | Eric P | 11-14-2015 | No other UC campuses are using SN for PM to any significant degree | |
4 | Train PMC members learn ServiceNow PM and workflow basics | All | 1-26-2015 | Demonstrated at various PMC meetings | |
5 | Define the OIT Project Approval Process workflow in ServiceNow | Eric P | 11-15-2015 | 5-15-2015? | 5-15-2015: Eric P finished config of latest version for pilot testing in production |
6 | Exercise the process and ServiceNow workflow with a small project | Eric P and Eric T | 5-15-2015 | 4-20 thru 5-12 Eric P and Eric T continued testing/exercises in dev and production connecting UCI PM info to SN Proposal record and recording approvals as reflected in the record's action log. 4-12-2015 Eric P and Eric T did an initial exercise, but found the SN Approval record doesn't work as desired for ongoing approvals, tracking and reporting. Switching to storing data with the SN Project record. | |
7 | Refine the SN Workflow | Eric P | 3-4-2015 | 5-15-2015 | 5-15-2015 Eric P/T testing in production 3-4-205 Eric P's switching from tying OIT Project Proposal template data elements from SN Approval records to the SN Project records - also revising the Project Intake form accordingly |
9 | Final test of workflow with example projects and a couple real projects | Eric T | 5-15-2015 | 5-15-2015 Eric T entered test projects in project and will ad real projects next | |
10 | All PMC members submit select real projects (currently in progress) through the submission and review process to retroactively record approvals and see how data looks in SN | Eric T (All) | 3-4-2015 Waiting for new SN Proposal attributes and revised workflow | ||
11 | Consider adding all active OIT projects into SN so it represents a fairly complete picture of activity | Eric T (others) | |||
12 | Develop and execute a communications plan for OIT groups to begin using the process and ServiceNow workflow | ||||
Workstream: Tools and Resources | ||||
---|---|---|---|---|
Item # |
Activity | Target/Actual Start Date | Target/Actual End Date |
Notes |
1 | ||||
1.1 | ||||
1.2 | ||||
2 | ||||
2.1 | ||||
3 | ||||
3.1 |
Workstream: OIT Project Consultative Support | ||||
---|---|---|---|---|
Item # |
Activity | Target/Actual Start Date | Target/Actual End Date |
Notes |
1 | ||||
1.1 | ||||
1.2 | ||||
2 | ||||
2.1 | ||||
3 | ||||
3.1 |