CIS5308 Information Technology Services Oz Assignment

CIS5308 Information Technology Services Oz Assignment

CIS5308 Information Technology Services Oz Assignment

Part One

The measurable organizational value defines the goal of the project and helps in analysing the values that the organization provides to its clients (Beringer, Jonas & Kock, 2013).). The measurable organization value that is set by Globex is development of a website and an application that will help in easier management of the gains that are stored in warehouse. The desired area of impact the project is expected to cover includes the operational, social, financial, strategy and customers associated with the organization behaviour(Binder, 2016). Ranking of the area of impact of the project is represented in the following table

Operational

Rank 1

Financial

Rank 2

Strategy

Rank 3

Social

Rank 4

Customers

Rank 5

The values that this project will be providing to the company are as follows (Burke, 2013)-

1. Better- The Client Globex wants to improve their process of business delivery by improving the ease of access and management of the warehoused grains.

2. Faster- With the implementation of this project, the process of selling the warehoused grains would be faster.

The metrics for measuring whether the project is successful in achieving the desired target or not are as follows-

1. The objectives set by Globex should be achieved with the help of the project.

2. The Project is needed to be implemented as inexpensively as possible.

The timeframe for achieving the desired MOV of the organization will be six months from the project initiation. The Globex and Virtucon will be able to achieve the desired target by ensuring successful implementation of the application and the website.

Scope and Scope management

It is important to identify the scope of the project in order to ensure that the implementation of the project by the project management team follows the goals and the objectives of the project. The scope of this project is to implement the website and the smartphone application in an inexpensive manner as possible. The scope will be managed by ensuring that each project deliverables are completed within a scheduled time (Heagney, 2016). The Functional Manger of the project will be responsible appropriate project monitoring and control. Apart from that the resource manager will be responsible for managing the resources of the project.

List of Resources

The main resources that are needed in the project are as follows-

Resource Name

Max. Units

Std. Rate

Ovt. Rate

Cost/Use

         

Project Manager

100%

$90.00/hr

$0.00/hr

$0.00

Functional Manager

100%

$40.00/hr

$0.00/hr

$0.00

Resource Manager

100%

$40.00/hr

$0.00/hr

$0.00

Coding team

600%

$45.00/hr

$0.00/hr

$0.00

Code and Application Tester

800%

$30.00/hr

$0.00/hr

$0.00

Database Administrator

200%

$40.00/hr

$0.00/hr

$0.00

Website and Application Licensing Cost

 

$0.00

 

$60,000.00

Training Team

300%

$30.00/hr

$0.00/hr

$0.00

Archieve

 

$0.00

 

$5,000.00

Content writer

300%

$10.00/hr

$0.00/hr

$0.00

Project Manager of Globex

100%

$90.00/hr

$0.00/hr

$0.00

Milestone

The identified milestones of the project are as follows-

M1: Completion of the Project Initiation Phase

M2: Project Plan Approval

M3: Successful Coding

M4: Completion of Testing and Bug Fixation

M5: Successful Go Live and Training

M6: Project completion

Activities/tasks

The tasks and the activities associated with each deliverables of the project are as follows-

WBS

Task Name

0

I-Crop-A Project by Virtucon

1

Project Initiation

1.1

Meeting with Globex

1.2

Requirements Gathering and identification of the specifications of the Project

1.3

Documentation

1.4

Approving the requirements from the Clients

1.5

M1: Completion of the Project Initiation Phase

2

Project Planning

2.1

Project Scheduling

2.2

Identification of Resource Requirements

2.3

Budgeting

2.4

Development and Approval of Project Plan

2.5

M2:Project Plan Approval

3

Project Execution

3.1

Coding of Website and smartphone Application

3.2

Linking with database

3.3

Documenting each Activity

3.4

M3: Successful Coding

4

Testing

4.1

Unit Testing

4.2

System testing

4.3

User acceptance testing

4.4

Bug Fixing (if any)

4.5

Documentation

4.6

M4: Completion of Testing and Bug Fixation

5

Go Live and Traning

5.1

Website and Application Launch

5.2

Training

5.3

Post implementation support

5.4

M5: Successful Go Live and Training

6

Project Closure

6.1

Documentation

6.2

Record Archival

6.3

Completion of payment

6.4

Resource Release

6.5

Client Sign off

6.6

M6:Project completion

The Gantt Chart of the Project is represented below-

Figure 1: Representing the Gantt Chart of the project

(Source: Generated by Author using MS project)

The work activities marked in red in the Gantt chart above depict the critical path of the project

The work breakdown structure of the project is represented in the following picture –

Figure 2: Representing the Work Breakdown Structure

(Source: Created by Author using MS Schedule Pro and MS Project)

Resource Assignments

The resources allocated to each of the activities of the project are represented in the following table-

