UNIVERSITY OF GONDAR

FACULTY OF INFORMATICS
DEPARTMENT COMPUTER SCIENCE
SOFTWARE PROJECT MANAGEMENT PLAN ENTITLED ON: Web Based System For Ethiopian
Insurance Corporation.

TEAM NAME: T_TA

By Tigist & Amarech

To : Mr. Abay(Asst prof)

Gondar Ethiopia

June:2018

i
Contents
1. Project charter.....................................................................................................................................2
2. System description..........................................................................................................................3
3. Project organization............................................................................................................................3
3.1. Process Model.............................................................................................................................3
3.2. Organizational Structure..............................................................................................................4
3.3. Project Responsibilities................................................................................................................4
4. Managerial process.............................................................................................................................6
4.1. Management Objectives and Priorities........................................................................................6
4.2. Risk management........................................................................................................................7
4.2.1. Cost risk...............................................................................................................................7
4.2.2. Schedule risk........................................................................................................................7
4.2.3. Performance risk..................................................................................................................7
4.2.4. Resource Risk.......................................................................................................................7
4.2.5. Technological risks...............................................................................................................7
4.2.6. Operational risk...................................................................................................................7
4.3. Monitoring and Controlling Mechanism......................................................................................8
4.3.1. Implement Risk Response............................................................................................................8
3.3.2. Risk Urgency Assessment...........................................................................................................8
3.3.3. Monitoring.................................................................................................................................8
3.3.4. Risk Reassessment.....................................................................................................................8
5. Technical processes.............................................................................................................................9
5.1. Tools............................................................................................................................................9
5.2. System documentation................................................................................................................9
6. Work elements, schedule and budget.................................................................................................9
APPENDIX....................................................................................................................................................9
Meeting Minutes.........................................................................................................................................9

1
 1. Project charter
Project title: web based system for Ethiopian insurance corporation.

Project Sponsor: Ethiopian Insurance Corporation

Project start date: May 10 2010(E.C)

project finished date: June 9, 2010(EC)

Project manager: Tigist Mintesnot

Project objectives: Develop web based system will be use by the society in different aspects of
insurance such as

a. property,

b. life and

c. liability insurances using the software.

Role: Role Responsibility

1. Project leader-----------------------------Tigist

2. Requirement Analyst-------------------Amarech

3. System designer--------------------------Tigist

4. Coding & unit tester---------------------Tigist

5. Integration tester-------------------------Both

6. Installation & training -------------------Both

Purpose

This document describes the plan to produce web based system for Insurance Corporation for
Ethiopia. The web based system will be use by the society in different aspects of insurance such
as property, life and liability insurances using the software.

 Communication strategy: Using Email

 phone communication

 Direct interviewing(face to face )

2
Assumptions

 Team members are assumed to be able to

a. perform and stay involved in the tasks that they are assigned.

b. studying, understanding and identifying the current system problems.

c. designing a solution for the problems identified.

d. perform Coding and testing.

e. performs installation of software’s.

Dependency

 good communication between team members.

 perform tasks based on the schedule.

 develop a habit of accept and resolve conflict between team members.

Constraints

 If the project cannot be finished based on deadline date so the project team must
communicate sonly.

 If one of project team member cannot finish assigned task, so the team communicate
immediately to help each other or reassign again.

Sign off(signature of all team members)

 Tigist Mintesnot-------------

 Amarech Hunie----------------

2. System description
The purpose of this project is to develop user interactive and web based system for Ethiopian
Insurance Corporation. The system to be developed allows the clients to communicate, to get
services in fast remedy and to be membership of the company by themselves without going
directly to their office

3. Project organization
3.1. Process Model

3
Team T_TA will be utilizing the iteration project development model. Using this model, Team
will be able to perform analysis and cooperation can able to rollback and perform the
development process for understanding what is needed for the software project.

3.2. Organizational Structure

The project will be completing in the following phase of schedule as following

Phase Leader Date

Phase1 Tigist Mintesnot June 1-june3
Phase2 Amarech Hunie June4-june5
Phase3 Tigist Mintesnot June6-june7

The team is formed of 2 members in whom one person would lead the team for each phase.
Phase 1.Requirment analysis
Phase2.Documentation
Phase3.Immmplementation

