Scope Management Plan
Discuss about the Project Management Grand Wines.
Grand Wines Ltd is facing problem with the management of the business operations and the sales database due to the manual handling of the data insertion and inventory system management. As the business of the company expanded over a large area and the representatives need to insert and update the database from various locations, the company need a wireless device for data handling. In this context, the company’s previous database management system cannot be used for using the new devices. The company needs a new information system for managing all the data required for the business operations and the inventory management and using the new wireless data input devices.
This report is explaining the project management activities involved in the information system development. The detailed work breakdown structure, Gantt chart, budget planning and risk management activities are considered in this project management.
1.1 Requirements: This project is about the development of an information system which will be able to support the wireless data entry devices for Grand wines Ltd. The advance characteristics of the information system are the requirements of the company. The required functions of the new system are given in the section below:
- Real time response from the system by the ability of having data input from the sales representatives
- Ability of monitoring the stock and warehouse of the company
- Reducing the human errors by the automatic data entry systems
- Tracking the orders of the client in minimum time
In scope and out scope management:
The in scope management items for the project are as follows:
- Budget estimation and proper monitoring of the progress of the project
- Cash flow during the project development phase
- Arrangement of the meetings with all the other stakeholders of the project
The out scope management requirements of the project are as follows:
- Management of the legal issues associated with the project
- Management of errors in the resource management
Work Breakdown Structure:
Project Schedule:
|
Task Name |
Duration |
Start |
Finish |
Predecessors |
Resource Names |
Cost |
|
Development of Information System for Grand Wines Ltd |
87 days |
Thu 1/5/17 |
Fri 5/5/17 |
$59,680.00 |
||
|
Requirements of Analysis/Software |
10 days |
Thu 1/5/17 |
Wed 1/18/17 |
$9,360.00 |
||
|
Requirement Analysis |
3 days |
Thu 1/5/17 |
Mon 1/9/17 |
Analyst |
$2,160.00 |
|
|
Draft preliminary software specifications |
1 day |
Tue 1/10/17 |
Tue 1/10/17 |
3 |
Analyst |
$720.00 |
|
Develop preliminary budget |
1 day |
Wed 1/11/17 |
Wed 1/11/17 |
4 |
Project Manager |
$960.00 |
|
Review software specifications/budget with team |
1 day |
Thu 1/12/17 |
Thu 1/12/17 |
5 |
Project Manager |
$960.00 |
|
Incorporate feedback on software specifications |
2 days |
Fri 1/13/17 |
Mon 1/16/17 |
6 |
Project Manager |
$1,920.00 |
|
Develop delivery timeline |
1 day |
Tue 1/17/17 |
Tue 1/17/17 |
7 |
Analyst,Project Manager |
$1,680.00 |
|
Secure required resources |
1 day |
Wed 1/18/17 |
Wed 1/18/17 |
8 |
Project Manager |
$960.00 |
|
Analysis complete |
0 days |
Wed 1/18/17 |
Wed 1/18/17 |
9 |
$0.00 |
|
|
Design |
15 days |
Thu 1/19/17 |
Wed 2/8/17 |
$10,800.00 |
||
|
Revision of the preliminary requirements of the system |
4 days |
Thu 1/19/17 |
Tue 1/24/17 |
10 |
Analyst |
$2,880.00 |
|
Development of the functional specifications |
3 days |
Wed 1/25/17 |
Fri 1/27/17 |
12 |
Analyst |
$2,160.00 |
|
Revision of the functional specifications |
3 days |
Mon 1/30/17 |
Wed 2/1/17 |
13 |
Project Manager |
$2,880.00 |
|
Incorporate feedback into functional specifications |
3 days |
Thu 2/2/17 |
Mon 2/6/17 |
14 |
Project Manager |
$2,880.00 |
|
Approval of the project |
2 days |
Tue 2/7/17 |
Wed 2/8/17 |
15 |
CEO |
$0.00 |
|
Completion of the Design |
0 days |
Wed 2/8/17 |
Wed 2/8/17 |
16 |
$0.00 |
|
|
Development |
22 days |
Thu 2/9/17 |
Fri 3/10/17 |
$14,400.00 |
||
|
Revision of the functional specifications |
3 days |
Thu 2/9/17 |
Mon 2/13/17 |
17 |
Developer |
$1,920.00 |
|
Identification design parameters (modular/tiered) |
2 days |
Tue 2/14/17 |
Wed 2/15/17 |
19 |
Developer |
$1,280.00 |
|
Assign staf for development |
1 day |
Thu 2/16/17 |
Thu 2/16/17 |
20 |
Project Manager |
$960.00 |
|
Develop code |
12 days |
Fri 2/17/17 |
Mon 3/6/17 |
21 |
Developer |
$7,680.00 |
|
Developer testing (primary debugging) |
4 days |
Tue 3/7/17 |
Fri 3/10/17 |
22 |
Developer |
$2,560.00 |
|
Development complete |
0 days |
Fri 3/10/17 |
Fri 3/10/17 |
23 |
$0.00 |
|
|
Testing |
15 days |
Mon 3/13/17 |
Fri 3/31/17 |
$9,600.00 |
||
|
Unit Test Plan Development |
2 days |
Mon 3/13/17 |
Tue 3/14/17 |
24 |
Testers |
$1,280.00 |
|
Integration test plan development |
2 days |
Wed 3/15/17 |
Thu 3/16/17 |
26 |
Testers |
$1,280.00 |
|
Test module integration |
2 days |
Fri 3/17/17 |
Mon 3/20/17 |
27 |
Testers |
$1,280.00 |
|
Identify anomalies to specifications |
2 days |
Tue 3/21/17 |
Wed 3/22/17 |
28 |
Testers |
$1,280.00 |
|
Modify code |
2 days |
Thu 3/23/17 |
Fri 3/24/17 |
29 |
Developer |
$1,280.00 |
|
Re-test modified code |
5 days |
Mon 3/27/17 |
Fri 3/31/17 |
30 |
Testers |
$3,200.00 |
|
Testing complete |
0 days |
Fri 3/31/17 |
Fri 3/31/17 |
31 |
$0.00 |
|
|
Documentation |
13 days |
Mon 4/3/17 |
Wed 4/19/17 |
$7,280.00 |
||
|
Development of the Help specification |
2 days |
Mon 4/3/17 |
Tue 4/4/17 |
32 |
Technical Communicators |
$1,120.00 |
|
Development of the Help system |
2 days |
Wed 4/5/17 |
Thu 4/6/17 |
34 |
Technical Communicators |
$1,120.00 |
|
Reviewing the Help documentation |
2 days |
Fri 4/7/17 |
Mon 4/10/17 |
35 |
Technical Communicators |
$1,120.00 |
|
Incorporate Help documentation feedback |
1 day |
Tue 4/11/17 |
Tue 4/11/17 |
36 |
Technical Communicators |
$560.00 |
|
Development of the user manuals specifications |
1 day |
Wed 4/12/17 |
Wed 4/12/17 |
37 |
Technical Communicators |
$560.00 |
|
Development of the user manuals |
2 days |
Thu 4/13/17 |
Fri 4/14/17 |
38 |
Technical Communicators |
$1,120.00 |
|
User documentation review |
2 days |
Mon 4/17/17 |
Tue 4/18/17 |
39 |
Technical Communicators |
$1,120.00 |
|
Incorporation of user feedbacks |
1 day |
Wed 4/19/17 |
Wed 4/19/17 |
40 |
Technical Communicators |
$560.00 |
|
Completion of documentation |
0 days |
Wed 4/19/17 |
Wed 4/19/17 |
41 |
$0.00 |
|
|
Deployment |
9 days |
Thu 4/20/17 |
Tue 5/2/17 |
$5,360.00 |
||
|
Final deployemnt strategy identification |
1 day |
Thu 4/20/17 |
Thu 4/20/17 |
42 |
Deployment Team |
$640.00 |
|
Development of deployment methodology |
1 day |
Fri 4/21/17 |
Fri 4/21/17 |
44 |
Deployment Team |
$640.00 |
|
Security of deployemnt resources |
1 day |
Mon 4/24/17 |
Mon 4/24/17 |
45 |
Deployment Team |
$640.00 |
|
Deploy software |
1 day |
Tue 4/25/17 |
Tue 4/25/17 |
46 |
Deployment Team |
$640.00 |
|
Train support staff |
5 days |
Wed 4/26/17 |
Tue 5/2/17 |
47 |
Trainers |
$2,800.00 |
|
Deployement completion |
0 days |
Tue 5/2/17 |
Tue 5/2/17 |
48 |
$0.00 |
|
|
Review of Post Implementation |
3 days |
Wed 5/3/17 |
Fri 5/5/17 |
$2,880.00 |
||
|
Lessons learned from document |
1 day |
Wed 5/3/17 |
Wed 5/3/17 |
49 |
Project Manager |
$960.00 |
|
Distribution of learning |
1 day |
Thu 5/4/17 |
Thu 5/4/17 |
51 |
Project Manager |
$960.00 |
|
Creation of software maintanenance team |
1 day |
Fri 5/5/17 |
Fri 5/5/17 |
52 |
Project Manager |
$960.00 |
|
Completion of Post implementation review |
0 days |
Fri 5/5/17 |
Fri 5/5/17 |
53 |
$0.00 |
Time Phase Budget:
Risk Register:
The risks associated with this project can be considered into four types-
- Risks associated with Quality.
- Risks associated with Budget.
- Risks associated with Resource.
- Risks associated with Deadline.
|
Serial No. |
Risk description |
References of Cells |
|
1 |
Risks associated with Quality: At the initial level the system specification and design of information system was not mentioned. |
B1 |
|
2 |
Risks associated with Budget: the development of the project may be hampered for the problems in resource allocation and payment related operations. |
C4 |
|
3 |
Risks associated with Resource: Lack of communication among the team members and conflict of interest regarding the project activities. |
C2 |
|
4 |
Deadline Risks: Fail to meet the deadline of the project due to various types of changes in the schedule and the sub activities of the project. |
C4 |
|
Risk Identification |
A (Unlikely) |
B (Medium) |
C (Expected) |
D (Confident) |
|
1 (Small) |
1 |
|||
|
2 (Negligible) |
3 |
|||
|
3 (Missing Time) |
||||
|
4 (Impactful) |
4, 2 |
|||
|
5 (Serious) |
Mitigation of the Identified Risks
|
Recognized Risks |
Mitigating Activities |
|
Risks associated with Quality |
The client organization demands for requirement analysis. Testing of the information system information system at the starting of the project is important. |
|
Risks associated with Budget |
Resource allocation and conciliation with the client regarding the payment related issues. |
|
Risks associated with Resource |
Periodical monitoring and sharing of resources are very important in order to resolve the risks associated with resources. |
|
Risks associated with Deadline |
The project schedule needs to be revised in accordance with the revised schedules during the project development. |
Conclusion:
The project of developing an information system for the Grand Wines will be a helpful one for the busienss processes of the comapny. In the new system, the sales representatives will be able to input data from the remote locations through the wireless data entry device. The new system will be an effeticve one for handling all the inventory management and database handling activties of the company through a siingle system. It will be a rea time data base habdling system which will help the company to compete with the others in the market. The time required for this project is four months and the required budget is AUD 59,680.
Balaban, I., Mu, E. & Divjak, B., (2013). Development of an electronic Portfolio system success model: An information systems approach. Computers & Education, 60(1), pp.396-411.
Bendoly, E., Bharadwaj, A. & Bharadwaj, S., (2012). Complementary Drivers of New Product Development Performance: Cross?Functional Coordination, Information System Capability, and Intelligence Quality. Production and Operations Management, 21(4), pp.653-667.
Burke, R., (2013). Project management: planning and control techniques. New Jersey, USA.
Ferrucci, F., Harman, M. & Sarro, F., (2014). Search-based software project management. In Software Project Management in a Changing World (pp. 373-399). Springer Berlin Heidelberg.
Gido, J. & Clements, J.P., (2014). Successful project management. Nelson Education.
Kerzner, H.R., (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