Task Name

Duration

Predecessors

Resource Names

I-Crop-A Project by Virtucon

114 days

   

Project Initiation

18 days

   

Meeting with Globex

5 days

 

Project Manager

Requirements Gathering and identification of the specifications of the Project

10 days

2

Project Manager, Functional Manager

Documentation

2 days

3

Archive [1],Content writer

Approving the requirements from the Clients

1 day

4

Project Manager

M1: Completion of the Project Initiation Phase

0 days

5

 

Project Planning

7 days

   

Project Scheduling

2 days

6

Project Manager, Resource Manager

Identification of Resource Requirements

7 days

6

Project Manager, Resource Manager

Budgeting

5 days

6

Functional Manager ,Resource Manager

Development and Approval of Project Plan

2 days

10

Project Manager of Globex

M2:Project Plan Approval

0 days

11

 

Project Execution

32 days

   

Coding of Website and smartphone Application

15 days

12

Coding team ,Website and Application Licensing Cost[1]

Linking with database

15 days

14

Coding team ,Database Administrator

Documenting each Activity

2 days

15

Archieve [1],Content writer

M3: Successful Coding

0 days

16

 

Testing

36 days

   

Unit Testing

10 days

17

Code and Application Tester

System testing

7 days

19

Code and Application Tester

User acceptance testing

12 days

20

Code and Application Tester

Bug Fixing (if any)

5 days

21

Code and Application Tester

Documentation

2 days

22

Archive [1],Content writer

M4: Completion of Testing and Bug Fixation

0 days

22

 

Go Live and Training

12 days

   

Website and Application Launch

5 days

22

Project Manager, Project Manager of Globex

Training

5 days

26

 

Post implementation support

7 days

26

Training Team ,Functional Manager

M5: Successful Go Live and Training

0 days

28

 

Project Closure

11 days

   

Documentation

2 days

28

Archive [1],Content writer

Record Archival

2 days

31

Archive [1]

Completion of payment

7 days

32

Project Manager of Globex

Resource Release

1 day

32

Project Manager

Client Sign off

2 days

34

Project Manager

M6:Project completion

0 days

35

 

Estimates for Each Activity

The time estimation or duration of each of the activities of the project is represented in the following table-

WBS

Task Name

Duration

Start

Finish

0

I-Crop-A Project by Virtucon

114 days

Wed 03-10-18

Mon 11-03-19

1

Project Initiation

18 days

Wed 03-10-18

Fri 26-10-18

1.1

Meeting with Globex

5 days

Wed 03-10-18

Tue 09-10-18

1.2

Requirements Gathering and identification of the specifications of the Project

10 days

Wed 10-10-18

Tue 23-10-18

1.3

Documentation

2 days

Wed 24-10-18

Thu 25-10-18

1.4

Approving the requirements from the Clients

1 day

Fri 26-10-18

Fri 26-10-18

1.5

M1: Completion of the Project Initiation Phase

0 days

Fri 26-10-18

Fri 26-10-18

2

Project Planning

7 days

Mon 29-10-18

Tue 06-11-18

2.1

Project Scheduling

2 days

Mon 29-10-18

Tue 30-10-18

2.2

Identification of Resource Requirements

7 days

Mon 29-10-18

Tue 06-11-18

2.3

Budgeting

5 days

Mon 29-10-18

Fri 02-11-18

2.4

Development and Approval of Project Plan

2 days

Mon 05-11-18

Tue 06-11-18

2.5

M2:Project Plan Approval

0 days

Tue 06-11-18

Tue 06-11-18

3

Project Execution

32 days

Wed 07-11-18

Thu 20-12-18

3.1

Coding of Website and smartphone Application

15 days

Wed 07-11-18

Tue 27-11-18

3.2

Linking with database

15 days

Wed 28-11-18

Tue 18-12-18

3.3

Documenting each Activity

2 days

Wed 19-12-18

Thu 20-12-18

3.4

M3: Successful Coding

0 days

Thu 20-12-18

Thu 20-12-18

4

Testing

36 days

Fri 21-12-18

Fri 08-02-19

4.1

Unit Testing

10 days

Fri 21-12-18

Thu 03-01-19

4.2

System testing

7 days

Fri 04-01-19

Mon 14-01-19

4.3

User acceptance testing

12 days

Tue 15-01-19

Wed 30-01-19

4.4

Bug Fixing (if any)

5 days

Thu 31-01-19

Wed 06-02-19

4.5

Documentation

2 days

Thu 07-02-19

Fri 08-02-19

4.6

M4: Completion of Testing and Bug Fixation

0 days

Wed 06-02-19

Wed 06-02-19

5

Go Live and Training

12 days

Thu 07-02-19

Fri 22-02-19

5.1

Website and Application Launch

5 days