3.3. Project Responsibilities

All the team members will be involved in all phases of the project life cycle. The role for each
team member will change for every deliverable to ensure that no one team member is overload.

Phase Role TIGIST Amarec

h
1. Initial Project leader
×
Requirement
analysis ×
System designer
×
Coding and unit
×
Test

Integration test
× ×
Installatio,training
× ×
7. Final Project leader
×
Requirement
analysis × ×
System designer
×
Coding and unit
test × ×
Integration test
× ×
4
 1. Initial Project leader
×
Requirement
analysis ×
System designer
Coding & unit
tester × ×
Integration test
×
Project leader
×
6. Final Requirement
analysis ×
System designer
×
Coding and unit
tester ×
Integration test
×

Project Leader
 Leadership: The project leader works with the team and key stakeholders to set the
key goals and major objectives
 Decision Making/Judgment: The PL should include the team in formulating
decisions but should accept accountability for the decision. Provide an honest assessment
of the project relative to current and future cost.
 Knowledge. Understand the scientific rationale and technical issues associated with the
project target and lead agents.
 Planning. The PL is responsible for developing a project plan that works to achieve
progression criteria using sound scientific processes in the shortest amount of time with
the least cost.

5
  Influencing. Making sure all team members and their line managers and key
stakeholders support the project.
 Negotiation: The PL may need to interact directly with line managers to ensure
resources are available when needed, and to negotiate amendments to the project plan
especially those that change deliverable completion dates
 Meeting Management: The PL is responsible for organizing, facilitating and
ensuring follow-up action on issues raised in the meeting. When required, the PL will
organize corporate scientific program review.
 Communication: Keep team members and stakeholders informed of key
developments, program decisions, issues, and changes to the project and the project plan.

Requirement analysis’

Determining the needs or conditions to meet for a new or altered product, taking account of the
possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating
and managing software or system requirements

System designer

Defining the architecture, modules, interfaces, and data for a system to satisfy specified
requirements.

Coding & unit tester

One of team member tests sets of one or more computer program modules together with
associated control data, usage procedures, and operating procedures, are tested to determine
whether they are fit for use.

Integration tester

Handle testing, system performance, environmental and system troubleshooting. Analyze data,
study trade and prepare test briefings and write reports.

4. Managerial process
4.1. Management Objectives and Priorities

Project Team leader will maintain the responsibility of controlling the overall activity of the
project schedule and monitoring that all project works are completed on provided schedule.

6
Headship is also answerable for the creation of all deliverables and scheduling or running
meetings.

4.2. Risk management

The team members have identified numerous factors associated with system development failure.
first synthesize the vast research regarding systems development risk factors .Those involves
identifying, assessing various strategies that used to mitigate the adverse effects of risk on the
organization. Management uses risk management as a strategic tool to mitigate the loss of
property and increase the success chance of the organization.

4.2.1. Cost risk

Cost risk, typically escalation of project costs due to poor cost estimating accuracy and scope
creep.

4.2.2. Schedule risk

The risk that activities will take longer than expected. Slippages in schedule typically increase
costs and, also, delay the receipt of project benefits, with a possible loss of competitive
advantage.

4.2.3. Performance risk

The risk that the project will fail to produce results consistent with project specifications.

4.2.4. Resource Risk

This risk mainly arises from outsourcing and personnel related issues. If a project needs another
employee out of the team, this, leads that bringing in a new worker at a later stage in the project
can significantly slow down the project. Another source of the risk includes lack of availability
of funds. This could happen if you are relying on an external source of funding (such as a client
who pays per milestone) and the client suddenly faces a cash crunch.

4.2.5. Technological risks

This risk includes delays arising out of software & hardware defects or the failure of an
underlying service or a platform. There could be issues in the platform used to build your
software or a software update of a critical tool that no longer supports some of your functions.

4.2.6. Operational risk

7
Includes risks from poor implementation and process problems such as procurement, production,
and distribution.

4.3. Monitoring and Controlling Mechanism

While the project management team and project management team leader is doing its careful and
complete characterizations of risk, they often will find ourselves in a position in which we realize
that a particular component as to the project and or a particular part of the project will be in fact
come with a set or series of inherent risks. After all of these likely and potential risks have been
properly organized and categorized, it is up to the project management team and or the project
manager to effectively determine the best way to deal with these risks.

