QUT IFN700 Project Plan: Case Study - Legal Documents Online System

This project plan presents a case study on implementing an information system for legal documents online (LDO) within Australia. The plan outlines the business drivers, project objectives (including competitive advantage and online process improvements), and business benefits, framed using the SMART goals framework. It defines the project scope, including a scope statement, product breakdown structure, product flow diagram, work breakdown structure, precedence table, network diagram, and critical path analysis. The selected methodology is PRINCE2, justified for its structured approach to project management. Key stakeholders and their responsibilities are identified. The solution involves implementing an information system for various legal document types. The plan addresses key risks (budget shortfall, schedule slippage, testing issues, and late supply) and proposes mitigation strategies. Delivery and release planning are visualized via a Gantt chart. Project control measures are also discussed. The plan adheres to the requirements of the IFN700 assignment, including referencing and the use of the provided template.

Running head: PROJECT MANAGEMENT
Project management: Case Study- The Legal Documents online
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
1. Business driver.............................................................................................................................2
2. Project objectives.........................................................................................................................2
3. Business benefits.........................................................................................................................3
4. Project scope................................................................................................................................4
4.1 Scope statement.........................................................................................................................4
4.2 Work breakdown structure....................................................................................................4
4.3 Precedence table....................................................................................................................5
4.5 Critical path...........................................................................................................................7
5. Selected methodology justification..............................................................................................8
6. Key stakeholders..........................................................................................................................8
7. Outline solution.........................................................................................................................12
8. Key risks....................................................................................................................................12
9. Delivery and release planning...................................................................................................15
10. Project control..........................................................................................................................15
11. Project costs.............................................................................................................................16
Bibliography..................................................................................................................................24

2
PROJECT MANAGEMENT
Revision history
Date Changes done
10-10-2019 Adding product breakdown structure for
providing overview about the working of the
information system that is mainly
implemented in LDO
22-09-2019 Adding network diagram as well as work
breakdown structure in the project for
providing proper overview about the project
activities which will be executed.
1. Business driver
The paper mainly reflects the legal documents online that helps in selling different types
of information about various companies, properties, individuals, solicitors as well as
conveyances within Australia. The information that LDO includes information about the current
ownership of the company, property title-based certificates, rates certificates, transport interest as
well as property description. It is found that the organization is mainly creating a plan as per
which they will implement one of the information systems that will be beneficial in providing
proper one stop shop for the various types of information which is mainly listed. This will further
help in allowing the clients for properly placing orders as well as monitoring the status of the
orders. Thus, it is found that with the help of the information system they generally act as one of
the brokers between the providers of information as well as LDO clients. With the
implementation of information system, the entire procedure is made online. Moreover, if the

3
PROJECT MANAGEMENT
entire project are not easily undertaken then it will mainly create a lot of problems in properly
handling the information quite manually.
2. Project objectives
The project objectives are mainly listed below:
 To implement an information system within an organization for providing one stop shop
for the different types of information about various companies, properties, individuals,
solicitors as well as conveyances within Australia.
 To gain proper competitive advantage in the market by making the entire process of the
organization online so that more clients get linked with the organization
 To keep record of the information that is shared and the status of the orders including the
retrieve result for future use.
 To integrate with the present system so that the information can be transferred to the
present online system
3. Business benefits
It is found that in order to reflect the advantages from the present system, it is found that
SMART goals are mainly utilized as they are mainly helpful in guiding the entire procedure of
goal setting and further focuses on the efforts for increasing the chances of achieving the project
goal. The business benefits as per the SMART goal are elaborated below:
Specific: The main benefit that will be achieved is the implementation of IT system in
LDO for managing the project activities.

