Chapter Two

Information system development project

Managing information system project

Information system project phases representing and scheduling

project plans

 A specific kind of project in which an Information System is planned,

developed and implemented in an organization. Approaches and Methods

for Individual Performance Assessment in Information Systems Projects.

 An important function of information management is to reduce the risk of

legal and financial punishments against the organization.

 It achieves this with a well-defined protocol for recording, storing,

disseminating and destroying data. This reduces the chance of breaches and

improves compliance with regulations

 An information system consisting of the tools and techniques used to gather,

integrate, and disseminate the outputs of project management processes. It is

used to support all aspects of the project from initiating through closing, and

can include both manual and automated systems.

 Project planning phase

 A PMIS can be your best friend, assisting with: In-depth project scheduling,

including critical path analysis and related tasks. Supporting cost and budget

management, including setting up of cost controls, budget analysis, and related

KPI metrics. Jun 8, 2022

 Managing the Information Systems Project

1. Describing project scope, alternatives, and feasibility. ...

2. Dividing the project into manageable tasks. ...

3. Estimating resources and creating a resource plan. ...

4. Developing a preliminary schedule. ...

5. Developing a communication plan.

 All information systems projects have to go through the four phases of

planning, analysis, design, and implementation. These phases are part of the

system development life cycle (SDLC)

 The SDLC concept applies to a range of hardware and software

configurations, as a system can be composed of hardware only, software

only, or a combination of both. There are usually six stages in this

 cycle: requirement analysis, design, development and testing,

implementation, documentation, and evaluation

1. Planning: The purpose of this step is to find out the scope of the problem

and determine solutions. Constraints like resources, costs, time should also

be considered at this stage.

 Defining the problem and scope of the existing system.

 Overview of the new system and determine its objectives.

 Checking project feasibility and producing the project schedule.

 Threats, security, and any constraint.

 A feasibility report for the entire project, which is created at the end of this

phase.

2. Analysis: The stage is to determine what a business’ needs are, how they can

be met, who will be responsible for individual pieces of the project, and

when should be expected to accomplish the project.

3. Design: The stage is to explain detailedly the necessary specifications,

features, and operations that will meet the functional requirements of the

proposed system which will be in place. This is the step for end-users to

discuss and determine their specific business information needs for the

proposed system.
 4. 4. Implementation: This step puts the project into production by moving the

data and components from the old system and placing them in the new

system.

Representing and scheduling project plans

 Scheduling in project management is the listing of activities, deliverables,

and milestones within a project.

 A schedule usually includes a planned start and finish date, duration, and

resources assigned to each activity.

We can represent project plan

1. Step 1: Define your goals and objectives. ...

2. Step 2: Set success metrics. ...

3. Step 3: Clarify stakeholders and roles. ...

4. Step 4: Set your budget. ...

5. Step 5: Align on milestones, deliverables, and project dependencies. ...

6. Step 6: Outline your timeline and schedule. ...

7. Step 7: Share your communication plan.

Steps in involving in project planning and scheduling

 Define stakeholders. Stakeholders include anyone with an interest in

the project.
  Define roles. Each stakeholder's role should be clearly defined.

 Introduce stakeholders.

 Set goals.

 Prioritize tasks.

 Create a schedule.

 Assess risks

 Communications

 Project scheduling is just part of the project planning. Scheduling is

determined by the timing and sequence of operations to give
completion time, Work breakdown structure terminal elements, the
statement of work or a contract data requirements list and on needed
for completion of the project.
 The purpose of a project plan is to guide the execution and control
project phases. As mentioned above, a project plan consists of the
following documents: Project Charter: Provides a general overview of
the project. It describes the project's reasons, goals, objectives,
constraints, stakeholders, among other aspects.
 A project plan typically contains a list of the essential elements of a
project, such as stakeholders, scope, timelines, estimated cost and
communication methods. The project manager typically lists the
information based on the assignment.
 A project summary is a document that contains a concise,
comprehensive overview of an entire project and its key details. It
usually consists of a project's objectives, background information,
requirements, problems, analysis, and conclusion.

the job or activity of planning the times at which particular tasks will be done or
events will happen: production/work/crew scheduling.
1. Project scheduling is just as important as cost budgeting as it determines the

timeline, resources needed, and reality of the delivery of the project.