Running head: PROJECT MANAGEMENT

Project management

Name of the Student

Name of the University

Author’s Note
 Table of Contents
1. Project scope statement..........................................................................................................2

2. Stakeholder register and stakeholder management strategy..................................................2

3. Team contract.........................................................................................................................3

4. Financial analysis...................................................................................................................5

5. SDLC model for the project and justification for the phases.................................................7

6. Work breakdown structure.....................................................................................................8

7. Gantt chart............................................................................................................................11

8. Critical path method.............................................................................................................12

9. Float......................................................................................................................................13

10. Communication management plan.....................................................................................15

PROJECT
11. MANAGEMENT
Five potential risks in the project.......................................................................................16
1

12. Weekly status repot............................................................................................................19

Bibliography.............................................................................................................................20
 1. Project scope statement

In-scope

The project scope includes the following:

 Development of the information system for the organization “Bendigo Tours

&Travel

 Providing facility of worldwide reservation of hotel, worldwide car rental,

catering and more

 Requirement of new information system for securing the online reservation

 Completing the project 7 months as per the initial planning.

Out-scope

The out scope

PROJECT of the project include:
MANAGEMENT
2

 Information about the project suppliers are not given

 Training facility are not given to the workers of the organizations

2. Stakeholder register and stakeholder management strategy

The management strategy as well as stakeholder register for the two project

stakeholders are generally given below:

Stakeholder Power Interest

Sponsor High Low
Project manager High High
 Figure 1: Stakeholder matrix

(Source: Created by Author)

It is found that in order manage the stakeholders effectively, it is very much necessary

to utilize strategies that are generally listed below:

PROJECT MANAGEMENT
3  Proper mapping of the stakeholders

 Influencing the stakeholders of the project quite properly

 Identification of the triggers of the project

3. Team contract

The project generally focusses on developing proper team contract and then utilize it

in order to manage the performance of the team. It is found that the benefits from the contract

mainly includes commitment, proper values as well as clear expectations about the project so

that proper decision related with the project can be made in order to develop high quality of

work.
 Code of conduct

As a project team, it is very much necessary to follow steps that are generally listed

below:

 Working proactively in order to resolve the problems

 Keeping team members informed about the project

 Focusing on the activities that is best for the entire team

Participation

The participation of the team members generally includes:

 It is necessary for the team members to work with each activity of the project with

honesty
PROJECT MANAGEMENT
4
 Encouraging the team work in context with diversity

 Providing equal opportunities to each team members

Communication

The communication of the team will generally include:

 It is quite important to decide as a team in order to communicate about different types

of information

 Presenting various ideas very much clearly

 Arranging proper meeting with the team members in order to hear about the problems

Problem solving

It is quite necessary to focus on the following problem solving skills

  Encouraging each of the participant so that they ca solve problems

 Striving or building each other’s plan for the project

4. Financial analysis

The financial analysis for the \information system development is generally given

below:

Project

Cost-

Benefit

Analysis                
Analysis

Variables:                
                 
Discount 9.00
PROJECT MANAGEMENT
5 Rate Used %              
$

Annual 3,20,0

Benefits 00.00              
$

Maintenanc 55,00

e cost 0.00              
One-Time $

Developmen 6,80,0

t Cost 00.00              
Year of

        Project        
TOTA

    0 1 2 3 4 5 LS
                 
Economic   $0.00 $ $ $ $ $  
 3,20,00 3,20,00 3,20,00 3,20,00 3,20,00

Benefit 0.00 0.00 0.00 0.00 0.00

Discount 1.000

Rate   0 0.9174 0.8417 0.7722 0.7084 0.6499  

PV of $2,93,5 $2,69,3 $2,47,0 $2,26,6 $2,07,9

Benefits   $0.00 77.98 37.60 98.71 96.07 78.04  

                 
$ $ $ $ $ $

NPV of all 2,93,57 5,62,91 8,10,01 10,36,7 12,44,6 12,44,

BENEFITS   $0.00 7.98 5.58 4.29 10.36 88.40 688.40

                 

$(6,80

One-Time ,000.0

COSTS   0)            
                 
PROJECT MANAGEMENT $ $ $ $ $
6
Recurring (55,000 (55,000 (55,000. (55,000 (55,00

Costs   $0.00 .00) .00) 00) .00) 0.00)  

Discount 1.000

Rate   0 0.9174 0.8417 0.7722 0.7084 0.6499  

PV of $ $ $ $ $

Recurring (50,458 (46,292 (42,470. (38,963 (35,74

Costs   $0.00 .72) .40) 09) .39) 6.23)  

                 

$(6,80 $ $ $ $ $ $

NPV of all ,000.0 (7,30,4 (7,76,7 (8,19,22 (8,58,1 (8,93,9 (8,93,9

COSTS   0) 58.72) 51.12) 1.21) 84.59) 30.82) 30.82)

                 
Overall               $

NPV 3,50,7
 57.58
                 
Overall

ROI                
                0.3924

5. SDLC model for the project and justification for the phases

Agile methodology is generally utilized for the development of information system o.

