Journal and self reflection
( Assignment 1 Project planning at gbi )
Contents Project scope document 2 Project charter 3 Communication plan 4 Team contract 6 Work Breakdown Structure (WBS) 7 References 8 Gantt chart 9
Project scope document
Project charter
|
Project Name |
|
GBI INFORMATION SYSTEM Development and Deployment Project |
||
|
Project Manager |
|
|
Organization |
|
|
Sponsor |
|
|
Organization |
|
|
|
|
|
|
|
|
Executive Committee |
|
|
|
|
|
Sponsor |
|
|
|
|
|
|
Version 1.2 dated 8th April 2019. |
|||
|
Document Version and Date |
|
|
|
Document Change Control |
|||
|
Revision Number |
Date of Issue |
Author(s) |
Brief Description of Change |
|
Revision 1 |
3rd April |
|
Development of new process included in scope. |
|
Revision 2 |
8th April |
|
Change of existing data included in scope. |
|
Project Scope |
|
|
|
|
|
|
|
|
Business Need |
There is need to automate the processes and centralised the database. This shall be done with the automation of existing processes and using relational database in place of multiple database (Heldman, 2010). This shall reduce the processing time and enhance user experience of various stakeholders. |
||||||
|
Project Goals |
• To develop and deploy the dashboard software as a fully automated information system for client. • To understand the existing business process and convert those processes to automated processes which can be streamlined in the new system software. • To train the client staff for operating the new information dashboard. |
||||||
|
Product Description |
We are implementing tailor made system software. This shall have modules related to accounting, distribution, inventory, sales, receivables, payables and other reporting. |
||||||
|
In Scope/Out of Scope |
Study of existing processes, development of software, preparation of software manual, deployment of software and training of client staff is in scope. Purchase of hardware for client, making add-ins for the software are considered as out scope. |
||||||
|
Critical Success Factors |
• Dashboard software is smoothly handling the business processes of GBI. • There is no major bug other than the routine small bugs in software, which shall be removed during maintenance. • Training to client staff is successful and majority of existing employees are able to work on system software. |
||||||
|
Project Assumptions |
• Majority of existing business processes of GBI can be converted to automated processes. • There shall be good cooperation form the staff of GBI when explaining the existing business processes. • The project shall be completed within the estimated cost and timeline. • There shall be minimal communication gap among the various stakeholders |
||||||
|
Project Constraints |
Project has time constrain and needs to be completed within the given timeline. Project does not have any cost constrain and thus it is possible to go for project crashing when it is must to meet timeline. |
||||||
|
Project Deliverables |
· Information dashboard software along with schema of relational database. · System software training manual · Working papers such as Use Cases and Entity diagrams may be made available to technical team of GBI on request regarding dashboard software along with schema of relational database. |
Communication plan
|
COMMUNICATIONS MATRIX |
|
|
|
|
|
|||
|
Project Name: |
|
GBI INFORMATION SYSTEM Development and Deployment Project |
|
|
|
|
|
|
|
National Center: |
|
|
|
|
|
|
|
|
|
Project Manager Name: |
|
|
|
|
|
|
|
|
|
Project Description: |
|
|
We are implementing tailor made information dashboard. This shall have modules related to accounting, distribution, inventory, sales, receivables, payables and other reporting. |
|||||
|
ID |
Communication Vehicle |
Target Audience |
Description/Purpose |
Frequency |
Owner |
Distribution Vehicle |
Internal / External? |
Comments |
|
0 |
Weekly status report |
Project Team |
Communicate updated project status |
Weekly |
Project manager |
|
Internal |
|
|
1 |
Team meeting minutes |
Project team |
|
Weekly |
Project manager |
|
Internal |
|
|
2 |
Project cash flow statement |
Project team |
|
Weekly |
Project manager |
|
Internal |
|
|
3 |
Project Gantt chart |
Project team |
|
Weekly |
Project manager |
|
Internal |
|
|
4 |
Sponsor feedback form |
Project team & Sponsor |
|
Weekly |
Project manager |
|
Internal & External |
|
|
5 |
Technical/ Design team meeting |
Project team |
Discuss technical/ design problems and solutions |
As needed |
Project manager |
In person |
Internal
|
|
|
6 |
Training sessions |
Users |
Process overview of software (how to) |
1 month prior to implementation |
Project manager |
In person |
Internal |
|
|
7 |
Risk review and update |
Project team |
|
Fortnightly |
Project manager |
|
Internal |
|
Team contract
Team Contract
Team Name: PROJECT AVENGERS
These are the terms of group conduct and cooperation that we agree on as a team.
Participation: We agree to meet on schedule day and time to discuss project related matters.
Communication: We agree to use formal communication.
Meetings: We agree to follow meeting deadlines. In case of specific meetings, we shall discuss matters as per agenda.
Conduct: We agree to use formal communication and conduct in a professional manner. We shall respect the hierarchy of project team.
Conflict: We agree to resolve the conflict in a way which is in best interest of project.
Deadlines: We agree to meet the deadlines and prefer project tasks over our personal tasks.
|
Team Member’s Name |
Team Member’s Signature |
|
Muhammad Ahmad |
AUK3021
|
|
Hafiz Muhammad Ahmad |
AEG3028
|
|
Saim Altaf |
VSS32156
|
|
Ranga Herath Mudiyanselage |
PRT3133
|
|
Lovepreet Singh |
DMA3351 |
Work Breakdown Structure (WBS)
|
WBS OF GBI INFORMATION SYSTEM PROJECT |
|
|
1 |
GBI INFORMATION SYSTEM Development and Deployment Project |
|
1.1 |
Defining project scope |
|
1.1.1 |
Initial meeting to discuss scope |
|
1.1.2 |
Finalising and documenting project scope |
|
1.1.3 |
Project scope complete |
|
1.2 |
System Requirement |
|
1.2.1 |
Requirement analysis |
|
1.2.2 |
Stakeholders' identification |
|
1.2.3 |
Interviewing stakeholders |
|
1.2.4 |
Finalising the requirements |
|
1.2.5 |
Requirement analysis complete |
|
1.3 |
System Design |
|
1.3.1 |
Reviewing system requirement documents |
|
1.3.2 |
Developing functional specifications |
|
1.3.3 |
Considering feedback into functional specifications |
|
1.3.4 |
System design complete |
|
1.4 |
System Development |
|
1.4.1 |
Reviewing system design documents |
|
1.4.2 |
Development of uses cases |
|
1.4.3 |
Developing codes and routines |
|
1.4.4 |
Review of codes |
|
1.4.5 |
Development complete |
|
1.5 |
Testing & Debugging |
|
1.5.1 |
Trial run of module codes |
|
1.5.2 |
Test component modules to product specifications |
|
1.5.3 |
Identify anomalies to product specifications |
|
1.5.4 |
Modification of codes |
|
1.5.5 |
Re-test modified code |
|
1.5.6 |
Unit testing complete |
|
1.6 |
Documentation |
|
1.6.1 |
Developing user help manuals |
|
1.6.2 |
Review of user documents |
|
1.6.3 |
Incorporate user documentation feedback |
|
1.6.4 |
Documentation complete |
|
1.7 |
Deployment |
|
1.7.1 |
Final deployment |
|
1.7.2 |
Distribution of help manuals |
|
1.7.3 |
Training of client staff |
|
1.7.4 |
Deployment complete |
|
1.8 |
Post Implementation Review |
|
1.8.1 |
Document lessons learned |
|
1.8.2 |
Distribute to team members |
|
1.8.3 |
Create system maintenance |
|
1.8.4 |
Post implementation review complete |
|
1.8.5 |
System Development complete |
References Anantatmula, V. S., 2010. Project Manager Leadership Role in Improving Project Performance. Associate Editor Thamhain, 22(1), pp. 13-23. Bruke, R., 2009. Project Management: Planning & Control Techniques. NY: Wiley. Clelant, D. L. & Irish, L. R., 2016. Project Management. 2nd ed. New York City: McGraw-Hill Professional. Heldman, K., 2010. Project Management JumpStart. NSW: John Wiley & Sons.
Gantt chart
References
REFERENCES-
Clelant, D. L. & Irish, L. R., 2016. Project Management. 2nd ed. New York City: McGraw-Hill Professional.
Heldman, K., 2010. Project Management JumpStart. NSW: John Wiley & Sons.
1.0 GBI INFORMATION SYSTEM Development and Deployment Project
1.1 Defining project scope
1.2 System requirement
1.3 System design
(1.4 and 1.5 will run simultaneously)
SYSTEM DEVELOPMENT
1.5 Testing & Debugging
1.7 Deployment
1.8 Post implementation review
1.1.1 Initial meeting for project scope
1.1.2 Finalising and documenting project scope
1.2.1 Requirement analysis
1.2.2 Stakeholders' identification
1.3.1 Reviewing system requirement documents
1.3.2 Developing functional specification
1.4.1 Reviewing system design documents
1.4.2 Development of use cases
1.5.1 Trial run of module codes
1.5.2 Test component modules to product specifications
1.5.3 Identify anomalies in specifications
1.7.1 Final deployment
1.7.2 Disstributino of help manuals
1.8.1 Document lessons learned
1.8.2 Distribute to team members
1.2.3 Interviewing stakeholders
1.2.4 Finalising the requirements
1.3.3 Considering feedback in to functional specifications
1.4.3 Developing codes and routines
1.4.4 Review of codes
1.5.4 Modification of codes
1.7.3 Training of client staff
1.8.3 Create system maintenance
1.6.3 Incorporate user documentation feedback
1.6.2 Review of user documents
1.6.1 Developing user help manuals
1.6 (It is essential for every step)
DOCUMENTATION
PERIODS
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
1.1Defining project scope44100%
1.1.1
Initial meeting to discuss scope
11
100%
1.1.2
Finalising and documenting projeect
scope
33
100%
1.1.3
Project scope complete
00
100%
1.2
System requirement1313
93%
1.2.1
Requirement analysis
44
90%
1.2.2
Staleholder's identfication
22
85%
1.2.3
Interviewing stakeholders
33
100%
1.2.4
Finalizing the requirements
44
100%
1.25
Requirement analysis complete
00
89%
1.3
System Design77
84%
1.3.1
Reviewing system requirement
documents
11
75%
1.3.2
Developing functional specifications
44
100%
1.3.3
Considerin feedback into functional
specifications
22
60%
1.3.4
System design complete
00
100%
1.4
System Development3838
80%
1.4.1
Reviewing system design documents
88
50%
1.4.2
Development of use cases
88
90%
1.4.3
Developing codes and routines
1212
81%
1.4.4
Review of codes
99
80%
1.4.5
Development complete
11
100%
1.5
Testing and debugging1111
10%
1.5.1
Trial run of module codes
44
0%
1.5.2
Test component modules to product
specifications
22
0%
1.5.3
Identify anomalies to product
specifications
22
0%
1.5.4
Modification of codes
22
44%
1.5.5
Re-test mofidied code
11
0%
1.5.6
Unit testing complete
00
12%
1.6
Documentation55
13%
1.6.1
Developing user help manuals
22
5%
1.6.2
Review of user documents
22
0%
1.6.3
Incorporate user documentation
feedback
11
50%
1.6.4
Documentation complete
00
0%
1.7
Deployment4646
13%
1.7.1
Final deployment
1515
5%
1.7.2
Distribution of help manuals
1515
0%
1.7.3
Training of client staff
1616
50%
1.7.4
Deployment complete
00
0%
1.8
Post implementation review33
0%
1.8.1
Document lessons learned
11
0%
1.8.2
Distribute to team members
11
5%
1.8.3
Create system maintenance
11
0%
1.8.4
Post implementation review complete
00
0%
1.8.5
System development complete
00
0%
ACTIVITY
ACTUAL
DURATION
ACTUAL START
PERCENT
COMPLETE