Scribd
Upload
309 views

Sample Work Breakdown Structure

This project aims to train over 500 employees on a new student management system (SMS) for an online university. The work breakdown structure outlines the key deliverables of role mapping employees' access in the SMS, conducting training needs analysis and usability testing, and providing ongoing support. It details the phases of preparation, execution, production launch, and long-term support in 3 main sections with subsections defining specific tasks.

Uploaded by

George Emmerich
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
309 views

Sample Work Breakdown Structure

This project aims to train over 500 employees on a new student management system (SMS) for an online university. The work breakdown structure outlines the key deliverables of role mapping employees' access in the SMS, conducting training needs analysis and usability testing, and providing ongoing support. It details the phases of preparation, execution, production launch, and long-term support in 3 main sections with subsections defining specific tasks.

Uploaded by

George Emmerich
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Sample Work Breakdown Structure

This project's scope statement focuses on training over 500 employees on a new student management system that will manage all student information and guide all administrative process for an online, private postsecondary institution. The desired deliverables are: 1. To ensure each employee has the correct access into the SMS (role mapping) 2. To discover training based upon usability testing findings 3. To perform needs analysis of training staff size and robustness of training materials Although the true scope of integrating a new student management system into the institution's operating model is far more robust, I am focusing squarely on the training and human resources quadrant of this project. The table below illustrates the work breakdown structure for training the staff and ensuring continuing support following the production launch.

Main Deliverable 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 1 - Role Mapping 2 - Training

WBS Phase 1.1 - Business Process Roles 1.1 - Business Process Roles 1.1 - Business Process Roles 1.1 - Business Process Roles 1.1 - Business Process Roles 1.2 - Permission groups in SMS 1.2 - Permission groups in SMS 1.2 - Permission groups in SMS 1.2 - Permission groups in SMS 1.2 - Permission groups in SMS 1.2 - Permission groups in SMS 2.1 Preparation

WBS Activity 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.2.6 2.1.1

Description (if applicable) Assign staff business process roles Validate Business Process Roles Update staff business process roles Approve business process roles Forward staff role groups to programmers for end-user authentication and permission groups Validate end-user permission groups against business process needs Assign staff to permission groups Assemble business process diagonal validation team to perform duty-specific procedures in SMS Review findings from validation team Analyze findings with campus administration Forward any changes to permission groups to programmers Perform cost analysis

2 - Training 2 - Training 2 - Training 2 - Training 2 - Training

2.1 Preparation 2.1 Preparation 2.1 Preparation 2.1 Preparation 2.1 Preparation

2.1.2 2.1.3 2.1.4 2.1.5 2.1.6

Identify training team and assemble Secure resources and facilities Develop materials Map schedule against business needs Using materials and resources, schedule sessions against functional user-groups and business needs. Each training breakout session should include only relevant staff groups. Meet with training team for project execution Send out meeting requests to staff members as appropriate Take attendance at each breakout session; reschedule critical absent staff members as necessary Distribute survey at the end of each session and evaluate feedback Identify "super-users" from breakout sessions Modify training team into support team Meet with directors, support team, IT division, programmers, and "super-users" to determine support protocol/ process (including issue escalation process) Meet with all staff to prepare for production launch and reinforce support process Launch new SMS Reinforce support process (and escalation process) Track support issues and analyze data Develop refresher training and continuing training based on support data and issue analysis Reinforce the issue process Continue ongoing refresher training and track problem areas for concentrated training efforts Run post-mortem on project

2 - Training 2 - Training 2 - Training

2.2 - Execution 2.2 - Execution 2.2 - Execution

2.2.1 2.2.2 2.2.3

2 - Training 2 - Training 2 - Training 3 - Launch Production

2.2 - Execution 2.2 - Execution 2.2 - Execution 3.1 Preparation

2.2.4 2.2.5 2.2.6 3.1.1

3 - Launch Production 3 - Launch Production 4 - Support 4 - Support 4 - Support 4 - Support 4 - Support 4 - Support

3.1 Preparation 3.2 - Execution 4.1 - Execution 4.1 - Execution 4.1 - Execution 4.2 - Sustain/ Governance 4.2 - Sustain/ Governance 4.2 - Sustain/ Governance

3.1.2 3.2.1 4.1.1 4.1.2 4.1.3 4.2.1 4.2.2 4.2.3

You might also like