4
PROJECT MANAGEMENT
Measurable: The successful IT implementation helps in managing the work purposes of
LDO online including the management of information and further helps in gaining proper
competitive advantage within the entire market.
Assignable: The project manager generally plays a significant role in properly
implementing the information system so that the implementation process can get accomplished
in the budget and time that is mainly assumed such that it plays a significant role in realizing the
business-related benefits in the project (Joslin & Muller, 2015).
Realistic: Due to the information system implementation within LDO, the organization
can be able to allow the various clients for properly placing orders as well as properly monitoring
the status of the orders (Hornstein, 2015). In addition to this, the system will also help in
retrieving results and assist in the procedure of invoicing.
Time related: It is found that the information system for the organization LDO can get
completed by 31st December
4. Project scope
4.1 Scope statement
It is found that as the project uses PRINCE2 methodology during the implementation of
an information system. The project scope includes designing of the system, development of code,
code validation, database development as well as adding functionality like placing order,
monitoring order, searching results and payment. On the other hand, it is found that there are a
number of project activities which are not considered important and therefore not included
within the project and those activities include training facility, providing information about the
suppliers and contractors.

5
PROJECT MANAGEMENT
Information system for LDO
Order Monitor Status Payment
Placing
order Checking Receiving
payment
4.2 Product breakdown structure
Figure 1: Product breakdown Structure
(Source: Created by Author)

6
PROJECT MANAGEMENT
Start
Order
Process
Decision
Information
Payment
END
Order cancel
No
Yes
4.3 Product flow diagram
Figure 2: Product flow diagram
(Source: Created by Author)

7
PROJECT MANAGEMENT
4.4 Work breakdown structure
Implementation of
information system for
LDO
Planning phase
Focussing on the
problem
Proposing solution
Creating project
plan
Stakeholder
identification
Getting approval on
the project plan
Designing phase
Collecting ideas
Getting review from
the clients
Developing design
Undertaking
feasiability study
Analysis of budget
Organizing meeting
Final design
approval
Coding
Prototype
construction
Development pf
database
Code validation
Testing of
cross-browser
Optimization
Navigation structure
development
Site content pages
development
Developing user
experience
Details update
Information update
Project requirement
Providing order
place functionality
Providing status
retrive functionality
Providing payment
functionality
Project closure phase
Risk assesment
Managing quality
Final review
Figure 3: Work breakdown Structure
(Source: Created by Author)
4.5 Precedence table
The table which is generally provided below helps in reflecting that the precedence for
each of the activities of the project is generally helpful in successfully implementing the system.
WBS Task Name Duration Predecessors
0
Implementation of information system for
LDO
77 days
1 Planning phase 11 days
1.1 Focussing on the problem 3 days
1.2 Proposing solution 2 days 2
1.3 Creating project plan 3 days 3
1.4 Stakeholder identification 2 days 4

8
PROJECT MANAGEMENT
1.5 Getting approval on the project plan 1 day 5
2 Designing phase 25 days
2.1 Collecting ideas 4 days 6
2.2 Getting review from the clients 3 days 8
2.3 Developing design 5 days 9
2.4 Undertaking feasibility study 3 days 10
2.5 Analysis of budget 5 days 11
2.6 Organizing meeting 4 days 12
2.7 Final design approval 1 day 13
3 Coding 19 days
3.1 Prototype construction 3 days 14
3.2 Development pf database 5 days 16
3.3 Code validation 4 days 17
3.4 Testing of cross-browser 3 days 18
3.5 Optimization 2 days 19
3.6 Navigation structure development 1 day 20
3.7 Site content pages development 1 day 21
4 Developing user experience 5 days
4.1 Details update 2 days 22
4.2 Information update 3 days 24

9
PROJECT MANAGEMENT
5 Project requirement 10 days
5.1 Providing order place functionality 3 days 25
5.2 Providing status retrieve functionality 4 days 27
5.3 Providing payment functionality 3 days 28
6 Project closure phase 7 days
6.1 Risk assessment 3 days 29
6.2 Managing quality 3 days 31
6.3 Final review 1 day 32

10
PROJECT MANAGEMENT
4.6 Network path

11
PROJECT MANAGEMENT
Figure 4: Network diagram
(Source: Created by Author)
4.7 Critical path
Figure 5: Work breakdown structure
(Source: Created by Author)