Create/discuss a WBS diagram/chart for the project. The WBS submitted should look like a hierarchy chart (i.e.  (note I say “looks”…do not give me an org chart hierarchy structure of the organization…I am saying use the WBS format that is often used to depict an org chart to build your WBS)

/in /by

This assignment looks long but it’s short. I’ve attached an example of the paper, and the diagram. I would like to use Scenario 1 – Software Upgrade.

Choose a scenario from one of the 2 scenarios provided and submit a paper of 650 words (again just a note….intro/conclusion paragraphs and any tables/charts/etc do not count in the word count).

Include the following items in your paper:

·        Identify the scope of the project. Note: do not just repeat exactly what the scenario states is going on/needed….use your own words to tell me what the project will cover/what it is not covering/why.

·        Discuss the needs of at least three stakeholders involved in the project. In doing this you have to clearly identify those stakeholders as well.

·        Create/discuss a WBS diagram/chart for the project. The WBS submitted should look like a hierarchy chart (i.e.  (note I say “looks”…do not give me an org chart hierarchy structure of the organization…I am saying use the WBS format that is often used to depict an org chart to build your WBS) like an organization chart with boxes, lines, etc….this can be built in Powerpoint…yes I understand that MS Project can build a WBS but the focus here is on the WBS concept so I need to see you building it) and the diagram/chart should be included within the paper (not as an attachment)…you need to provide at least 4 levels deep (i.e. X.X.X.X) of detail on the WBS

diagram. Remember in the WBS you are breaking down the work items (in more detail/degrees at each level) needed to complete the project.

·        List/discuss necessary tools and techniques for the project. For example, are you using MS Project to manage the effort or is a technique going to be using the Waterfall development approach.

·        List/discuss the milestones for the project. Note: make sure you understand what a milestone is…not every activity/task is a project milestone.

·        Sequence the project tasks/subtasks in a diagram. Include the diagram within the paper (not as an attachment). Note that this is a separate diagram from the WBS; the WBS does not show sequence….the WBS is used as an input to build the project schedule and the project schedule is much more detailed than the WBS. The sequence diagram can be done in MS Project (Note: this course does not provide students MS Project…if you have it you can use it, but I am not requiring it and this portion of the assignment can be done without using that tool), MS Powerpoint, etc to sequence the tasks/subtasks. Make sure you have an adequate number of tasks/subtasks in the diagram to complete the project. In other words don’t just show me say 4 tasks and think that is complete….this diagram needs to be detailed.

Just a note:  This is a made up scenario and you are filling in the gaps by applying the concepts from the course. There is no website to go to that tells you what this project is….you are making it up. Students often feel the need to do research on “the organization” but there is none to perform here….this is a made up scenario. You will be using the same scenario for upcoming weeks assignments….they key is we are using the scenario to build/show the concepts discussed in the course.

Submit paper in APA format