Norfolk State University M2 SOW Work Breakdown Structure

/ Uncategorized / By

Description

create a work breakdown structure (WBS) based on the M2 SOW. You will also do a risk analysis to identify all risks that might put your project in jeopardy.
– use the guide to give you detailed instructions about how to complete the risk analysis and create the WBS.Create the WBS from the SOW that you created in the last module. Remember, your WBS can be in outline or graphical form. Note: there is no assignment template for the WBS.
Create risk analysis please use the risk analysis template.M3 Project Guide (WBS and Risk Analysis) #
In the last module, you created the SOW and specified all the activities the team needs to do to
complete the project. Now it’s time for you to do two more tasks: 1) create a work breakdown
structure (WBS) and (2) analyze risks that might put your project in jeopardy. Note that you must do
your WBS first, and then do your risk analysis.
Work Breakdown Structure
Now that you have your SOW, you can create your WBS. Sometimes the hardest part of doing this is
getting started. A good way to begin is to review the work you’ve already done during project
definition. Then read about the required structure of the WBS and grading criteria below. Note: You
will not use a template to create your WBS because you have a couple of options when creating it.
For instance, you can use MS PowerPoint or MS Word. You can also create it in graphical or
indented representation form.
Style Requirements
In general, there are several options for WBS formats. However, for this project, you will follow
specific WBS style requirements. You will graded based on your adherence to the following
requirements:
.
• Software: You may use either MS PowerPoint or MS Word.
• Structure: The WBS can be either in graphical or indented representation.
• Notes: If you have notes, commentary, or assumptions that you want to be considered as part
of your deliverable, please include them using the Notes feature of PPT or directly in MS Word.
• WBS style: Your WBS represents a hierarchical representation of the work.
• Notation: Use dot-number notation.
• Summary tasks: Use nouns (or verbs) for summary tasks.
• Work package format: Use action verb-object format for work packages.
• Task titles format: Use concise titles for all tasks that stand on their own even when taken out
of the WBS context (e.g., don’t have titles such as Write Report. Instead, you should title it
Draft Market Research Report). Remember that when you do any project of any size, you will
be using a software tool (e.g., MS Project)—and these tools have associated databases so
you can capture additional information about each task. You don’t need to capture it all in a
long task title.
• Flow: Make sure the WBS follows logically from your SOW.
• Charge Number: Provide a charge number such that all the workers on a project can see a
work package they can charge their time to—including a PM task for the work of the project
manager.
Last updated on 14 August 2017 !
•
•
•
•
•
Page 2 of 2
Value: The WBS should add value, elaborating from your starting point, the SOW.
Objective: Record all of the needed work elements to accomplish the objective of the project.
Break down: When you “break down” a task, be sure to note if it is two or more descendent
tasks.
Balance: There should be a sense of balance in the depth and breadth of your WBS—roughly
analogous to an org chart (e.g., it would be unusual to have structures such as one node
breaking down into 25 direct descendants, or an entirely binary tree in which every node
breaks down into exactly two descendants).
Proportionality: There is a sense of proportionality in the number of work packages in the
WBS and the size of the project. For this project, 10–25 work packages are appropriate.
Risk Analysis
By analyzing risks that you might experience throughout your project, you can uncover problems
before they actually damage the project. The Risk Analysis template provides a starting point for your
own systematic risk management process and gives you a way of tracking risks.
Brainstorm and come up with every reasonable risk. Then complete the M3 Project (Risk Analysis)
Template, completing the following information:
•
•
•
•
•
•
•
Risk ID: A unique identifier
WBS: WBS number of the task(s) related to this risk
Rank: How important is this risk relative to others? Rank with 1=highest. No risks have the
same rank.
Date found: Date risk became known, mm/dd/yy
Assigned to: Person who is assigned to manage this risk
Description: High level description of risk event, impact, and probability
Strategy: What will be done to reduce the probability, impact, or both?
M2 Template (SOW)
Instructions: Follow the steps below to complete the SOW. Delete all red text in the template and
insert your own text in black.
Steps
1. In the Project Manager section, list your name.
2. In the Date of Original SOW section, list the date.
3. Complete the Revision History table. In this table, enter the revision date, the name of the
person who will do the revisions, the name of the person who will approve the revisions, and a
description of each change.
4. Keep the Project Objective the same. You do not need to alter this section.
5. Keep the Period of Performance the same. You do not need to alter this section.
6. In the Major Activities and Expected Time Period section, list all the major activities that you
must do to complete the project. Then assign an estimate for when your team will complete
each of these activities.
7. In the Out of Scope Activities section, list all out of scope activites for this project.
8. In the Budget/Cost Estimates section, list cost estimates for all types of costs.
9. In the Schedule Overview section, list estimated project completion date, all major milestones
with estimated dates of completion, and all external milestones with estimated dates of
completion.
10. In the Impact of Late Delivery section, list all the ways in which the project will be affected if it
is delivered late.
11. In the Deliverables and Acceptance Criteria section, list all major deliverables, as well as the
criteria by which those deliverables will be accepted.
12. In the Measures of Success for Project section, list all the ways in which you intend to
measure the project’s success.
13. In the Assumptions section, list all the assumptions that you have about the project.
14. In the Major Risks section, list all the major risks related to the project.
15. In the Stakeholder Register section, list all the stakeholders and their roles, as well as their
major responsibility or contribution.
Last updated on 13 February 2023
Page 2 of 6
Revision Histor :
Revision Date
Revised B
2/4/23
2/5/23
Dan
Carla
pproved B
Elisa
Nicole
Description of Chan e
Creation of bud et
Modification of dates o
completion
Project Objective: Come up with a product design for a next generation smartphone
Period of Performance: Jan 1 through June 30
Major Activities and Expected Time Period (all dates are in 2023) :
1. Review feedback (reviews and ratings) of old designs of older generation phone(success
factors)
a. Jan1- 15
2. Brain storm features that will be carried over from older generations of phone
a. Jan 15-25
3. Brainstorm physical design and create sketches
a. Jan 25-February 15
Last updated on 13 February 2023
Page 3 of 6
4. Brain storm software features to be carried over from older generations of phone
a. Jan 15-25
5. Brainstorm and begin designing prototypes of software of phone
a. February 15- March 15
6. Creates physical prototypes
a. March 15 – April 20
a
11. Develop marketing strategy
a. April 15-April 30
12. Deliver the Firm or NextGen Smartphone product design document.
a. June 15
Out of Scope Activities:
13. Plan a launch party for employers and customers
14. Budget review to ensure everything is on schedule
15. Review to make sure designing is properly suited for the software. Ensure merging is correct
16. Generation of leads for customer and launch
17. Identifying risks of each feature and
Budget/Cost Estimates:
Cost Type
Labor hours
Amount
165 days=1320 hours
External costs
$20,000
Labor (consultants, contract labor)
$20,000
Last updated on 13 February 2023
Page 4 of 6
Cost Type
Amount
Equipment, hardware or software
$100,000
List other costs such as travel & training
$20,000
Schedule Overview
Schedule Overview
Estimated Project Completion Date: June 15 2023
Major Milestones
•
Sketches of the product- March 1
•
•
•
•
Budget of the project plan – Janurary 15
Prototypes completed for both software and physcial April 20
Beta testing completed of phone design. May 17
Marketing strategy and in implementation May 15th.
External Milestones Affecting the Project
1. Understanding markt trends- January 20, 2023
2. Understanding an implementing regulations needed for product development or
distribution February 1st 2023
3. New technological innovation implementation Jan 24-April 20th 2023
4. Supply chain understanding and planning January 1 st-February 24th
Impact of Late Delivery:
1. Upset stakeholders
2. Decline in sales
3. Late delivery of final product
4. Retention Loss
Deliverables and Acceptance Criteria:
1. Developers:Product with all agreed upon features and deisgn
Last updated on 13 February 2023
Page 5 of 6
a. Criteria 1: complete look
b. Criteria 2: Functional
c. Criteria 3: Passes all quality tests and beta testing.
2. Marketing Team: promoting and creating brand image for product
a. Criteria 1: Market strategy formed based on trends analysis done prior
b. Criteria 2: Has multiple levels to strategy to help sales and upkeep retention
3. Sales Team: building relationship with customer to sell
a. Criteria 1: Agreed upon forecasts from major companies acquired
4. Customer Service Team: This team is responsible for providing support to customers,
addressing their concerns and issues, and ensuring customer satisfaction.
a. Criteria 1: Training for pre and post sale has commenced, all representatives are
knowledgable to help customers.
5. Procurement team: sourcing and managing the materials
a. Criteria 1: All materials have been sourced
b. Criteria 2: All materials have secondary suppliers in place in case of supply chain issues
c. Criteria 3: Logistics have been planned out for the next 2-3 years.
Measures of Success for Project:
1. Product with great quality and minimal bugs
2. Document that outlines all the necessities and includes extra time for possible errors or
mistakes
3. Accountability and tasks completed for each team member
4. Great sales at launch
Assumptions:
1. Market demand: Analyzing the demand and product’s target market.
2. Understanding of the competitors with the features that their goods provide.
3. Maintaining and providing innovation technological developments
4. Cost: Guaranteed profitabilit
5. Design preferences for style, functionality, and the entire user experience
6. Product regulation is complete.
7. No Manufacturing and supply chain errors from thorough procedures
8. Support after the sale
Last updated on 13 February 2023
Page 6 of 6
Major Risks:
1. Customers or stake holders could hate the design
2. Design could malfunction or have erros causing great delay of launch
3. Going over budget with a highly innovative design or with possible error.
4. Creating a product where market demand is low
5. Making a product that turns obsolete soon after launch
6. Disruptions in supply chain or channels preventing final launch
7. Legal requirements not fulfilled
Stakeholder Register:
6. Developers:Designing and developing the product
7. Consisting of both mechanical and software teams
8. Marketing Team: promoting and creating brand image for product
9. Sales Team: building relationship with customer to sell
10. Customer Service Team: This team is responsible for providing support to customers,
addressing their concerns and issues, and ensuring customer satisfaction.
11. Procurement team: sourcing and managing the materials
12. Accounting: managing the budget, analyzing costs, and ensuring profitability
13. Legal Team: protecting the company’s intellectual property and complying with regulations,

