Project Start Date: Mon 10/20/03
Project Finish Date: Mon 10/24/05
| WBS | ID | Name | Deadline | Duration | Start_Date | Early_Finish | Early_Start | Milestone | Notes | Cost | Critical | Priority | Remaining_Duration | Resource_Group |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 1 | Initiate and Manage the Project | NA | 131 days | Mon 10/20/03 | Mon 4/19/04 | Mon 10/20/03 | No | $0.00 | Yes | 500 | 131 days | ||
| 1.1 | 2 | Validate Project Charter | NA | 4 days | Mon 10/20/03 | Thu 10/23/03 | Mon 10/20/03 | No | $0.00 | Yes | 500 | 4 days | ||
| 1.2 | 3 | Identify and commit project resources | NA | 4 days | Fri 10/24/03 | Wed 10/29/03 | Fri 10/24/03 | No | $0.00 | Yes | 500 | 4 days | ||
| 1.3 | 4 | Establish progress reporting format | NA | 4 days | Thu 10/30/03 | Tue 11/4/03 | Thu 10/30/03 | No | $0.00 | Yes | 500 | 4 days | ||
| 1.4 | 5 | Agree on procedures for managing project-related issues and changes in project scope | NA | 4 days | Wed 11/5/03 | Mon 11/10/03 | Wed 11/5/03 | No | $0.00 | Yes | 500 | 4 days | ||
| 1.5 | 6 | Define how project materials will be organized and documented (Project Control Book) | NA | 8 days | Tue 11/11/03 | Thu 11/20/03 | Tue 11/11/03 | No | $0.00 | Yes | 500 | 8 days | ||
| 1.6 | 7 | Complete detailed project plan, and obtain approval | NA | 16 days | Fri 11/21/03 | Fri 12/12/03 | Fri 11/21/03 | No | $0.00 | Yes | 500 | 16 days | ||
| 1.7 | 8 | Conduct organizing meetings with project teams | NA | 8 days | Mon 12/15/03 | Wed 12/24/03 | Mon 12/15/03 | No | $0.00 | Yes | 500 | 8 days | ||
| 1.8 | 9 | Establish project communications procedure | NA | 8 days | Thu 12/25/03 | Mon 1/5/04 | Thu 12/25/03 | No | $0.00 | Yes | 500 | 8 days | ||
| 1.9 | 10 | Issue progress reports | NA | 131 days | Mon 10/20/03 | Mon 4/19/04 | Mon 10/20/03 | No | $0.00 | No | 500 | 131 days | ||
| 1.9.1 | 11 | Issue progress reports 1 | NA | 1 day | Mon 10/20/03 | Mon 10/20/03 | Mon 10/20/03 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.2 | 12 | Issue progress reports 2 | NA | 1 day | Mon 11/17/03 | Mon 11/17/03 | Mon 11/17/03 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.3 | 13 | Issue progress reports 3 | NA | 1 day | Mon 12/15/03 | Mon 12/15/03 | Mon 12/15/03 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.4 | 14 | Issue progress reports 4 | NA | 1 day | Mon 1/19/04 | Mon 1/19/04 | Mon 1/19/04 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.5 | 15 | Issue progress reports 5 | NA | 1 day | Mon 2/16/04 | Mon 2/16/04 | Mon 2/16/04 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.6 | 16 | Issue progress reports 6 | NA | 1 day | Mon 3/15/04 | Mon 3/15/04 | Mon 3/15/04 | No | $0.00 | No | 1000 | 1 day | ||
| 1.9.7 | 17 | Issue progress reports 7 | NA | 1 day | Mon 4/19/04 | Mon 4/19/04 | Mon 4/19/04 | No | $0.00 | No | 1000 | 1 day | ||
| 2 | 18 | Design and Conduct Client Surveys | NA | 82 days | Tue 1/6/04 | Wed 4/28/04 | Tue 1/6/04 | No | $0.00 | Yes | 500 | 82 days | ||
| 2.1 | 19 | Assemble survey team | NA | 4 days | Tue 1/6/04 | Fri 1/9/04 | Tue 1/6/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.2 | 20 | Solicit topics for inquiry from service providers (within CIT and distributed) | NA | 4 days | Mon 1/12/04 | Thu 1/15/04 | Mon 1/12/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.3 | 21 | Determine subsets of clientele to survey; probably students and employees, or students and faculty and staff | NA | 4 days | Fri 1/16/04 | Wed 1/21/04 | Fri 1/16/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.4 | 22 | Develop student survey(s); determine optimum timing and means of data collection (in-person interviews, online surveys, paper, etc.) | NA | 12 days | Thu 1/22/04 | Fri 2/6/04 | Thu 1/22/04 | No | $0.00 | Yes | 500 | 12 days | ||
| 2.5 | 23 | Develop staff & faculty survey(s); determine optimum timing and means of data collection (in-person interviews, online surveys, paper, etc.) | NA | 24 days | Mon 2/9/04 | Thu 3/11/04 | Mon 2/9/04 | No | $0.00 | Yes | 500 | 24 days | ||
| 2.6 | 24 | Determine and purchase survey-taker bonuses | NA | 2 days | Fri 3/12/04 | Mon 3/15/04 | Fri 3/12/04 | No | $0.00 | Yes | 500 | 2 days | ||
| 2.7 | 25 | Develop student survey advertising plan | NA | 4 days | Tue 3/16/04 | Fri 3/19/04 | Tue 3/16/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.8 | 26 | Develop faculty & staff survey(s) advertising plan | NA | 4 days | Mon 3/22/04 | Thu 3/25/04 | Mon 3/22/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.9 | 27 | Advertise and administer student survey | NA | 8 days | Fri 3/26/04 | Tue 4/6/04 | Fri 3/26/04 | No | $0.00 | Yes | 500 | 8 days | ||
| 2.10 | 28 | Advertise and administer faculty & staff survey(s) | NA | 8 days | Wed 4/7/04 | Fri 4/16/04 | Wed 4/7/04 | No | $0.00 | Yes | 500 | 8 days | ||
| 2.11 | 29 | Manually enter survey results if necessary | NA | 4 days | Mon 4/19/04 | Thu 4/22/04 | Mon 4/19/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 2.12 | 30 | Announce prizes and administer prize claims | NA | 4 days | Fri 4/23/04 | Wed 4/28/04 | Fri 4/23/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 3 | 31 | Evaluate Survey Results & Develop Action Items for Improving Client Service | NA | 84 days? | Thu 4/29/04 | Tue 8/24/04 | Thu 4/29/04 | No | $0.00 | Yes | 500 | 84 days? | ||
| 3.1 | 32 | Provide in-progress survey results for each survey, if possible | NA | 4 days | Thu 4/29/04 | Tue 5/4/04 | Thu 4/29/04 | No | $0.00 | Yes | 500 | 4 days | ||
| 3.2 | 33 | Publish Perseus-generated simple reports for each survey | NA | 8 days | Wed 5/5/04 | Fri 5/14/04 | Wed 5/5/04 | No | $0.00 | Yes | 500 | 8 days | ||
| 3.3 | 34 | Convene IT providers for results analysis (perhaps in subgroups by survey or by clientele): find themes, determine what's working and needs strengthening; what is not working; changes and trends since last iteration of each survey | NA | 12 days | Mon 5/17/04 | Tue 6/1/04 | Mon 5/17/04 | No | $0.00 | Yes | 500 | 12 days | ||
| 3.4 | 35 | IT Newsletter article for each survey, including graphical and descriptive analysis | NA | 12 days | Wed 6/2/04 | Thu 6/17/04 | Wed 6/2/04 | No | $0.00 | Yes | 500 | 12 days | ||
| 3.5 | 36 | Prioritize areas for improvement; propose solutions; assess feasibility; choose which to pursue. Focus on the most readily doable and useful; forward remainder to "Delivery Framework" or IT Master Plan. | NA | 16 days | Fri 6/18/04 | Fri 7/9/04 | Fri 6/18/04 | No | $0.00 | Yes | 500 | 16 days | ||
| 3.6 | 37 | Develop project plans for improvements | NA | 20 days | Mon 7/12/04 | Fri 8/6/04 | Mon 7/12/04 | No | $0.00 | Yes | 500 | 20 days | ||
| 3.7 | 38 | Announce plans via IT Newsletter (and via ?); | NA | 8 days | Mon 8/9/04 | Wed 8/18/04 | Mon 8/9/04 | No | $0.00 | Yes | 500 | 8 days | ||
| 3.8 | 39 | Assess success of improvements, e.g., through future surveys | NA | 4 days? | Thu 8/19/04 | Tue 8/24/04 | Thu 8/19/04 | No | $0.00 | Yes | 500 | 4 days? | ||
| 4 | 40 | Benchmarking & best practices: UVM, peer & aspirant institutions | NA | 84 days | Tue 1/6/04 | Fri 4/30/04 | Tue 1/6/04 | No | $0.00 | No | 500 | 84 days | ||
| 4.1 | 41 | Assemble project team | NA | 4 days | Tue 1/6/04 | Fri 1/9/04 | Tue 1/6/04 | No | $0.00 | No | 500 | 4 days | ||
| 4.2 | 42 | Determine what is of interest: support ratios, support structures, budgetary structures, best practices. Include student computing as well as faculty and staff. Develop recording (database) formats for consistency. | NA | 8 days | Mon 1/12/04 | Wed 1/21/04 | Mon 1/12/04 | No | $0.00 | No | 500 | 8 days | ||
| 4.3 | 43 | Identify institutions of interest: peer and aspirant institutions | NA | 4 days | Thu 1/22/04 | Tue 1/27/04 | Thu 1/22/04 | No | $0.00 | No | 500 | 4 days | ||
| 4.4 | 44 | Identify information sources | NA | 8 days | Wed 1/28/04 | Fri 2/6/04 | Wed 1/28/04 | No | $0.00 | No | 500 | 8 days | ||
| 4.5 | 45 | Gather information – UVM | NA | 20 days | Mon 2/9/04 | Fri 3/5/04 | Mon 2/9/04 | No | $0.00 | No | 500 | 20 days | ||
| 4.6 | 46 | Gather information – other institutions | NA | 20 days | Mon 3/8/04 | Fri 4/2/04 | Mon 3/8/04 | No | $0.00 | No | 500 | 20 days | ||
| 4.7 | 47 | Analyze information – where does UVM differ; which gaps are important to close; which differences are desirable or acceptable | NA | 20 days | Mon 4/5/04 | Fri 4/30/04 | Mon 4/5/04 | No | $0.00 | No | 500 | 20 days | ||
| 5 | 48 | Service Delivery Framework/Students: Design Client-Facing Service Improvements (excluding labs and classrooms) | NA | 216 days | Wed 8/25/04 | Wed 6/22/05 | Wed 8/25/04 | No | $0.00 | Yes | 500 | 216 days | ||
| 5.1 | 49 | Assemble project team; include Microcomputer Services, Client Services (including Media Resources and student employees), Academic Computing. Identify and enlist IT support providers outside of CIT: perhaps Libraries, ResLife, Wired suite. | NA | 8 days | Wed 8/25/04 | Fri 9/3/04 | Wed 8/25/04 | No | $0.00 | Yes | 500 | 8 days | ||
| 5.2 | 50 | Conduct focused, collaborative work sessions, comprised of IT and user community representatives, both to develop the proposed client service framework and to identify and analyze short-term opportunities for service improvement. | NA | 16 days | Mon 9/6/04 | Mon 9/27/04 | Mon 9/6/04 | No | $0.00 | Yes | 500 | 16 days | ||
| 5.3 | 51 | Collect and analyze all relevant internally-available information sources, including client services data recorded in the Footprints data base for all IT support units, workstation sales and support transaction information from the Microcomputer Depot. | NA | 24 days | Tue 9/28/04 | Fri 10/29/04 | Tue 9/28/04 | No | $0.00 | Yes | 500 | 24 days | ||
| 5.4 | 52 | Analyze need for change: what problems are we trying to solve; for whom; understand current processes and providers -- what's not working with current locations and processes (is it location, volume, nature of services, or process?); what is working; conf | NA | 24 days | Mon 11/1/04 | Thu 12/2/04 | Mon 11/1/04 | No | $0.00 | Yes | 500 | 24 days | ||
| 5.5 | 53 | Investigate anticipated trends in student computing – student-, faculty- and administration-driven. | NA | 12 days | Fri 12/3/04 | Mon 12/20/04 | Fri 12/3/04 | No | $0.00 | Yes | 500 | 12 days | ||
| 5.6 | 54 | Identify client groups which may have different needs that are met by different service structures and processes. | NA | 12 days | Tue 12/21/04 | Wed 1/5/05 | Tue 12/21/04 | No | $0.00 | Yes | 500 | 12 days | ||
| 5.7 | 55 | Recommend means of providing clear and consistent pathways and procedures for reporting, referring, monitoring and resolving user-reported problems, taking into account that IT client services are provided by a variety of organizations with varying needs, | NA | 20 days | Thu 1/6/05 | Wed 2/2/05 | Thu 1/6/05 | No | $0.00 | Yes | 500 | 20 days | ||
| 5.8 | 56 | Determine optimum service locations and hours; room visits vs. common ("walk-in") sites vs. phone support. Explore feasibility of identified locations and times. Explore staffing and collaboration options. Explore impact on IT personnel: schedules, effici | NA | 20 days | Thu 2/3/05 | Wed 3/2/05 | Thu 2/3/05 | No | $0.00 | Yes | 500 | 20 days | ||
| 5.9 | 57 | Recommend means to reduce or accommodate the diversity of user computing platforms and configurations that must be supported, since this complicates the ability of support staff to respond efficiently to user-reported problems, properly inform and educate | NA | 20 days | Thu 3/3/05 | Wed 3/30/05 | Thu 3/3/05 | No | $0.00 | Yes | 500 | 20 days | ||
| 5.10 | 58 | Define expectations for client information fluency, active or passive problem resolution roles, recommended, supported, or nonrecommended software, hardware, and networking. | NA | 16 days | Thu 3/31/05 | Thu 4/21/05 | Thu 3/31/05 | No | $0.00 | Yes | 500 | 16 days | ||
| 5.11 | 59 | Identify other proactive measures, such as education and publications, which could transform the need for and nature of "help." | NA | 12 days | Fri 4/22/05 | Mon 5/9/05 | Fri 4/22/05 | No | $0.00 | Yes | 500 | 12 days | ||
| 5.12 | 60 | Consider opportunities and demands posed by new student center | NA | 12 days | Tue 5/10/05 | Wed 5/25/05 | Tue 5/10/05 | No | $0.00 | Yes | 500 | 12 days | ||
| 5.13 | 61 | Develop proposal(s) including benefits, resource needs, structures, coordination and work flow processes; current and future (student center) locations. Propose Future IT Client Services Delivery Framework for Students | NA | 20 days | Thu 5/26/05 | Wed 6/22/05 | Thu 5/26/05 | No | $0.00 | Yes | 500 | 20 days | ||
| 6 | 62 | Service Delivery Framework/Employees: Design Service Improvements | NA | 192 days | Wed 8/25/04 | Thu 5/19/05 | Wed 8/25/04 | No | $0.00 | No | 500 | 192 days | ||
| 6.1 | 63 | Assemble project team; include Microcomputer Services, Client Services (including Media Resources and student employees), Academic Computing; Administrative Information Systems. Identify and enlist IT support providers outside of CIT. | NA | 8 days | Wed 8/25/04 | Fri 9/3/04 | Wed 8/25/04 | No | $0.00 | No | 500 | 8 days | ||
| 6.2 | 64 | Conduct focused, collaborative work sessions, comprised of IT and user community representatives, both to develop the proposed client service framework and to identify and analyze short-term opportunities for service improvement. | NA | 16 days | Mon 9/6/04 | Mon 9/27/04 | Mon 9/6/04 | No | $0.00 | No | 500 | 16 days | ||
| 6.3 | 65 | Collect and analyze all relevant internally-available information sources, including client services data recorded in the Footprints data base for all IT support units; computer sales and support transaction information from the Microcomputer Depot | NA | 24 days | Tue 9/28/04 | Fri 10/29/04 | Tue 9/28/04 | No | $0.00 | No | 500 | 24 days | ||
| 6.4 | 66 | Examine current processes -- how do employees really get help; how long does it take; what are problem factors (lack of proficiency; lack of information or communication; inconsistency of client environment; complexity or unreliability of infrastructure/a | NA | 24 days | Mon 11/1/04 | Thu 12/2/04 | Mon 11/1/04 | No | $0.00 | No | 500 | 24 days | ||
| 6.5 | 67 | Understand results of IT Inventory project: variety or consistency of client hardware and software, expenditures, budgets | NA | 8 days | Fri 12/3/04 | Tue 12/14/04 | Fri 12/3/04 | No | $0.00 | No | 500 | 8 days | ||
| 6.6 | 68 | Understand approaches of smaller UVM units (Medicine, Business, Admin & Facilities Services, Development, Arts & Sciences) | NA | 8 days | Wed 12/15/04 | Fri 12/24/04 | Wed 12/15/04 | No | $0.00 | No | 500 | 8 days | ||
| 6.7 | 69 | Understand needs of special units (e.g., executive offices) | NA | 4 days | Mon 12/27/04 | Thu 12/30/04 | Mon 12/27/04 | No | $0.00 | No | 500 | 4 days | ||
| 6.8 | 70 | Investigate anticipated trends in employee computing; institutional and particularly teaching and research needs. | NA | 8 days | Fri 12/31/04 | Tue 1/11/05 | Fri 12/31/04 | No | $0.00 | No | 500 | 8 days | ||
| 6.9 | 71 | Identify client groups which may have different needs that are met by different service structures and processes. Determine whether to treat faculty & staff (or academic and administrative units) together or separately. Break into subproject teams if ne | NA | 4 days | Wed 1/12/05 | Mon 1/17/05 | Wed 1/12/05 | No | $0.00 | No | 500 | 4 days | ||
| 6.10 | 72 | Consider opportunities and demands posed by transition from NetWare to Windows-based file services. | NA | 4 days | Tue 1/18/05 | Fri 1/21/05 | Tue 1/18/05 | No | $0.00 | No | 500 | 4 days | ||
| 6.11 | 73 | Define expectations for client information fluency, active or passive problem resolution roles, recommended, supported, or nonrecommended software, hardware, and networking. | NA | 12 days | Mon 1/24/05 | Tue 2/8/05 | Mon 1/24/05 | No | $0.00 | No | 500 | 12 days | ||
| 6.12 | 74 | Recommend means of providing clear and consistent pathways and procedures for reporting, referring, monitoring and resolving user-reported problems, taking into account that IT client services are provided by a variety of organizations with varying needs, | NA | 12 days | Wed 2/9/05 | Thu 2/24/05 | Wed 2/9/05 | No | $0.00 | No | 500 | 12 days | ||
| 6.13 | 75 | Recommend means to reduce or accommodate the diversity of user computing platforms and configurations that must be supported, since this complicates the ability of support staff to respond efficiently and effectively to user-reported problems, properly in | NA | 40 days | Fri 2/25/05 | Thu 4/21/05 | Fri 2/25/05 | No | $0.00 | No | 500 | 40 days | ||
| 6.14 | 76 | Develop standards for acceptable asset quality and performance | NA | 8 days | Fri 4/22/05 | Tue 5/3/05 | Fri 4/22/05 | No | $0.00 | No | 500 | 8 days | ||
| 6.15 | 77 | Propose Future IT Client Services Delivery Framework for Employees. | NA | 12 days | Wed 5/4/05 | Thu 5/19/05 | Wed 5/4/05 | No | $0.00 | No | 500 | 12 days | ||
| 7 | 78 | Develop Management Presentation | NA | 64 days | Thu 6/23/05 | Tue 9/20/05 | Thu 6/23/05 | No | $0.00 | Yes | 500 | 64 days | ||
| 7.1 | 79 | Agree on presentation audience, format, organization and contents | NA | 4 days | Thu 6/23/05 | Tue 6/28/05 | Thu 6/23/05 | No | $0.00 | Yes | 500 | 4 days | ||
| 7.2 | 80 | Summarize and incorporate results of the major project work products. | NA | 12 days | Wed 6/29/05 | Thu 7/14/05 | Wed 6/29/05 | No | $0.00 | Yes | 500 | 12 days | ||
| 7.3 | 81 | Develop and review draft presentation with sponsor | NA | 4 days | Fri 7/15/05 | Wed 7/20/05 | Fri 7/15/05 | No | $0.00 | Yes | 500 | 4 days | ||
| 7.4 | 82 | Finalize presentation materials | NA | 12 days | Thu 7/21/05 | Fri 8/5/05 | Thu 7/21/05 | No | $0.00 | Yes | 500 | 12 days | ||
| 7.5 | 83 | Deliver presentation to senior management team members | NA | 8 days | Mon 8/8/05 | Wed 8/17/05 | Mon 8/8/05 | No | $0.00 | Yes | 500 | 8 days | ||
| 7.6 | 84 | Revise presentation and project work products as needed based on senior management team comments | NA | 16 days | Thu 8/18/05 | Thu 9/8/05 | Thu 8/18/05 | No | $0.00 | Yes | 500 | 16 days | ||
| 7.7 | 85 | Issue final project work products | NA | 8 days | Fri 9/9/05 | Tue 9/20/05 | Fri 9/9/05 | No | $0.00 | Yes | 500 | 8 days | ||
| 8 | 86 | Close the Project | NA | 24 days | Wed 9/21/05 | Mon 10/24/05 | Wed 9/21/05 | No | $0.00 | Yes | 500 | 24 days | ||
| 8.1 | 87 | Obtain Project Sponsor concurrence that all project objectives have been met | NA | 4 days | Wed 9/21/05 | Mon 9/26/05 | Wed 9/21/05 | No | $0.00 | Yes | 500 | 4 days | ||
| 8.2 | 88 | File all work products and templates in a common shared directory for future project use. Ensure appropriate project work products are available on the UVM web. | NA | 8 days | Tue 9/27/05 | Thu 10/6/05 | Tue 9/27/05 | No | $0.00 | Yes | 500 | 8 days | ||
| 8.3 | 89 | Identify work products to be maintained on a regular basis, and develop procedures and assign responsibilities for their ongoing update | NA | 4 days | Fri 10/7/05 | Wed 10/12/05 | Fri 10/7/05 | No | $0.00 | Yes | 500 | 4 days | ||
| 8.4 | 90 | Conduct and document summative ("lessons learned") evaluation session | NA | 4 days | Thu 10/13/05 | Tue 10/18/05 | Thu 10/13/05 | No | $0.00 | Yes | 500 | 4 days | ||
| 8.5 | 91 | Complete documentation in the Project Control Book | NA | 4 days | Wed 10/19/05 | Mon 10/24/05 | Wed 10/19/05 | No | $0.00 | Yes | 500 | 4 days |