Lebanese Canadian University – LCU

Faculty of Arts and Science – FSA

Bachelor in Computer Science

Final project

Project Management

Presented by
Mohammad Mansour

Supervised by
Dr. Kassis

1|Page
July 26, 2021
 Table of Contents

1. EXECUTIVE SUMMARY

A) INTRODUCTION
B) SCOPE
C) VISION AND MISSION
D) OBJECTIVES

2. DELIVERABLES
3. ORGANIZATION CHART
4. ROLES & RESPONSIBILITIES
5. RESOURCE TABLE (STAKEHOLDER’S)
6. SCHEDULE
7. BUDGET
8. RISK ASSESSMENT
9. WORK BREAKDOWN STRUCTURE

2|Page
 Executive Summary

This report looks into four areas in project planning. The areas are project Charter, resource
scheduling, and project Schedule & Budget, and risk assessment. These four areas of an ATM
Software project for Maddox Bank will be discussed as planned by Sin Links Inc.
After going through each above-mentioned area, it is compared with the theoretical
frameworks of project management. By comparing, it was found out that although some of
the areas in the above-mentioned project were quite similar there were some areas that were
not. There were few differences in all four areas when they are in practice. The details can be
found in this document.

1-Introduction

The project selected is an ATM Software project taken by Sin Links Inc. to build the software
for Maddox Bank’s ATM service. Maddox Bank is a newly started bank which hopes to
expand their business nationwide. Sin Links Inc., a software solutions specialist firm, has
proposed them with a plan of action for carrying out the project. The following are the scope,
mission and vision, objectives and deliverables of the project.

a-Scope

Scope of the project is to build a fault proof software for managing the ATMs of MADDOX
bank and a user-friendly software for the ATMs which will be used by the customers of the
bank and to provide adequate training for the staff of the MADDOX Bank.

b-Vision and Mission

The vision of the Sin Links Inc. is to be the best software solutions provider in the nation.

The mission for the project is to provide the MADDOX Bank with a worsen fault proof
software that fulfills all the requirements expected by the Bank and to give proper training to
the staff.

3|Page
 c-Objectives

The objectives of the project include the following:

 Completing project on the deadline given by the MADDOX bank

 Completing the project within the given budget
 Joining the customer database of the bank with ATM software to track the accounts
 Building a software for management and ATM interface that fits the specified criteria

d-Deliverables

The following are the deliverables of the project

 The software for management and ATMs

 Installation of the software
 Project and software documentations
 Staff training

4|Page
Organizational Chart:

MADDOX
Bank
(Contractor)

Sin Links Inc.

(Project Worker)

Top Management

Project Manager

Requirements &
Design

Implementation &
Maintenances

Validation &
Support

Training, Installation
and Documentation

5|Page
Roles & Responsibilities:

1. MADDOX Bank
2. Sin Links Inc. Top Management
3. Project Manager of Sin Links Inc.
4. Requirement & Design Team
5. Implementation & Maintenance Team
6. Validation & Support Team
7. Training, Installation & Documentation Team

Task 1 2 3 4 5 6 7
Initiation x x x
Allocating Resources x
Setting up Project Environment x
Create WBS x
Project Monitoring Plan x
Managing the Project x
Schedule Updating x x
Software Management x
Develop System Requirements x
Designing x
Verification & Validation x
Testing x x x
Documentation x
Training x
Implementing x x x

Resources Table: Stakeholders

Human Resource Working Project Phase Quantity

Hours
Project Manager 1200 All 1
Requirements Analyst 120 Requirements 2
Software Designer 300 Requirements, Design 1
Programmer 800 Implementation 2
Validation Engineer 600 Requirements, Design 2
Quality Analyst 250 All 2
Database Engineer 90 Design, Implementation, Installation 1
Training Specialist 240 Training 1
Technical Writer 300 Documentation 1
Installation Specialist 50 Installation 1

6|Page
Communication Management :
Cc= ((N) x (N-1)) /2
= ((14)x(14-1)) /2
=91 communications

Schedule (Microsoft Office)

TASK START FINISH DURATION

Initiation 1/20/21

Allocating Resources 1/20/21 2/23/21 4 weeks

Setting up Project 3/2/21 4/3/21 5 weeks

Environment
Create WBS 4/3/21 5/15/21 6 weeks

Project Monitoring Plan 5/18/21 6/15/21 4 weeks

Managing the Project 5/22/21 7/10/21 7 weeks

Schedule Updating 6/1/21 8/14/21 11 weeks

Software Management 7/13/21 8/28/21 7 weeks

Develop System 7/2/21 9/4/21 7 weeks

Requirements
Designing 7/20/21 11/6/21 16 weeks

Verification & Validation 9/1/21 10/30/21 9 weeks

Testing 9/28/21 11/20/21 8 weeks

Documentation 11/20/21 12/18/21 5 weeks

Project Complete – Celebrate 12/18/21

Project Budgets

Software = $2,000,000
External fees (Risk) =$500,000
Total Project = $2,500,000

Total Project Budget includes all internal costs, fees and permits

7|Page
Risk Categorization:

Risks Low Risk Medium Risk High Risk Evidence Risk

Evidence Evidence (H) Ratin
(L) (M) g
(H, M, L)
Project Fit Fits within the Requires some Out of hand for the firm L
organizations help from outside
level
Project Team Works together Needs some Division among team L
improvement
Management Works together Delays in No support at all L
Support Support
Customer Happy Normal Upset -
Experience
Training Needs Needs little or no Needs moderate Need a lot of training M
training amount of
training
Budget Budget is enough Might need Too less for the project M
for the project additional budget
Technology Latest With few Not good enough to be M
possible faults used
Costs Low Medium High M
Project Within the Little behind the Too much time wasted M
schedule expected time time schedule,
frame can be caught up
Designing Necessary Some resources No proper resources L
Resources are has to be bought available
available or borrowed
Documenting Easy to Normal Hard to understand L
understand
Implementation Full support from Delays in support No Support L
the contractor
Testing Resources are Require No adequate way to test M
available for additional
testing support
Communication Well established normal No communication or L
among less communications
stakeholders
Quality Well checked Normal Not checked L
Assurance
Complexity System is easy to Can be used with Need experts to use -
use some training

8|Page
WORK BREAKDOWN Structure

The process of software development is divided into stages are as listed and illustrated
below:

 Requirement analysis
 Feasibility study
 Design
 Coding
 Testing
 Install/deploy
 Maintenance

THANK YOU!

9|Page