Thu 07-02-19

Wed 13-02-19

5.2

Training

5 days

Thu 14-02-19

Wed 20-02-19

5.3

Post implementation support

7 days

Thu 14-02-19

Fri 22-02-19

5.4

M5: Successful Go Live and Training

0 days

Fri 22-02-19

Fri 22-02-19

6

Project Closure

11 days

Mon 25-02-19

Mon 11-03-19

6.1

Documentation

2 days

Mon 25-02-19

Tue 26-02-19

6.2

Record Archival

2 days

Wed 27-02-19

Thu 28-02-19

6.3

Completion of payment

7 days

Fri 01-03-19

Mon 11-03-19

6.4

Resource Release

1 day

Fri 01-03-19

Fri 01-03-19

6.5

Client Sign off

2 days

Mon 04-03-19

Tue 05-03-19

6.6

M6:Project completion

0 days

Tue 05-03-19

Tue 05-03-19

 Project Budget

The estimated budget for the project corresponding to each of the activities in the project is as follows-

WBS

Task Name

Duration

Resource Names

Cost

0

I-Crop-A Project by Virtucon

114 days

 

$156,440.00

1

Project Initiation

18 days

 

$19,880.00

1.1

Meeting with Globex

5 days

Project Manager

$3,600.00

1.2

Requirements Gathering and identification of the specifications of the Project

10 days

Project Manager, Functional Manager

$10,400.00

1.3

Documentation

2 days

Archive [1],Content writer

$5,160.00

1.4

Approving the requirements from the Clients

1 day

Project Manager

$720.00

1.5

M1: Completion of the Project Initiation Phase

0 days

 

$0.00

2

Project Planning

7 days

 

$14,000.00

2.1

Project Scheduling

2 days

Project Manager, Resource Manager

$2,080.00

2.2

Identification of Resource Requirements

7 days

Project Manager, Resource Manager

$7,280.00

2.3

Budgeting

5 days

Functional Manager ,Resource Manager

$3,200.00

2.4

Development and Approval of Project Plan

2 days

Project Manager of Globex

$1,440.00

2.5

M2:Project Plan Approval

0 days

 

$0.00

3

Project Execution

32 days

 

$80,760.00

3.1

Coding of Website and smartphone Application

15 days

Coding team ,Website and Application Licensing Cost[1]

$65,400.00

3.2

Linking with database

15 days

Coding team ,Database Administrator

$10,200.00

3.3

Documenting each Activity

2 days

Archive [1],Content writer

$5,160.00

3.4

M3: Successful Coding

0 days

 

$0.00

4

Testing

36 days

 

$13,320.00

4.1

Unit Testing

10 days

Code and Application Tester

$2,400.00

4.2

System testing

7 days

Code and Application Tester

$1,680.00

4.3

User acceptance testing

12 days

Code and Application Tester

$2,880.00

4.4

Bug Fixing (if any)

5 days

Code and Application Tester

$1,200.00

4.5

Documentation

2 days

Archive [1],Content writer

$5,160.00

4.6

M4: Completion of Testing and Bug Fixation

0 days

 

$0.00

5

Go Live and Training

12 days

 

$11,120.00

5.1

Website and Application Launch

5 days

Project Manager, Project Manager of Globex

$7,200.00

5.2

Training

5 days

 

$0.00

5.3

Post implementation support

7 days

Training Team ,Functional Manager

$3,920.00

5.4

M5: Successful Go Live and Training

0 days

 

$0.00

6

Project Closure

11 days

 

$17,360.00

6.1

Documentation

2 days

Archive [1],Content writer

$5,160.00

6.2

Record Archival

2 days

Archive [1]

$5,000.00

6.3

Completion of payment

7 days

Project Manager of Globex

$5,040.00

6.4

Resource Release

1 day

Project Manager

$720.00

6.5

Client Sign off

2 days

Project Manager

$1,440.00

6.6

M6:Project completion

0 days

 

$0.00

Assumptions

The assumptions that has been considered in this project are as follows-

1. Virtucon will be able to implement the project in an inexpensive manner as possible.

2. The project will be completed within the resource allocated and within the given schedule

Project Risks

The risks associated with the project are as follows-

1. Schedule Risk
2. Budget Risk
3. Technical Risk
4. Problems with inappropriate Coding
5. Resource Risk

Risk Analysis

The analysis of the risks associated with the project is as follows-

Risk

Responsibility

Mitigation Strategy

Schedule Risk

Project Manager

Project scheduling in the planning stage

Budget Risk

Resource Manager

The budget will be prepared according to the resource needs

Technical Risk

Coding team

Appropriate project monitoring will be enforced

Problems with inappropriate Coding

Coding team

Errors per 1000 line of codes will be analysed

Resource Risk

Resource Manager