It is found that the agile methodology generally breaks the project into smaller pieces which

is then prioritized by the team members in terms of significance. In addition to this, it is

found that agile methodologies are generally helpful in reducing the challenges which are

mainly related with the work of the project.

The phases of the project that are mainly selected for the agile methodology are

generally elaborated below:

PROJECT MANAGEMENT
Initiation phase: In the initiation phase, proper analysis on the project requirement
7

are generally made in order to start with the work of the project.

Planning phase: In this project phase, proper conversation with the stakeholders are

done and proper proposal for the project is development so that the project stakeholders can

start with the project work.

Designing phase: In the designing phase of the project, proper project design is

developed by gathering proper ideas about the project and by developing proper design.

Development phase: In the development phase, the activities that are generally

undertake includes prototype development, database development, code validation, site

content pages as well as helps in providing proper user experience in context to ticketing,

catering and more.

 Closure phase: In the closure phase of the project, entire project is reviewed and then

stakeholder sign off is done for closing the project.

6. Work breakdown structure

The WBS for the information system is provided below:

WBS Task Name

Development of an information system for an organization
0
Bendigo Tours &Travel
1 Project planning phase
1.1 Discussing with stakeholders
1.2 Creating project proposal
1.3 Project agreement
1.4 Stakeholders with the engagement
1.5 Project plan approval
2 Web application design
2.1 Developing concepts for design
2.2 Proper idea gathering
PROJECT
2.3 MANAGEMENT
Development of project design
8
2.4 Checking feasibility of the project
2.5 Project budget analysis
2.6 Arrangement of meeting
2.7 Approval about the design of the project
3 Implementation phase
3.1 Coding
3.1.1 Developing the project prototype
3.1.2 Developing the database for the information system
3.1.3 Code validation
3.1.4 Testing of cross-browser
3.1.5 Optimization
3.2 Web content development
3.2.1 Development of site content pages
3.2.2 Navigation structure development
3.3 User experience
3.3.1 International Airline Reservations & Ticketing
3.3.2 Worldwide hotel reservation
3.3.3 Cruises world-wide & locally
3.3.4 Requirement of the project
3.3.5 Meet & Assist services.
3.3.6 Conferences
 3.3.7 Catering
4 Project review phase
4.1 Risk assessment
4.2 Planning for quality management
4.3 Final review
4.4 Integration of website with social media
5 Project closure phase
5.1 Assessment of different types of risks
5.2 Proper management of quality
5.3 Final review

PROJECT MANAGEMENT
9
 7. Gantt chart

The Gantt chart that is provided below helps in reflecting on the estimation of activity

resources, allocation of the activity resources as well as the sequence activities of the project.

PROJECT MANAGEMENT
10

Figure 2: Gantt chart

(Source: Created by Author)

 8. Critical path method

The critical path of the project is generally reflected below in the Gantt chart.

PROJECT MANAGEMENT
11

Figure 3: Critical path

(Source: Created by Author)

 9. Float

The float in the project is generally reflected in the table below:

Task Name Duration Float

Development of an information system for an
7 mons 0 mons
organization Bendigo Tours &Travel
Project planning phase 0.95 mons 0 mons
Discussing with stakeholders 3 days 0 days
Creating project proposal 8 days 0 days
Project agreement 4 days 0 days
Stakeholders with the engagement 3 days 0 days
Project plan approval 1 day 0 days
Web application design 0.65 mons 0 mons
Developing concepts for design 4 days 115 days
Proper idea gathering 2 days 115 days
Development of project design 4 days 0 days
Checking feasibility of the project 3 days 114 days
Project budget analysis 3 days 0 days
Arrangement
PROJECT of meeting
MANAGEMENT 4 days 0 days
12 Approval about the design of the project 2 days 0 days
Implementation phase 5.15 mons 0 mons
Coding 1.05 mons 0 mons
Developing the project prototype 7 days 0 days
Developing the database for the information
5 days 0 days
system
Code validation 2 days 0 days
Testing of cross-browser 5 days 0 days
Optimization 2 days 0 days
Web content development 0.15 mons 0 mons
Development of site content pages 3 days 84 days
Navigation structure development 2 days 0 days
User experience 4 mons 0 mons
International Airline Reservations &
5 days 0 days
Ticketing
Worldwide hotel reservation 4 days 0 days
Cruises world-wide & locally 4 days 0 days
Requirement of the project 3 mons 0 mons
Meet & Assist services. 2 days 0 days
Conferences 5 days 5 days
 Catering 3 days 0 days
Project review phase 0.2 mons 0 mons
Risk assessment 1 day 0 days
Planning for quality management 1 day 0 days
Final review 2 days 3 days
Integration of website with social media 2 days 0 days
Project closure phase 0.15 mons 0 mons
Assessment of different types of risks 1 day 0 days
Proper management of quality 1 day 0 days
Final review 1 day 0 days

10. Communication management plan

The communication management plan for communicating with the team members of

the project are generally provided below:

Audience Message Vehicle Frequency Responsible

