Statement of Work (SOW) and Work Breakdown Structure (WBS)
PART 1''.docx
MEMO TO EXECUTIVE STAFF
|
|
Saltlake Defence Inc. |
Memo
To: |
Sales Manager |
From: |
Project Manager |
cc: |
Assistant Sales Manager |
Date: | August 20, 2015 |
Re: |
Project update |
|
|
|
Introduction:
The company has landed a contract to supply a backpack with built in refrigerated pouch and radio module. This project will commence on September 1, 2015 and run through March 1, 2017. The total budget is $1,500,000 which will be paid out in installments per milestone, the first payment on October 30, 2015 followed by a second payment on January 30, 2017 and final payment on May 30, 2017.
Customer:
Our customer is the US Army, focusing on two units; the Ground Forces and Special Operations. Each unit has requested for 100 units of the said items.
Initial program action items
The company must provide 100 units within twelve months after delivery of order. This will be followed by 50 units every three months until we meet the full order. The first delivery is due on September 1, 2016, the second deliver is due on December 1, 2016, and the final delivery on March 1, 2017.
Project Risks / Risk Mitigation strategies:
1. Inferior quality- enlist the best staff to do the project
2. Missing deadlines- the team leaders will ensure that their team completes the work in time
3. Late payment- the finance department will process payments in time to fund the project
4. Over-budgeting- the team can only purchase items that were budgeted for at proposal stage
5. Loss of future business- the head of sales will meet the client to discuss future opportunities
Memo Conclusion:
The senior management expects that teams working on this project use the resources wisely and deliver the products before or on the expected dates.
1
2
part 2 Backpacks.docx
Rasmussen College
Author Note
This paper is being submitted on November 28, 2016, for Joseph Morabito B362 Business Project Management course.
PROJECT SCOPE STATEMENT
Written by: Talesha Mcrae
Date:
Position Held:
Project Description
The Backpack project requires the design and development of backpacks with a refrigerated pouch including communications capabilities for US armed forces. The United States military continues to face challenges of carrying their meals including drinks while conducting ground and special operations in isolated locations. The current backpacks used by the US military lack refrigeration pouch and radio communications component, subsequently jeopardizing soldiers ability of communicating and facilitating recovery operations for troops injured in combat. Subsequentially, US Armed Force including Ground and Special Operation Forces have requested the design and advancement of a refrigerated backpacks equipped with radio capabilities in order to solve this problem and improve the effectiveness of their operations. The project specifications and requirements design, develop, and delivery high quality refrigerated backpacks to the United States. The project will be completed in milestones with the first phase involving delivery of xx amount of models and xx amount of units each thereafter.
Project Assumptions
The backpack project considers that manufacturers of raw materials will provide quality materials that will meet US armed forces strict criteria of durability as well as flexibility, considering the product will become utilized in economic extreme weather conditions and work environments. Accordingly, the project assumes that the United States military will remain willing to continue supplying adequate funding as discussed in the proposed award in order to deliver the final product within the pre-determined time period schedule. The project manager will ensure that project team have the required skills in design and will complete the project tasks within the timelines. All the project participants will abide by the recommendations outlined by the US military policies such as the need to maintain confidentiality on the information of the product design features.
Project Goals
The Backpacks project will certainly aim at providing the United States military with refrigerated backpacks which are important concerning their ground forces and specialized operations forces. The project will provide excellent, long lasting, lightweight functional backpacks which will ensure that men and woman in the military forces carry his or her supplies in refrigerated backpacks, subsequently beating the weather conditions and environmental difficulties during their operations. The project enhances the ability of armed forces while replenishing performance increasing their responsive responsibilities. The adjustable shoulder safety straps and the radio component will become less restrictive while maneuvering alongside soldier and ensure constant communication alongside peers situated within the battle field. In addition, identifying project specifications and requirements improve the morale of soldiers since the backpack is soft and light thus minimizing any unforeseen injuries to the users of these innovative backpacks. Furthermore, the project will guarantee that the backpacks are functionally re-usable and eco-friendly in order to meet sustainable adverse environmental effects.
Project Constraints
The project faces countless constraints that may hinder the design and development of high quality products at a cost effective refrigerated backpacks. The first constraint is the limited budgetary allocation in the proposed awards and inability of securing bank funding. An additional constraint is accosted with time frame constraints since the project must be accomplished at the end of one and half years. Therefore, the design will encompass controlling the environment within the backpack without the need of interfering the radio communications, creating additional constraints meeting project stage timeframes.
Project Limitation
The project faces the limitation of inadequate skilled personnel to undertake the design and development of the backpacks due to the project complexity and need to employment highly qualified project team. The second limitation is the lengthy vendor selection process and the requirement of seeking approval from the US military. Limitation will increase the overall project costs due to the high labor costs.
Project Millstones
The first delivery is due on September 1, 2016. The company must provide 100 units within twelve months after delivery of order. This will be followed by 50 units every three months until we meet the full order, the second deliver is due on December 1, 2016, and the final delivery on March 1, 2017.
Project Risks
The project faces the risk of underestimation of the design and development costs than proposed award due to lack of accurate estimation of the material costs and unavailability of data on the costs of similar projects. Another inherent risk is the possibility of not meeting the delivery schedule and time frame. The project manager will avoid this risk by developing an action plan and a project schedule guideline that outlines the lists of project activities and their estimated time period requirements.
CUSTOMER REVIEW
· 5 out of 5 - Great service! - Anonymous
Everything was great and everyone was pleasant and helpful! I will be ordering more as the bag get older.
Recommend: Yes, I would recommend this to a friend.
Chris • 5 out of 5 - Great service!
Seems to be well made. The initials look good. The cooler is taller than I thought it would be but they look very nice.Recommend: Yes, I would recommend this to a friend.
· 5.0 5 out of 5 - backpack cooler -
Anonymous bought for my fiancée while it was on sale. he loves it. I did not get it monogrammed. used it immediately. put some freezer cold packs in the cooler portion and kept his drinks cold. very satisfied. Recommend: Yes, I would recommend this to a friend.
· 5.0 5 out of 5 - Coolest Gift Ever - April 19, 2016
Sherry (Monroe)
This product exceeded our expectations! Very cool and unique gift for anyone for any occasion! Perfect! We will be ordering more! Recommend: Yes, I would recommend this to a friend.
part 2 Backpacks.xlsx
Course Project Schedule
| Project Title | Project Schedule | |||||||||||||||||||||||||
| Start Date | Sep 1, 2015 | |||||||||||||||||||||||||
| Month | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | ||
| Sep | Oct | Nov | Dec | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Notes | ||
| 42248.0 | 42278.0 | 42309.0 | 42339.0 | 42370.0 | 42401.0 | 42430.0 | 42461.0 | 42491.0 | 42522.0 | 42552.0 | 42583.0 | 42614.0 | 42644.0 | 42675.0 | 42705.0 | 42736.0 | 42767.0 | 42795.0 | 42826.0 | 42856.0 | 42887.0 | 42917.0 | 42948.0 | |||
| Phase | Project Completion | |||||||||||||||||||||||||
| One | ||||||||||||||||||||||||||
| Phase | ||||||||||||||||||||||||||
| Two | ||||||||||||||||||||||||||
| Product Design Phase | ||||||||||||||||||||||||||
| Initial Product Test | ||||||||||||||||||||||||||
| Final Test | ||||||||||||||||||||||||||
| Phase | ||||||||||||||||||||||||||
| Three | ||||||||||||||||||||||||||
Project Award Sept. 1, 2015
First Delivery Sept. 1, 2015
Second Delivery Dec. 1, 2015
Third (Final) Delivery March 1, 2015
First Milestone Payment (from Customer) Oct. 30, 2015
Second Milestone Payment (from Customer) Jan. 30, 2017
Third Milestone Payment (from Customer) May. 30, 2017
Initial Program Review (PR) Nov. 16, 2015
Program Review (PR) May. 16, 2016
Program Review (PR) Nov. 16, 2016
Design Review
Production begins
Week
| Project Title | Project Schedule | |||||||||||||||||||||
| Start Week | Jan 5, 2014 | |||||||||||||||||||||
| Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | ||
| Starting | Jan | Jan | Jan | Jan | Feb | Feb | Feb | Feb | Mar | Mar | Mar | Mar | Mar | Apr | Apr | Apr | Apr | May | May | May | Notes | |
| 5 | 12 | 19 | 26 | 2 | 9 | 16 | 23 | 2 | 9 | 16 | 23 | 30 | 6 | 13 | 20 | 27 | 4 | 11 | 18 | |||
| Phase | ||||||||||||||||||||||
| One | ||||||||||||||||||||||
| Phase | ||||||||||||||||||||||
| Two | ||||||||||||||||||||||
| Phase | ||||||||||||||||||||||
| Three | ||||||||||||||||||||||
Help
| HELP | |||
| http://www.vertex42.com/ExcelTemplates/project-schedule-template.html | © 2014 Vertex42 LLC | ||
| About this Template | |||
| This project schedule can be used to create a basic timeline for your project. | |||
| Try the Vertex42 Gantt Chart Template if you want to something more automated for creating and managing your project schedule. (See the reference below). | |||
| How to use this Template | |||
| 1) | Enter your project start date in cell E3. This will automatically update the dates in rows 6 and 7. | ||
| 2) | Add tasks: Choose what phase (row) and week (column) the task will start and enter the task title into that cell. Then fill in the background color of the cells to indicate how long the task will take to complete. | ||
| If you would like to show the completion status of a task, you can fill the background with a darker or different color (see the Sample worksheet for an example). | |||
| 3) | Add a milestone: If you'd like to show a milestone, you can create a vertical "line" in the schedule by changing the cell borders and the background fill (see the Sample worksheet). | ||
| Note: In the sample worksheet, the Project End milestone was created by merging cells, turning on Wrap Text, and pressing Alt+Enter after each letter to force each letter onto a new line. | |||
| Additional Help | |||
| The link at the top of this worksheet will take you to the web page on vertex42.com that talks about this template. | |||
| REFERENCES | |||
| SEE ALSO | Vertex42.com: Gantt Chart Template | ||
| SEE ALSO | Vertex42.com: Project Management Templates | ||
| TIPS | Vertex42.com: Spreadsheet Tips Workbook | ||
©
| Project Schedule Template | |
| By Vertex42.com | |
| http://www.vertex42.com/ExcelTemplates/project-schedule-template.html | |
| © 2014 Vertex42 LLC | |
| This spreadsheet, including all worksheets and associated content is considered a copyrighted work under the United States and other copyright laws. | |
| Do not submit copies or modifications of this template to any website or online template gallery. | |
| Please review the following license agreement to learn how you may or may not use this template. Thank you. | |
| See License Agreement | |
| http://www.vertex42.com/licensing/EULA_privateuse.html | |
| Do not delete this worksheet. If necessary, you may hide it by right-clicking on the tab and selecting Hide. | |
Week 2 unexpected events
| Date of Event | |
| Oct. 15, 2015 | 1. Customer Notifies you that the first milestone payment will be three months delayed. What is your course of action? |
| We first secure ourt product by enteringg into an agrement stating that our organizatin will be entitled to a 20% weekly surcharge, delivery quantities will be half the request and moving forward all payments will be made prior to the completions of product ordering. 3. Late payment- the finance department will process payments in time to fund the project | |
| March 15, 2016 | 2. The material pattern for the backpack will not be available to meet your initial production start date. What is your course of action? |
| This materials for lot available at the initial production of backpacks then now the time to devise alternative plans incorporating differentiating suppliers which will ultimately allow the project to stay with in completion deadlines. | |
| May 15, 2016 | 3. Customer notifies you they would like to increase the initial delivery from 100 backpacks to 150. What is your course of action? |
| The company will have the increase production by 50% to meet the new demands however this is contingent upon account credibility and financial worthiness. Additionally course of action will require devising work breakdown structures and identifying possible slacks and scope creep. | |
Week 5 unexpected events
| Date of Event | |
| March 1, 2016 | 1. The project engineering team discovers the refrigerated module is too large for the designed refrigerated backpack pouch. What is your course of action? |
| The only course of action is to find alternative supplier that can meet the demands within specifications that we are looking for. The purpose for this course of action is because the backpacks dimensional weights is a crucial factor for soldiers, therefore, increasing the size of the bag structure is not an option | |
| May 27, 2016 | 2. The subcontractor assigned to build the radio module for the backpack has shut down. What is your course of action? |
| Two alternative course of actions for this situation. One we find a local dealer that possesses the certifications for the equipment that we are working with. If a local dealer cannot be located alternative course would be to outsource parts and or the refrigeration unit alone. | |
WBS template example for part 3.xlsx
Example
| WBS | Title | Description | Start Date | End Date | Total estimated days | Point of Contact (POC) | ||
| 1.0 | Develop Work Breakdown Structure (WBS) | Description of work to be completed / milestone | 1/5/16 | 1/5/16 | 1 | |||
| 1.1 | Review customer statement of work (SOW) | Read and review the statement of work | 1/6/16 | 1/9/16 | 3 | Project Manager | ||
| 1.1.1 | Identify all project deliverables and milestones | Highlight and identify all project deliverables and milestones associtated with the project | 1/6/16 | 1/9/16 | 0 | Project Manager | ||
| 1.2 | Forward a copy of the customer statement of work to the project team | Forward a copy of the customer statement of work to all project team members | 1/10/16 | 1/10/16 | 1 | Project Manager | ||
| 1.2.1 | Begin development of the WBS | Develop the WBS | 1/10/16 | 1/10/16 | 1 | Project team | ||
| 1.3 | Project team review | Set up a SOW team review with the project team | 1/13/16 | 1/13/16 | 1 | Project team | ||
| 1.3.1 | Identify all top level work packages | Highlight and identify all top level milestones / deliverables | 1/14/16 | 1/15/16 | 1 | S. Johnson | ||
| 1.4 | Identify all lower level work packages | identify all work associated with the top level milestones | 1/14/16 | 1/15/16 | 1 | M. Jones | ||
| 1.4.1 | Project team approval | Set up a project team meeting for WBS review / approval | 1/17/16 | 1/17/16 | 1 | Project team | ||
Proj. Work Breakdown Structure
| WBS | Title | Description | Start Date | End Date | Total estimated days | Point of Contact (POC) | ||
| 1.0 | ||||||||
| 1.1 | ||||||||
| 1.1.1 | ||||||||
| 1.2 | ||||||||
| 1.2.1 | ||||||||
| 1.3 | ||||||||
| 1.3.1 | ||||||||
| 1.4 | ||||||||
| 1.4.1 | ||||||||
| 2.0 | ||||||||
| 2.1 | ||||||||
| 2.1.1 | ||||||||
| 2.2 | ||||||||
| 2.2.1 | ||||||||
| 2.3 | ||||||||
| 2.3.1 | ||||||||
| 2.4 | ||||||||
| 2.4.1 | ||||||||
| 3.0 | ||||||||
| 3.1 | ||||||||
| 3.1.1 | ||||||||
| 3.2 | ||||||||
| 3.2.1 | ||||||||
| 3.3 | ||||||||
| 3.3.1 | ||||||||
| 3.4 | ||||||||
| 3.4.1 | ||||||||
| 4.0 | ||||||||
| 4.1 | ||||||||
| 4.1.1 | ||||||||
| 4.2 | ||||||||
| 4.2.1 | ||||||||
| 4.3 | ||||||||
| 4.3.1 | ||||||||
| 4.4 | ||||||||
| 4.4.1 | ||||||||
| 5.0 | ||||||||
| 5.1 | ||||||||
| 5.1.1 | ||||||||
| 5.2 | ||||||||
| 5.2.1 | ||||||||
| 5.3 | ||||||||
| 5.3.1 | ||||||||
| 5.4 | ||||||||
| 5.4.1 | ||||||||
| 6.0 | ||||||||
| 6.1 | ||||||||
| 6.2.1 | ||||||||
| 6.2 | ||||||||
| 6.2.1 | ||||||||
| 6.3 | ||||||||
| 6.3.1 | ||||||||
| 6.4 | ||||||||
| 6.4.1 | ||||||||
| 7.0 | ||||||||
| 7.1 | ||||||||
| 7.1.1 | ||||||||
| 7.2 | ||||||||
| 7.2.1 | ||||||||
| 7.3 | ||||||||
| 7.3.1 | ||||||||
| 7.4 | ||||||||
| 7.4.1 | ||||||||
| 8.0 | ||||||||
| 8.1 | ||||||||
| 8.1.1 | ||||||||
| 8.2 | ||||||||
| 8.2.1 | ||||||||
| 8.3 | ||||||||
| 8.3.1 | ||||||||
| 8.4 | ||||||||
| 8.4.1 | ||||||||
| 9.0 | ||||||||
| 9.1 | ||||||||
| 9.1.1 | ||||||||
| 9.2 | ||||||||
| 9.2.1 | ||||||||
| 9.3 | ||||||||
| 9.3.1 | ||||||||
| 9.4 | ||||||||
| 9.4.1 | ||||||||
| 10.0 | ||||||||
| 10.1 | ||||||||
| 10.1.1 | ||||||||
| 10.2 | ||||||||
| 10.2.1 | ||||||||
| 10.3 | ||||||||
| 10.3.1 | ||||||||
| 10.4 | ||||||||
| 2.4.1 |