Assignment template
Please use the below given sample formats when answering the assignment two questions
Task -1: Scope Management Plan
Requirements: List of functions and features in your application
In scope-out scope items: In scope items are list of requirements that are going to be implemented as part of this system. Out scope items are list of functions and features that are not going to be implemented in this project but can be done later for this application.
Deliverables:
Scope verification process: this is built from the Acceptance criteria listed
Task 2: WBS
You need to create level 3 WBS. It should have a minimum of 40 tasks. Use the indented format and level 1 as 4 phases of project life cycle.
Task 3: Gantt chart- Firstly you need to do Activity Estimation i.e. estimate the duration of each activity and Secondly dependencies between eh activities need to be determined before you can create a schedule and MS Project builds the Gann chart. You also need to allocate resources to each activity ( 1 resource per activity) from the table given below (PS: You do not need to use all the resources listed below, you may use the ones you need to complete your project)Gantt chart should include all the resources allocated in this project. You should attach the MS project screen shots to prove your workings.
The Resource table to be used for allocating resources is as below
|
|
|
|
|
$ per Hour
|
|
Project Manager
|
|
|
|
80 |
|
Systems Analysis
|
|
|
|
60 |
|
Graphic Designer
|
|
|
|
50 |
|
Application Programmer
|
|
|
|
50 |
|
Web System Expert
|
|
|
|
70 |
|
Program Team member_1
|
|
|
|
50 |
|
Program Team Member_2
|
|
|
|
50 |
|
Quality Assurance Tester
|
|
|
|
60 |
|
Database Administrator
|
|
|
|
50 |
|
Team Member_1
|
|
|
|
35 |
|
Team Member_2
|
|
|
|
35 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Total Duration for the Project
|
|
|
|
6 months
|
|
Working Days
|
|
|
|
5 days per week ( No Over time required)
|
|
Working Hours
|
|
|
|
8 hours per day ( 8.30 - 5.30pm) - 1 hour for lunch
|
|
Project Start Date
|
|
|
|
4 Jan 2016
|
Total Duration for the Project 6 months
Working Days 5 days per week ( No Over time required)
Working Hours 8 hours per day ( 8.30 - 5.30pm) - 1 hour for lunch
Project Start Date 4 Jan 2016
Task 4: Create a time-phased budget for your example project using bottom-up estimating. As you allocate resources to the activity your budget is being created. After you extract the Gantt chart, revisit the activity list and be sure to check direct labour costs for you and your team has been added and add 20% for fringe.
In this section, State all assumptions and constraints you have used when creating your budget. Give examples of known knowns and known unknowns( these are financial risks) on your project. Describe how you have budgeted for both of them plus how you have budgeted for unknown unknowns
Task 5: Risk Register
Create a risk register In the form of a risk register as per the format and example below ( 4 risks- 3 negative and 1 positive risk)for your example project.
For example, the following data might be entered for the first risk in the reg¬ister as follows. Notice that Cliff's team is taking a very proactive approach in managing this risk.
No.: R44
Rank: 1
Risk: New customer
Description: We have never done a project for this organization before and don't know too much about them. One of our company's strengths is building good customer relationships, which often leads to further proj¬ects with that customer. We might have trouble working with this cus¬tomer since they are new to us.
Category: People risk
Root cause: We won a contract to work on a project without really getting to know the customer.
Diggers: The project manager and other senior managers realize that we don't know much about this customer and could easily misunderstand their needs or expectations.
Risk Responses: Make sure the project manager is sensitive to the fact that this is a new customer and takes the time to understand them. Have the PM set up a meeting to get to know the customer and clarify their expec-tations. Have Cliff attend the meeting, too.
Risk owner. Our project manager
Probability: Medium
Impact High
Status: PM will set up the meeting within the week.
After identifying risks, the next step is to understand which risks are most important by performing qualitative risk analysis.
Conclusion