Project manager The team leaders Email, face to Monthly Team leader
discusses about face
the status of the
project with the
PROJECT MANAGEMENT
project managers.
13
Project team The project team Email, face to Weekly Team members
leaders members face
discusses the
issues that are
mainly associated
with the project.
Team members The project face to face Once Project
manager manager
generally
discusses about
the objectives
and project goals
that are needed to
be achieved
within the
project.
Financial The team leaders face to face Once Team leader
manager informs the
financial
manager about
the issues that are
associated with
the project
budget
 11. Five potential risks in the project

Risk Description Impact Likelihood Mitigation

Improper If the Major Possible It is quite
scheduling scheduling of necessary to
the project is track the
not done schedule of the
properly then project on a
number of regular basis for
problems can making sure
occur that that the project
further can is on right track.
obstruct the
project
progress.
Budget shortfall If the budget Major Probable It is quite
that is approved necessary to
for the project is estimate the
not enough then budget of the
it is found that project properly
financial issues so that the
as well as project does not
challenges can face any type of
generally occur financial
PROJECT MANAGEMENT
within the challenges.
14
project.
Technical issue If the Extreme Probable It is very much
integration of necessary to
information of hire
information experienced
system is not team leaders for
done with the completing the
social media project work.
then number of
problems and
issues related
with the work
of the project
can generally
occur.
Improper If the project is Moderate Possible It is very much
management not managed necessary to
properly then it manage the
is very much work of the
difficult to project
finish the entire effectively so
project on time. that the project
gets competed
on time.
 Improper skills If the team Minor Probable It is very much
and experience members does important to
of team not have proper hire
members skills and experienced and
experience then skilled team
they are unable members for
to complete the finishing the
project. wok of the
project.

Extreme Technical
issue
Major Improper Budget
scheduling shortfall
Impact

Moderate Improper Improper

experience management,
Minor
Insignifican
t
Remote Unlikely Possible Probable Highly
probable
Likelihood
PROJECT MANAGEMENT
15

12. Weekly status repot

Week Progress report

Week 1 Information about the requirements of the
project are gathered by focussing on the
business case study of the project.
Week 2 Feasibility of the project is analyzed for
making sure that the project is feasible and
it get completed within budge.
Week 3 Proper design for the project is developed
so that as per the design of the project, the
entire project is progressed
Week 4 Approval for the project design is generally
get from the higher authority of the
organization.
Week 5 After the approval of the design, the
information system for the organization is
devalued for meeting the needs and
requirements of the project.
 PROJECT MANAGEMENT
16
 Bibliography

Badewi, A., 2016. The impact of project management (PM) and benefits management (BM)

practices on project success: Towards developing a project benefits governance

framework. International Journal of Project Management, 34(4), pp.761-778.

Calvo-Mora, A., Navarro-García, A. and Periañez-Cristobal, R., 2015. Project to improve

knowledge management and key business results through the EFQM excellence

model. International Journal of Project Management, 33(8), pp.1638-1651.

Conforto, E.C., Salum, F., Amaral, D.C., da Silva, S.L. and de Almeida, L.F.M., 2014. Can

agile project management be adopted by industries other than software

development?. Project Management Journal, 45(3), pp.21-34.

Costantino, F., Di Gravio, G. and Nonino, F., 2015. Project selection in project portfolio
PROJECT MANAGEMENT
17 management: An artificial neural network model based on critical success

factors. International Journal of Project Management, 33(8), pp.1744-1754.

de Carvalho, M.M., Patah, L.A. and de Souza Bido, D., 2015. Project management and its

effects on project success: Cross-country and cross-industry comparisons. International

Journal of Project Management, 33(7), pp.1509-1522.

Golini, R., Kalchschmidt, M. and Landoni, P., 2015. Adoption of project management

practices: The impact on international development projects of non-governmental

organizations. International Journal of Project Management, 33(3), pp.650-663.

Hornstein, H.A., 2015. The integration of project management and organizational change

management is now a necessity. International Journal of Project Management, 33(2),

pp.291-298.
 Kaiser, M.G., El Arbi, F. and Ahlemann, F., 2015. Successful project portfolio management

beyond project selection techniques: Understanding the role of structural

alignment. International Journal of Project Management, 33(1), pp.126-139.

Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project

risk management methodology for small firms. International journal of project

management, 32(2), pp.327-340.

Sánchez, M.A., 2015. Integrating sustainability issues into project management. Journal of

Cleaner Production, 96, pp.319-330.

Sears, S.K., Sears, G.A., Clough, R.H., Rounds, J.L. and Segner, R.O., 2015. Construction

project management. John Wiley & Sons.

Serra, C.E.M. and Kunc, M., 2015. Benefits realisation management and its influence on

PROJECT
project MANAGEMENT
success and on the execution of business strategies. International Journal of Project
18
Management, 33(1), pp.53-66.

Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual

framework for project governance. International Journal of Project Management, 32(8),

pp.1382-1394.

Zheng, X., Le, Y., Chan, A.P., Hu, Y. and Li, Y., 2016. Review of the application of social

network analysis (SNA) in construction project management research. International journal

of project management, 34(7), pp.1214-1225.