| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | WBS and Schedule (Major Milestones are highlighted in gray) | |||||||||||||||||||||||||
2 | ||||||||||||||||||||||||||
3 | Phase | Section | Task | Description | Deliverable | Resource | Cost | Completion Date | ||||||||||||||||||
4 | 1: Project Initiation | 1.1 | Stakeholder identification | Identifies stakeholders and point of contact (POC) for each stakeholder team | Email to all stakeholders with identified point of contact for each stakeholder team | Project Manager, stakeholders and stakeholder teams | PM 1 hour Stakeholders (only reply to email) | March 1st | ||||||||||||||||||
5 | 1.2 | Stakeholder meeting | Creates goals and objectives with stakeholders Creates initial timeline after consultation with stakeholders | PPT of High Level Overview of the project goals | Project Manager, stakeholders and stakeholder teams | 1 hour meeting | March 1st | |||||||||||||||||||
6 | 1.3 | Communication Plan | Meeting to review and discuss project communication plan | Email Document outlining process of communication | Project Manager, stakeholders and stakeholder teams | PM 1 hour to create PM and stakeholders 1 hour meeting | March 2nd | |||||||||||||||||||
7 | 1.4 | Project Charter Created | Summary of the project with high level scope, budget, project goals, stakeholder roles and major milestones identified | Project Charter Document | Project Manager | 40 hours | March 7th | |||||||||||||||||||
8 | 1.5 | Discussion of Project Charter | Project charted discussed with stakeholders and feedback given and taken | Amended Project Charter based on feedback from stakeholders and project team | Project Manager, stakeholders and stakeholder teams | 1 hour meeting | March 8th | |||||||||||||||||||
9 | 1.6 | Approval of Project Charter | Director of HR reviews and approves Project Charter | Approved Project Charter | Director of HR | March 10th | ||||||||||||||||||||
10 | ||||||||||||||||||||||||||
11 | 2: Project Planning | 2.1 | Governance Structure | Lines of reporting, individual and team responsibilities clarified | Governance structure | Project Manager, stakeholders and stakeholder teams | PM: 2 hours prepare Stakeholders and stakeholder teams: 1 hour meeting | March 14th | ||||||||||||||||||
12 | 2.2 | Learning Needs Survey Created | Online survey created to access learning needs of content creators | Online survey | L&D Team member #1 | 3 hours | March 15th | |||||||||||||||||||
13 | 2.3 | Learned Needs Survey sent | Online survey | L&D Team member #1 | March 17th | |||||||||||||||||||||
14 | 2.4 | Existing Learning resources | Existing learning resources that can be used are identified | List of resources that can be used | L&D Lead L&D Team member #2 | L&D Lead: 20 hours L&D Team member #2: 80 hours | March 28th | |||||||||||||||||||
15 | 2.5 | Learning Needs Compiled | Learning needs identified across departments through survey analysis and discussion with Content Creator teams | Document of Learning needs compiled and assessed | L&D Team Member #1 and Stakeholder teams POC | L&D Team member #1: 160 hours Stakeholder teams POC: 10 hours each (30 hours total) | March 28th | |||||||||||||||||||
16 | 2.6 | Learning Path | Learning Path created based on learning needs | Learning Path template | L&D Lead | 20 hours | March 31st | |||||||||||||||||||
17 | 2.7 | Planning Discussion Meeting | Product requirements, UI/UX requirements, learning resources and learning path discussed. Potential Go-live date established Determine success criteria | Initial UI/UX and Product Requirements given | Project Manager, stakeholders and stakeholder teams | 3 hours meeting | April 4th | |||||||||||||||||||
18 | 2.8 | LMS Design Planning | Discussions, planning, and design of LMS | LMS Mock-Up | Product Lead Product #1 Product #2 UI/UX Lead UI/UX #1 L&D Lead | Product Lead: 20 hours Product #1: 40 hours Product #2: 40 hours UI/UX Lead: 20 hours UI/UX #1: 40 hours L&D Lead: 10 hours | April 8th | |||||||||||||||||||
19 | 2.9 | Project Scope Discussion | Scope Modified based on product UI/UX requirements | WBS Product UI/UX requirements accepted | Project Manager, stakeholders and stakeholder teams | PM: 10 hours (create WBS) Stakeholder and stakeholder teams: 2 hours meeting | April 11th | |||||||||||||||||||
20 | 2.10 | LMS Design Discussion | Presentation of LMS design | PPT of LMS Mock-up design and functionality | Project Manager, stakeholders and stakeholder teams | 1 hour meeting | April 11th | |||||||||||||||||||
21 | 2.11 | Risk Management | Risk register created and potential sources of risk identified | Risk Management Plan | Project Manager, stakeholders and stakeholder teams | PM: 20 hours | April 15th | |||||||||||||||||||
22 | 2.12 | New Resource Outline | New resource outline created based on learning path and learning needs | Excel outline of new learning resource with identified challenge for each course | L&D Lead L&D Team Member #3 | L&D Lead 20 hours L&D Team member #3: 160 hours | April 29th | |||||||||||||||||||
23 | 2.13 | Learning Resource build timeline | Timeline for resources created based on outline of new resources | Excel Timeline | L&D Lead | 3 hours | April 29th | |||||||||||||||||||
24 | 2.14 | Branding Strategy | Branding strategy for new learning resources created | Brand Guidelines | Marketing: Branding Expert | 160 hours | April 29th | |||||||||||||||||||
25 | 2.15 | Project Teams | Functional managers (L&D, Product, UI/UX) will determine who will do what | Personnel | Project Team | 32 hours (4 hours a week for 8 weeks) | Ongoing | |||||||||||||||||||
26 | 2.16 | OPPM | Meeting to discuss project plain and method for bi-weekly (twice a month) updates/check-in | OPPM | Project Manager, stakeholders and stakeholder teams | 4 hours meetings | Every other Tuesday from March 8th at 11am | |||||||||||||||||||
27 | 2.17 | Project evaluation survey plan | Discuss how to determine if project was a success. | Document on types of survey and interview questions to ask and what information should be ascertained. | Project Manager, stakeholders and stakeholder teams | 1 hour meeting | May 2nd | |||||||||||||||||||
28 | 2.18 | User feedback survey created | Survey questions created to the users to determine their level of satisfaction with the functionality and learning resources | Online user survey | Project Manager L&D Team Lead Product Team Lead | Project Manager: 1 hour L&D Team Lead: 1 hour Product Team Lead: 1 hour | May 3rd | |||||||||||||||||||
29 | 2.19 | Project manager evaluation survey created | Survey questions created to determine the project managers work | Online survey | PMO Lead | PMO Lead: 1 hour | May 3rd | |||||||||||||||||||
30 | 2.20 | Stakeholder evaluation survey created | Survey questions created to provide feedback on stakeholders | Online survey | Project Manager | Project Manager 1: hour | May 3rd | |||||||||||||||||||
31 | 2.21 | Content Creator Team lead and expert interview questions created | Feedback questions created to determine efficacy of The Learning Center | Interview Questions | Project Manager | Project Manager: 2 hours | May 3rd | |||||||||||||||||||
32 | 2.22 | Approval | Project plan approved and agreed upon by all stakeholders | All stakeholders | 1 hour meeting | May 4th | ||||||||||||||||||||
33 | ||||||||||||||||||||||||||
34 | 3: Project Execution | 3.1 | Project kick-off meeting | Approved plan for project announced kick-off meeting | PPT with rough timeline, goals and objectives of the project and stakeholders involved | Project Manager, stakeholders and stakeholder teams | 2 hour meeting | May 4th | ||||||||||||||||||
35 | 3.2 | Monitor Stakeholder needs | PM deals with stakeholder needs as necessary | Project Manager, stakeholders and stakeholder teams | PM: 48 hours (4 hours a week for 12 weeks) | |||||||||||||||||||||
36 | 3.3 | Check-in and Impact analysis | Ongoing weekly check-in for this phase of the project | OPPM | Project Manager, stakeholders and stakeholder teams | 12 hours meetings | Every other Tuesday from May 3rd at 11am | |||||||||||||||||||
37 | 3.4 | Stakeholder management plan | Stakeholder management Plan created | Stakeholder Management Plan | Project Manager, stakeholders and stakeholder teams | PM: 40 hours to create 1 hour meeting | May 13th | |||||||||||||||||||
38 | 3.5 | Launch Plan | Plan and dates for release of LMS agreed | Launch Plan Outline | Project Manager, stakeholders and stakeholder teams | 2 hour meeting | May 20th | |||||||||||||||||||
39 | 3.6 | Risk Mitigation | Risk register updated on an ongoing basis and risks handled appropriately | Risk Register updated | Project Manager, stakeholders and stakeholder teams | Project Manager: 36 hours | ||||||||||||||||||||
40 | 3.7 | LMS Build | Product team with UI/UX build the LMS | The Learning Center learner interface and LMS upload system | Product Team and UI/UX | Product Team Lead: 80 hours Product #1: 480 hours Product #2: 480 hours UI/UX #1: 80 hours | August 26th | |||||||||||||||||||
41 | 3.8 | Learning Resources Build | Learning Resources Content for LMS are created | Learning Resources | L&D Team | L&D Lead: 480 hours L&D #1: 480 hours L&D #2: 480 hours L&D #3: 480 hours | August 26th | |||||||||||||||||||
42 | 3.9 | Learning resource feedback | Feedback on learning resources provided by Stakeholder experts | Learning Resources with feedback | CC Experts | CC (Education) Expert: 10 hours CC (Entertainment) Expert: 10 hours CC (Sales) Expert: 10 hours | Ongoing (See resource timeline below) | |||||||||||||||||||
43 | 3.10 | LMS Training | Training to L&D team on material upload process | Training PPT | Product Team #1 L&D Team | 1 hour meeting | August 25th | |||||||||||||||||||
44 | 3.11 | LMS MVP launch | Test launch of LMS | Minimum viable product (MVP) system | Product Team #1 | August 26th | ||||||||||||||||||||
45 | 3.12 | Learning Center MVP launch | Test launch of Learning Center user interface | Minimum viable product (MVP) Learning Center | Product Team #2 | August 26th | ||||||||||||||||||||
46 | 3.13 | LMS Ready to Launch | LMS bugs found and fixed | Finished LMS | Product Team #1 L&D Team | Product Team #1: 50 hours L&D Lead: 10 hours L&D #1: 10 hours L&D #2: 10 hours L&D #3: 10 hours | September 9th | |||||||||||||||||||
47 | 3.14 | Learning Center Ready to Launch | Learning Center bugs found and fixed | Launch ready Learning Center | Product Team #2 L&D Team | Product Team #2: 50 hours L&D Lead: 10 hours L&D #1: 10 hours L&D #2: 10 hours L&D #3: 10 hours | September 9th | |||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | 4: Closeout | 4.1 | Resource completion and Resource Upload | Resources uploaded to The Learning Center | L&D Team | L&D Lead: 5 hours L&D #1: 10 hours L&D #2: 10 hours L&D #3: 10 hours | September 13th | |||||||||||||||||||
50 | 4.2 | LMS Launch | Full release of LMS and Learning Center user interface | The Learning Center | Product Team Lead | Product Team Lead: 1 hour | September 15th | |||||||||||||||||||
51 | 4.3 | Project manager evaluation survey sent | PMO Lead | September 16th | ||||||||||||||||||||||
52 | 4.4 | Stakeholder evaluation survey sent | Project Manager | September 16th | ||||||||||||||||||||||
53 | 4.5 | User feedback survey sent | L&D Team Lead | September 16th | ||||||||||||||||||||||
54 | 4.6 | Interviews with Content Creator team leads and experts | Interview Questions with answers and feedback | Project Manager | Project Manager: 3 hours CC Team leads: 1 hour each (3) CC Expert: 1 hour each (3) | September 20th | ||||||||||||||||||||
55 | 4.7 | User feedback survey analyzed | Determine how users like the resources and functionality in order to make future changes | Change log document and recommendations for next steps | L&D Team Lead Product Team Lead | L&D Team Lead: 5 hours Product Team Lead: 5 hours | September 23rd | |||||||||||||||||||
56 | 4.8 | Project evaluation surveys complete | Determine the project overall in terms of satisfaction, communication and success | Project Manager, stakeholders and stakeholder teams | Project Manager: 4 hours | September 28th | ||||||||||||||||||||
57 | 4.9 | Final report | Compile the results of the user feedback survey and project evaluation survey. Create a list of recommendations for next Learning Center project | Learning Center 2.0 recommendations | Project Manager L&D Lead Product Lead | Project Manager: 4 hours L&D Lead: 4 hours Product Lead: 4 hours | October 5th | |||||||||||||||||||
58 | ||||||||||||||||||||||||||
59 | Learning Resource Timeline | |||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||
61 | Course | Course Name | L&D Creator | Planning with CC Expert/HR | Rough Draft | Feedback on Rough Draft from CC expert/HR | Feedback on Rough Draft from L&D Lead/Peer review | Final Draft | ||||||||||||||||||
62 | Onboarding Course | OC | L&D Lead | May 5th | June 2nd | June 9th | June 16th | June 23rd | ||||||||||||||||||
63 | CC Ent. Novice Level | CC Ent. 1 | L&D #1 | May 5th | May 19th | May 23rd | May 25th | May 27th | ||||||||||||||||||
64 | CC Ent. Advanced beginner Level | CC Ent. 2 | May 30th | June 13th | June 15th | June 17th | June 21st | |||||||||||||||||||
65 | CC Ent. Competent Level | CC Ent. 3 | June 22nd | July 6th | July 8th | July 11th | July 13th | |||||||||||||||||||
66 | CC Ent. Proficient Level | CC Ent. 4 | July 14th | July 28th | August 1st | August 3rd | August 5th | |||||||||||||||||||
67 | CC Ent. Expert Level | CC Ent. 5 | August 8th | August 22nd | August 24th | August 29th | August 31st | |||||||||||||||||||
68 | CC Edu. Novice Level | CC Edu. 1 | L&D #2 | May 5th | May 19th | May 23rd | May 25th | May 27th | ||||||||||||||||||
69 | CC Edu. Advanced Beginner Level | CC Edu. 2 | May 30th | June 13th | June 15th | June 17th | June 21st | |||||||||||||||||||
70 | CC Edu. Competent Level | CC Edu. 3 | June 22nd | July 6th | July 8th | July 11th | July 13th | |||||||||||||||||||
71 | CC Edu. Proficient Level | CC Edu. 4 | July 14th | July 28th | August 1st | August 3rd | August 5th | |||||||||||||||||||
72 | CC Edu. Expert Level | CC Edu. 5 | August 8th | August 22nd | August 24th | August 29th | August 31st | |||||||||||||||||||
73 | CC S&PP Novice Level | CC S&PP 1 | L&D #3 | May 5th | May 19th | May 23rd | May 25th | May 27th | ||||||||||||||||||
74 | CC S&PP Advanced Beginner Level | CC S&PP 2 | May 30th | June 13th | June 15th | June 17th | June 21st | |||||||||||||||||||
75 | CC S&PP Competent Level | CC S&PP 3 | June 22nd | July 6th | July 8th | July 11th | July 13th | |||||||||||||||||||
76 | CC S&PP Proficient Level | CC S&PP 4 | July 14th | July 28th | August 1st | August 3rd | August 5th | |||||||||||||||||||
77 | CC S&PP Expert Level | CC S&PP 5 | August 8th | August 22nd | August 24th | August 29th | August 31st | |||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 | ||||||||||||||||||||||||||