4.3.1. Implement Risk Response

Is the process of planning and implementing actions and plans in response to project risks. The
purpose of this process is to ensure that each of the identified risks on the Risk Register has
appropriate actions or plans to mitigate or avoid a risk before it happens or to provide a response
when a risk occurs and turns into a project issue.

The idea is to reduce the exposure to risks in the project and minimize threats to the delivery in
terms of time, cost or quality.

3.3.2. Risk Urgency Assessment

The risk urgency assessment is a project management process that reviews and determines the
timing of actions that need to happen sooner than the other risk items. The purpose of this
particular type of risk assessment is that it identifies the near term risks.

3.3.3. Monitoring

The project management term action of monitoring and controlling processes refers specifically
to those particular processes that are implemented by the project team and/or the project team
leader for the sole and explicit purposes of taking a careful and thorough measurement of and to
complete a through monitoring of the team’s project execution to date.

3.3.4. Risk Reassessment

The project team identify new risks and reassessing current ones. It is also involved in closing
risks that are outdated and no longer threatening to the project.

8
 5. Technical processes
5.1. Tools
Email: by using email application the project team communicate each other
and from others E g: stakeholders

soft ware’s : Ms office, UML , ORACLE

servers: WAMP, XAMP

5.2. System documentation
We use UML diagrams after initial and planning stage. For coding and testing first the project
team delivers all necessarily documents for design and implementing the system. In addition to
this daily and weekly meetings are good components to forward our project to be achieved

6. Work elements, schedule and budget

The Budget for this project is according to the project scheduled to be completed on June 16th 2018.

Here is summary of the timeline of major milestones:

Milestones Date(EC)
Project initiating May 10
project title selection May 20
project plane June 1-5
Presentation June 9

APPENDIX

Meeting Minutes
Date: May 5, 2018 (8:10 AM)
Place: UOG Tewodros Campus office B:10 , Room:109
Participants:
Tigist Mintesnot (Leader), Amarech Hunie
Activities:
1.we get general consensus to do project
2.Discus briefly new system
3.assign project team name by “T_TA”
4.load balancing and responsibilities:
a. Tigist - develop system
b. Amarech - Project Plan preparation
c. Tigist and Amarech- describe new system features

9
 5.Assign the next meeting date and time.
Date: May 8, 2018(2:4 PM)
Place : UOG Tewodros Campus PG library

Participants:
Tigist Mintesnot (Leader), Amarech Hunie

Activities:
1. Discus the general objectives of the system
2. Identify the beneficiaries
3. Discuss the significance of the project
4. Add meeting minute on the software project document
5.Set up next meeting

Date: May 15, 2018 (8:10 AM)

Place: UOG Tewodros Campus office B:10 , Room:109
Participants:
Tigist Mintesnot (Leader), Amarech Hunie
Activities:
1. Briefly discuss the scope and delimitation of the project

2. Assign the next meeting date and time.

Date : May 25,2018(2:4 pm)

Place: : UOG Tewodros Campus office B:10 , Room:109
Participants :
a. Tigist
b. Amarech
Activities
1. We divide the responsibilities
Tigist Mintesnot : Functional requierments
Amarech Hunie : Non functional requirements of the system
2. Assign the next meeting date and time.
Date : june 13,2018(2:4 pm)
Place: : UOG Tewodros Campus office B:10 , Room:109
Participants :
c. Tigist
d. Amarech
Activities
1. Design user interface of the system
2. The project team went through all issues for area requirements and revised requirements
for that area part.
3. Assign the next meeting date and time.

Date : june 14 , 2018(2:4 pm)

10
 Place: : UOG Tewodros Campus office B:10 , Room:109
Participants :
Tigist
Amarech
Activities
1. We descus about the over all structure of the new system
2. We implement system testing on the new system
3. Assign the next meeting date and time.
Date : june 15,2018(2:4 pm)
Place: : UOG Tewodros Campus office B:10 , Room:109
Participants :
e. Tigist
f. Amarech
Activities
1. Prepare power point for presentation
2. Submit the document to mr: Abay(asst prof)

11