HUSKY AIR ASSIGNMENTPILOT ANGELS

This case assignment will require you to use Microsoft Project, a popular project manage- ment software tool.

The Scope Management Plan and WBS

Your client, Husky Air, has given your team the author- ity to develop the project's scope. The project's scope defines the project work. It includes the work bound- aries and deliverables that you will deliver to your client. In addition, you will do work breakdown structure (WBS) that will be used for project's schedule and budget in your next assignment.

Please provide a professional-looking document that includes the following:

A brief project description.

The project's MOVThis should be revised or

refined if necessary.

A deliverable structure chart (DSC)This should be based on the project life cycle and the

systems development life cycle. You should begin by creating a hierarchical chart that defines all of the project and system development phases. The system development phases will depend largely on the development approach you use (Waterfall or Agile). After you have identified all project phases, the next step in developing a DSC is to identify at least one project or product deliverable for each phase.

5. A use case diagram (UCD)A UCD defines the high-level features and functionality that the application system should include. Although Figure 5.5 provides an example of a use case, you can build one:

Draw a box to represent the system boundary.

Draw stick figures to represent the actors of the system. Actors can be users, managers, customers, or even other systems that will interact with or use the application system. Actors should be drawn on the outside of the system boundary. Be sure to label each actor with a descriptive name to describe the actor's role.

Draw an oval inside the system boundary for each function and label the oval with a descriptive name. A use case is a particu- lar function that the application system will perform. Examples of use cases are: update customer information, print employee over- time report, create new vendor record, and

so forth. This important step during your project necessitates a great deal of interaction with your client. Unfortunately, you will not have access to a real client, so you can be cre- ative. Keep in mind, however, that additional (and often unused) functionality will require more time and resources to build the system, thus adding to the project's schedule and bud- get. You and your team need to be aware that any features and functionality of the system should help the organization achieve its MOV.

d. Draw a connecting line to identify the actors who will make use of a particular use case.

6. Convert your deliverable structure chart (DSC) to a WBS. Using Microsoft Project, work breakdown structure (WBS) by listing all of the project life cycle and systems development life cycle phases and the associ- ated deliverables that you defined in the DSC. Be sure to work through the MPS tutorial first. Also, be sure to follow the work package concept shown in Figures 5.8 and 5.9. Your WBS should include:

a. Milestones for each phase and deliver- ableAchieving a milestone will tell every- one associated with the project that the phase or deliverable was completed satisfactorily.

b. Activities/TasksDefine a set of activities or tasks that must be completed to produce each deliverable.

c. Resource AssignmentsAssign people and other appropriate resources to each activ- ity. This will be based on the people and resources that you identified when you com- pleted the project infrastructure assignment from the previous chapter. Keep in mind that adding resources to an activity may allow the activity to be completed in a shorter amount of time; however, it may increase the cost of completing that task or activity.

d. Estimates for Each Activity/TaskBased on the tasks or activities and the resources assigned, develop a time estimate for each task or activity to be completed. For the pur- poses of this assignment, you should use a combination of estimation techniques such as time-boxing and bottom-up estimation.