Journal and self reflection

Ahmad571
assignmentforreferance.docx

( 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 ID

CLI0034-19

Date

9th April, 2019

Project Name

 Client GBI Information System Project

Project Objectives

· To develop and deploy information system as fully automated information system for client.

· To understand the existing business process and convert those processes to automated processes which can be streamline in information system

· To train the client staff for operating the information system

Product Scope Definition

The existing system of client GBI is not fully automated and this is creating sales, distribution and database management for the company. In today’s fast paced world, it may not be possible for a business to survive while adopting only centralized IT system. Due to existing centralized IT system GBI is facing information sharing and planning difficulties and thus there is need to replace the existing system with a much more sophisticated and modern system which can store a large amount of data and can process it effectively and efficiently. (Anantatmula, 2010).

The development and deployment of new information dashboard shall require study of the existing processes. It may be noted that some of these processes may not be suited for the dashboard environment. Thus the scope of this project also includes providing alternative process to replace such manual processes

Project Requirements

· GBI requires a new system that can store vast amounts of information like the material they are using and how many employees they have, what are their orders and how many products are manufactured annually and monthly.

· the new system should be able to generate the sale reports of GBI and how they are affected by the change in any sector like how changing the materials will affect the sale in that month, or what effect decreasing the price has on sales.

· There is need to fully understand and document the expectations and requirements of GBI management and staff from the new system.

· Another requirement is to estimate the project cost and timeline.

· John will need to access marketing and financial data according to his required queries using GBI data

· Peter will need to be able to access queries regarding development and operations using GBI data

· Employees working in development will need to be able to access research data according to their queries

Project Boundaries

The new information dashboard shall be developed for GBI Bike Inc. only and thus project team is not responsible if the INFORMATION SYSTEM is used for any other group company. Thus the project boundaries are restricted to GBI Bike Inc. workplace only (Bruke, 2009).

Project Deliverables

1. Dashboard software along with schema of relational database.

2. Dashboard user training manual

3. Documentation Working papers such as Use Cases and Entity diagrams may be made available to technical team of GBI on request.

Product Success Criteria

· The new dashboard 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 the dashboard software.

Project Constraints/ 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.

Initial Project Organization

Project manager shall report to project sponsor. Besides that project manager shall be single point of contact for all the stakeholders. Codes, developers, testers, designers shall report to project manager and their shall be hierarchy for each of these skill levels such as senior manager testing, manager testing and officer testing etc.

Schedule Milestones

Project phases

· Problem analysis

· Specification design

· Designing of new system

· Implementation of application

· Installation

· Maintenance

1. Project scope complete dated 10th April 2019

2. Requirement analysis complete dated 6th May 2019

3. System design complete dated 15th May 2019

4. Development competed dated 8th July 2019

5. Unit testing complete 22nd July 2019

6. Documentation complete 29th July 2019

7. Post implementation complete 6th August 2019

Cost Estimation/Fund Limitation

The actual cost of project may vary from the budgeted cost. However the project is not cost bound but time bound and thus if there is need for revising the critical path than extra funds shall be available (Clelant & Irish, 2016).

Risk, Responsibilities, Mitigation Strategies

There is risk that the existing data may not be able to convert to the automatic process. Under such situations the existing data need to be converted in to a format which can be used in the new system.

Also with a new more decentralized access to the information the risk of information security goes higher. Therefore new security measurements need to be in place.

There is a risk of unseen software patches that must be integrated with the new system. Identifying these early on will help a smother integration.

Approval Requirements

Approval is required from project sponsor as per the project scope.

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

email

Internal

 

 1

 Team meeting minutes

 Project team

 

Weekly

Project manager

email

Internal

 

 2

 Project cash flow statement

 Project team

 

Weekly

Project manager

email

Internal

 

 Project Gantt chart

 Project team

 

Weekly

Project manager

email

Internal

 

 Sponsor feedback form

 Project team & Sponsor

 

Weekly

Project manager

email

Internal & External

 

 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

E-mail

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