Purchase answer to see full
attachment

Description create a work breakdown structure (WBS) based on the M2 SOW. You will also do a risk analysis to identify all risks that might put your project in jeopardy. – use the guide to give you detailed instructions about how to complete the risk analysis and create the WBS.Create the WBS from the SOW that you created in the last module. Remember, your WBS can be in outline or graphical form. Note: there is no assignment template for the WBS. Create risk analysis please use the risk analysis template.M3 Project Guide (WBS and Risk Analysis) # In the last module, you created the SOW and specified all the activities the team needs to do to complete the project. Now it’s time for you to do two more tasks: 1) create a work breakdown structure (WBS) and (2) analyze risks that might put your project in jeopardy. Note that you must do your WBS first, and then do your risk analysis. Work Breakdown Structure Now that you have your SOW, you can create your WBS. Sometimes the hardest part of doing this is getting started. A good way to begin is to review the work you’ve already done during project definition. Then read about the required structure of the WBS and grading criteria below. Note: You will not use a template to create your WBS because you have a couple of options when creating it. For instance, you can use MS PowerPoint or MS Word. You can also create it in graphical or indented representation form. Style Requirements In general, there are several options for WBS formats. However, for this project, you will follow specific WBS style requirements. You will graded based on your adherence to the following requirements: . • Software: You may use either MS PowerPoint or MS Word. • Structure: The WBS can be either in graphical or indented representation. • Notes: If you have notes, commentary, or assumptions that you want to be considered as part of your deliverable, please include them using the Notes feature of PPT or directly in MS Word. • WBS style: Your WBS represents a hierarchical representation of the work. • Notation: Use dot-number notation. • Summary tasks: Use nouns (or verbs) for summary tasks. • Work package format: Use action verb-object format for work packages. • Task titles format: Use concise titles for all tasks that stand on their own even when taken out of the WBS context (e.g., don’t have titles such as Write Report. Instead, you should title it Draft Market Research Report). Remember that when you do any project of any size, you will be using a software tool (e.g., MS Project)—and these tools have associated databases so you can capture additional information about each task. You don’t need to capture it all in a long task title. • Flow: Make sure the WBS follows logically from your SOW. • Charge Number: Provide a charge number such that all the workers on a project can see a work package they can charge their time to—including a PM task for the work of the project manager. Last updated on 14 August 2017 ! • • • • • Page 2 of 2 Value: The WBS should add value, elaborating from your starting point, the SOW. Objective: Record all of the needed work elements to accomplish the objective of the project. Break down: When you “break down” a task, be sure to note if it is two or more descendent tasks. Balance: There should be a sense of balance in the depth and breadth of your WBS—roughly analogous to an org chart (e.g., it would be unusual to have structures such as one node breaking down into 25 direct descendants, or an entirely binary tree in which every node breaks down into exactly two descendants). Proportionality: There is a sense of proportionality in the number of work packages in the WBS and the size of the project. For this project, 10–25 work packages are appropriate. Risk Analysis By analyzing risks that you might experience throughout your project, you can uncover problems before they actually damage the project. The Risk Analysis template provides a starting point for your own systematic risk management process and gives you a way of tracking risks. Brainstorm and come up with every reasonable risk. Then complete the M3 Project (Risk Analysis) Template, completing the following information: • • • • • • • Risk ID: A unique identifier WBS: WBS number of the task(s) related to this risk Rank: How important is this risk relative to others? Rank with 1=highest. No risks have the same rank. Date found: Date risk became known, mm/dd/yy Assigned to: Person who is assigned to manage this risk Description: High level description of risk event, impact, and probability Strategy: What will be done to reduce the probability, impact, or both? M2 Template (SOW) Instructions: Follow the steps below to complete the SOW. Delete all red text in the template and insert your own text in black. Steps 1. In the Project Manager section, list your name. 2. In the Date of Original SOW section, list the date. 3. Complete the Revision History table. In this table, enter the revision date, the name of the person who will do the revisions, the name of the person who will approve the revisions, and a description of each change. 4. Keep the Project Objective the same. You do not need to alter this section. 5. Keep the Period of Performance the same. You do not need to alter this section. 6. In the Major Activities and Expected Time Period section, list all the major activities that you must do to complete the project. Then assign an estimate for when your team will complete each of these activities. 7. In the Out of Scope Activities section, list all out of scope activites for this project. 8. In the Budget/Cost Estimates section, list cost estimates for all types of costs. 9. In the Schedule Overview section, list estimated project completion date, all major milestones with estimated dates of completion, and all external milestones with estimated dates of completion. 10. In the Impact of Late Delivery section, list all the ways in which the project will be affected if it is delivered late. 11. In the Deliverables and Acceptance Criteria section, list all major deliverables, as well as the criteria by which those deliverables will be accepted. 12. In the Measures of Success for Project section, list all the ways in which you intend to measure the project’s success. 13. In the Assumptions section, list all the assumptions that you have about the project. 14. In the Major Risks section, list all the major risks related to the project. 15. In the Stakeholder Register section, list all the stakeholders and their roles, as well as their major responsibility or contribution. Last updated on 13 February 2023 Page 2 of 6 Revision Histor : Revision Date Revised B 2/4/23 2/5/23 Dan Carla pproved B Elisa Nicole Description of Chan e Creation of bud et Modification of dates o completion Project Objective: Come up with a product design for a next generation smartphone Period of Performance: Jan 1 through June 30 Major Activities and Expected Time Period (all dates are in 2023) : 1. Review feedback (reviews and ratings) of old designs of older generation phone(success factors) a. Jan1- 15 2. Brain storm features that will be carried over from older generations of phone a. Jan 15-25 3. Brainstorm physical design and create sketches a. Jan 25-February 15 Last updated on 13 February 2023 Page 3 of 6 4. Brain storm software features to be carried over from older generations of phone a. Jan 15-25 5. Brainstorm and begin designing prototypes of software of phone a. February 15- March 15 6. Creates physical prototypes a. March 15 – April 20 a 11. Develop marketing strategy a. April 15-April 30 12. Deliver the Firm or NextGen Smartphone product design document. a. June 15 Out of Scope Activities: 13. Plan a launch party for employers and customers 14. Budget review to ensure everything is on schedule 15. Review to make sure designing is properly suited for the software. Ensure merging is correct 16. Generation of leads for customer and launch 17. Identifying risks of each feature and Budget/Cost Estimates: Cost Type Labor hours Amount 165 days=1320 hours External costs $20,000 Labor (consultants, contract labor) $20,000 Last updated on 13 February 2023 Page 4 of 6 Cost Type Amount Equipment, hardware or software $100,000 List other costs such as travel & training $20,000 Schedule Overview Schedule Overview Estimated Project Completion Date: June 15 2023 Major Milestones • Sketches of the product- March 1 • • • • Budget of the project plan – Janurary 15 Prototypes completed for both software and physcial April 20 Beta testing completed of phone design. May 17 Marketing strategy and in implementation May 15th. External Milestones Affecting the Project 1. Understanding markt trends- January 20, 2023 2. Understanding an implementing regulations needed for product development or distribution February 1st 2023 3. New technological innovation implementation Jan 24-April 20th 2023 4. Supply chain understanding and planning January 1 st-February 24th Impact of Late Delivery: 1. Upset stakeholders 2. Decline in sales 3. Late delivery of final product 4. Retention Loss Deliverables and Acceptance Criteria: 1. Developers:Product with all agreed upon features and deisgn Last updated on 13 February 2023 Page 5 of 6 a. Criteria 1: complete look b. Criteria 2: Functional c. Criteria 3: Passes all quality tests and beta testing. 2. Marketing Team: promoting and creating brand image for product a. Criteria 1: Market strategy formed based on trends analysis done prior b. Criteria 2: Has multiple levels to strategy to help sales and upkeep retention 3. Sales Team: building relationship with customer to sell a. Criteria 1: Agreed upon forecasts from major companies acquired 4. Customer Service Team: This team is responsible for providing support to customers, addressing their concerns and issues, and ensuring customer satisfaction. a. Criteria 1: Training for pre and post sale has commenced, all representatives are knowledgable to help customers. 5. Procurement team: sourcing and managing the materials a. Criteria 1: All materials have been sourced b. Criteria 2: All materials have secondary suppliers in place in case of supply chain issues c. Criteria 3: Logistics have been planned out for the next 2-3 years. Measures of Success for Project: 1. Product with great quality and minimal bugs 2. Document that outlines all the necessities and includes extra time for possible errors or mistakes 3. Accountability and tasks completed for each team member 4. Great sales at launch Assumptions: 1. Market demand: Analyzing the demand and product’s target market. 2. Understanding of the competitors with the features that their goods provide. 3. Maintaining and providing innovation technological developments 4. Cost: Guaranteed profitabilit 5. Design preferences for style, functionality, and the entire user experience 6. Product regulation is complete. 7. No Manufacturing and supply chain errors from thorough procedures 8. Support after the sale Last updated on 13 February 2023 Page 6 of 6 Major Risks: 1. Customers or stake holders could hate the design 2. Design could malfunction or have erros causing great delay of launch 3. Going over budget with a highly innovative design or with possible error. 4. Creating a product where market demand is low 5. Making a product that turns obsolete soon after launch 6. Disruptions in supply chain or channels preventing final launch 7. Legal requirements not fulfilled Stakeholder Register: 6. Developers:Designing and developing the product 7. Consisting of both mechanical and software teams 8. Marketing Team: promoting and creating brand image for product 9. Sales Team: building relationship with customer to sell 10. Customer Service Team: This team is responsible for providing support to customers, addressing their concerns and issues, and ensuring customer satisfaction. 11. Procurement team: sourcing and managing the materials 12. Accounting: managing the budget, analyzing costs, and ensuring profitability 13. Legal Team: protecting the company’s intellectual property and complying with regulations, Purchase answer to see full attachment

Why Choose Us

  • 100% non-plagiarized Papers
  • 24/7 /365 Service Available
  • Affordable Prices
  • Any Paper, Urgency, and Subject
  • Will complete your papers in 6 hours
  • On-time Delivery
  • Money-back and Privacy guarantees
  • Unlimited Amendments upon request
  • Satisfaction guarantee

How it Works

  • Click on the “Place Your Order” tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
  • Fill in your paper’s requirements in the "PAPER DETAILS" section.
  • Fill in your paper’s academic level, deadline, and the required number of pages from the drop-down menus.
  • Click “CREATE ACCOUNT & SIGN IN” to enter your registration details and get an account with us for record-keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
  • From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.