Resources will be allocated according to the project activities.

Quality Management Plan

Quality management is an important consideration of the project since it ensures that the clients are delivered with the desired output. The quality management plan takes into consideration the verification and validation activities associated with the project (Hwang & Ng, 2013). The verification activities that are a part of the project implementation plan are as follows-

1. The objectives of the project are correctly met
2. The Errors in the coding are fixed
3. Specification reviews are taken into consideration.

The validation activities associated with the project evaluation are as follows (Kerzner, 2018)-

1. The website and the application works according to the specifications
2. Desired quality of the project is met.

Annotated Bibliography

Willcocks, L. P. (2013). 9 Evaluating the Outcomes of Information Systems Plans Managing information technology evaluation—techniques and processes". Strategic Information Management, 239.

According to Williocks (2013), project evaluation is important in order to ensure that the project has been able to meet its desired goals. It is an integral process of project management that ensures that needs of the project are met by the project team members. Project evaluation is important for in information technology projects mainly because the information systems that are being developed in the project proposes needs thorough inspection about its characteristics and the features of the project. The analysis and evaluation of the project helps in easier management of the project and improves the process of project closure. It is a project management technique that ensures that the project is implemented according to the project plan and the identified objectives of the project (Kerzner & Kerzner, 2017). The evaluation process of the project covers the economic evaluation and highlights the profits or the losses that the project has met. However, there are certain concerns associated with the project evaluation techniques (Leach, 2014). This process is mainly lengthy and is often uncalled for. However, with an accurate project evaluation, it is possible to ensure that the project that will be delivered to the client meets all the expected requirements of the project.

Aziz, R. F. (2014). RPERT: Repetitive-projects evaluation and review technique. Alexandria Engineering Journal53(1), 81-93.

According to Aziz (2014), accurate estimation in the project is essential in order to ensure successful execution of the project. PERT is a project management tool that helps in easier estimation of the project activity and the cost. This is one of the major tools for project evaluation. The use of PERT chart in project evaluation helps in ensuring the clients will be delivered with a successfully completed project. Project Evaluation and Review Technique is a statistical tools that is widely used by the project managers in ensuring that correct estimation process is followed in the project. An accurate project estimation further helps in easier management and execution of the activities and the deliverables of the project. PERT methodology is quite similar to critical patyn methodology and is often used for accurate scheduling and management of the tasks associated with the successful completion of the project. Thus it can be said that PERT method is one of the major project management tool for project evaluation. A PERT chart is used for scheduling, organizing and coordinating the project management tasks. Thus it can be said that project evaluation is important part of project management.

Agyei, W. (2015). Project planning and scheduling using PERT and CPM techniques with linear programming: case study. International Journal of Scientific & Technology Research4(8), 222-227.

According to Agyei (2015), PER and CPM are two most essential techniques that are mainly used for project evaluation. Project evaluation is necessary for successful completion of the project and therefore accurate tools for project evaluation and control are needed to be identified. PERT and CRM are two of the most important project management tools that ensures successful completion and execution of the project evaluation phase. With these two methods, accurate project estimations are done that helps in easier management of the project and further helps in ensuring that the project meets the standards and the expectations of the clients. The statistical calculation of the activities and the estimation of the project time help in accurate implementation of the project. Thus these two techniques help in easier management of the project. Project evaluation is particularly important as in unveils the bugs and the issues associated with a project. The aim of the project evaluation phase is to ensure that the implemented project has followed the set standards and the contribution of these two tools in project evaluation is huge.

References

1. Agyei, W. (2015). Project planning and scheduling using PERT and CPM techniques with linear programming: case study. International Journal of Scientific & Technology Research4(8), 222-227.
2. Aziz, R. F. (2014). RPERT: Repetitive-projects evaluation and review technique. Alexandria Engineering Journal53(1), 81-93.
3. Beringer, C., Jonas, D., & Kock, A. (2013). Behavior of internal stakeholders in project portfolio management and its impact on success. International Journal of Project Management31(6), 830-846.
4. Binder, J. (2016). Global project management: communication, collaboration and management across borders. Routledge.
5. Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
6. Heagney, J. (2016). Fundamentals of project management. Amacom.
7. Hwang, B. G., & Ng, W. J. (2013). Project management knowledge and skills for green construction: Overcoming challenges. International Journal of Project Management31(2), 272-284.
8. Kerzner, H. (2018). Project management best practices: Achieving global excellence. John Wiley & Sons.
9. Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
10. Leach, L. P. (2014). Critical chain project management. Artech House.
11. Schwalbe, K. (2015). Information technology project management. Cengage Learning.
12. Willcocks, L. P. (2013). 9 Evaluating the Outcomes of Information Systems Plans Managing information technology evaluation—techniques and processes". Strategic Information Management, 239.