UNIVERSITY OF GONDAR

FACULTY OF INFORMATICS

Department of Information Technology

PostgraduateProgram
Course Name: Software Project Management

A Project Plan

On

Active Directory Domain Service for Commercial Bank

Of Ethiopia Gondar District

Submitted By:

1. AbenetAlazar(IT Regular)
2. Nigus Oumer (IT Regular)

Submitted to instructor: -Abaye T.

July2018

Gondar, Ethiopia
 Project Data

 Client: Abenet and Nigus

 Name of project: Active Directory Domain Service for Commercial Bank of Ethiopia

Gondar District

 Project participants:

No. Name of group members E_mail address Phone No.

1 Abenet Alazar abenet365@gmail.com +251918556122

2 Nigus Oumer nigoumer@gmail.com +251918596681

 Planned workload: 2 hours/day

Revision History
The following table lists a history of changes made to this document.

Version No. Date Author Description Change Request No.

Table of Contents Page

1. Project plan...............................................................................................................................1
1.1. Introduction.......................................................................................................................1
1.2. Problem definition.............................................................................................................2
1.3. Objectives..........................................................................................................................2
1.3.1. General Objective......................................................................................................2
1.3.2. Specific Objective......................................................................................................2
1.4. Deliverables......................................................................................................................3
1.5. Project organization..........................................................................................................3
1.5.1. External Structure......................................................................................................3
1.5.2. Internal structure........................................................................................................3
1.6. Project Management.........................................................................................................5
1.6.1. Management targets...................................................................................................7
1.6.2. Assumptions and dependencies.................................................................................7
1.6.3. Risk control................................................................................................................8
1.6.4. Project Risk Assessment............................................................................................9
1.7. Progress control.................................................................................................................9
1.8. Technical Procedure........................................................................................................11
1.8.1. Methods and Tools..................................................................................................12
1.8.2. Data Collection Methods.........................................................................................12
1.8.3. Development Environment......................................................................................12
1.9. Quality Plan.....................................................................................................................14
1.9.1. Documentation plan.................................................................................................14
1.9.2. Internal communication plan...................................................................................16
2. Planning..................................................................................................................................16
2.1. Work packages, sub-projects, activities and milestones.................................................16
2.2. Planned Budget...............................................................................................................17
2.2.1. Manual preparation..................................................................................................18
2.3. Communication and PR..................................................................................................18
3. Approvals...............................................................................................................................20
4. References..............................................................................................................................21
Acronyms, Abbreviations and Definitions on project plan
Terms Descriptions
ADDS Active Directory Domain Services
CBE Commercial Bank of Ethiopia
Ms Microsoft office
SPMP Software project management plan

1. Project plan

1.1. Introduction

Active Directory Domain Services (ADDS) in Windows Server 2008 to simplify user and
resource management while creating scalable, secure, and manageable infrastructures. The
domain controller is a role that network administrators assign to a server to help them manage
computers and the network. The advantage of having domain controllers in a network pertains to
the ease that administrators can enjoy when managing all the computers from one single point.
Network administrators are then able to manage portable devices that connect to the network
externally.
This is useful for remote workers and people who need to work from home. Domain controllers
are also used to authenticate user login sessions. Its role is to manage user accounts and
password, which allows for users to log onto any computer with the same credentials within the
domain. Domain controllers also allow network administrators to assign and edit group policies
which can be deployed out to the computers on the domain. Any policies pushed out from the
Domain controller will override any individual computer policy set up by the user [1].
This allows for much more control over a network, where computers are locked down. For
instance, a group policy can specify for all computers to display the same corporate wallpaper.
This will add many restrictions to users on the domain from making any system changes.
Generally, it uses to manage different users to logins and various users access rights on shared
resources over the network such as printers or shared drives.
1
Gondar district office is one of the premium districts of commercial bank of Ethiopia has more
than 170 employees, 150 computers, and about 15 printers. It also serves more than thousands of
customers per a day.

1.2. Problem definition

Nowadays, the users and the computers in Gondar district office is becoming increase. And the
following problems are observed [2]:-
 Computers are not managed properly since they are locally authorized
 Users are not managed properly
 Inefficient use of resources such as storage, processor, and Printers
 There is no security protection from the virus this results in a frequent flow of IT officer
to the district to maintain computers
 No resource management mechanisms at the district level. This means that how many
computers, printers, and users are available at district level
 There is no knowledge management system. This means that for example in the IT
department of Gondar district there are different IT officers with different knowledge but
this knowledge is not managed properly. But this has its own impact on the goals of the
organization
 Misuse of the internet connection

1.3. Objectives

The general and specific objectives of this research are as follows:

1.3.1. General Objective

The general objective of this Project is Implementing Active Directory Domain Service for
Commercial Bank of Ethiopia Gondar district.
1.3.2. Specific Objective
With the aim of achieving the above general objective, the study will also have the following
specific objectives:

 Ensures the reliable internet connection for authorized users

 Act as a focal point for the system and network administrator

2
  Implement security instrument for Access Control List authentication,
 Manage resources and check the functionality of the networked devices centrally.
 Share networked resources
 Used to make application-level filtration

1.4. Deliverables

 Project plan documents

 User manual
 Active directory domain service
 Training manuals
 Training

1.5. Project organization

The SPMP will identify the organizational entities external to the project and their interaction
with the project team, as well as internal project structure and roles and responsibilities for the
project.

1.5.1. External Structure

The external groups of this project are clients and steering committee. All formal communication
between the client and the team is facilitated by the personal contact. The communication is done
via e-mail on “as need basis” and through regular team meetings with the client and also the
communication between the steering committee done via e-mail and personal contact. Team
members are expected to participate in the client meetings. Correspondence with the client shall
be recorded and made available for later retrieval.
1.5.2. Internal structure
The team structure is hierarchical and decisions are being made using a voting mechanism in
which each team member’s vote is counted equally. It is expected that each team members will
change his role in the project at the beginning of the election. This will allow the team members
to be involved in more than one role. The team will engage in regular daily meetings.
Additionally, team members will communicate by e-mail on as needed. Personal communication
between team members is strongly encouraged.

3
 Figure 1- Internal team structure hierarchy
Client Commercial Bank of Ethiopia Gondar District
Project Active Directory Domain Service for CBE Gondar district
Title
Name Role Responsibility Tasks
Project  Controlling and adjusting  Understand project
manager the project plan. Domain
 Leading, coordinating and  Organize the project
motivating the task  Define managerial process
groups.  Identify methods and tools
 Chairing plenary project to be used
Abnet
Project meetings.  Define Software

team  Dividing work among requirement

task groups
 Realize the project
 The focal point for the
project supervisor.
Quality control  organizing the external  Identify security
communication requirements
 prepare a presentation for  Identifying features to be
clients, team members tested and not to be tested

4
  organize the final meeting
with the client
 Realize the project
 prepare user manual
Procurement  Material Specification.
Manager  Material Selection
 Contracting
 Control the purchasing
process.
Communication  Reviewing: the review
and PR procedures and their
observance.
 Document management:
Nigus
procedures that can be
used for managing the
project files,
 Determining templates,
 Test the system using
different testing
mechanisms
 Realize the project
Risk manager  Plan, Identify, Analysis
Response, Monitor and
Control the risk
OR
5
 Identify scalability
requirements
 Identify resource
requirements
 Material Specification.
 Material Selection
 Contracting
 Control the purchasing
process
 Use control measurements
to analyze and evaluate the
quality standards and
processes.
 Perform quality control
assessments and audits.
 Compare quality control
measurements against
established control limits
and tolerances.
 Identify noncompliance
and reasons for that.
 Project Risk Analysis:
 Prioritize with project risk
 Assessments
Communicate with team
members about Risks
 Plan and Implement Risk
Responses
 Register Project Risks
Role Responsibilities Participant(s)

Project  Conduct Kick-off Meeting Abnet Alazar

Manager  Developing the project plan
 Direct and Execute Approved Plan
 Monitor Project Execution
 Track deliverables, milestones, and change requests.
 Manage software release content with key stakeholders like SQA
 Setup development milestones and entry or exit criteria.
 Interlock schedules as plans with participating teams.
 Follow the project status and modify to mitigate risk and ensure success.
 Present regular project status upgrades to the steering committee
 Monitor and enhance software development, troubleshooting, and QA
process.
 Liaise between development team, customer and several third parties.
 Control and monitor Project Scope, Time, Cost, Quality and Risk
 Managing the project stakeholders
 Managing the project team
 Managing the project delivery
 Reviewing requirement documents
Quality  Review and approve project deliverables
Assurance  Provide knowledge and recommendations
Manager  Assure the quality of products that will meet the project goals and
objectives
Risk Control  Identifies risks
Manager  Evaluates risks Nigus Oumer
 Classifies risks
 Prioritizing risks
 Plans risk mitigation
 Remove project obstacles
 Track risks and mitigation plans

6
Role Responsibilities Participant(s)

 Review and adjust mitigation plans

Configuration  Creating a storage area for all documents and code

Manager  Checking that the repository is used by all team members

 Maintaining the repository according to the SCMP

Requirement  Understand, identify and elicit and prioritize the system requirements, and Abenet Alazar
Analyst document in a RAD.
 Collects feedback from the team to validate the client's actual needs.
 Prepares reports for the project manager

1.6. Project Management

1.6.1. Management targets

 Fast Secured and flexible system
 User friend and Suitable resources sharing the environment
 Easy access control mechanism for CBE Gondar district
 Easy resource management and easy problem identification mechanism
1.6.2. Assumptions and dependencies
 Technology interoperability won’t hinder the project’s progress
 The project team will deliver work as scheduled
 An assumption made on projects for human resources is that individuals will work 14
hours per week.
 The materials to complete the project will be readily available in the district office
The following assumptions will be made while planning:
 The development team has enough experience personally and as a whole to complete the
project.
 The team will work together to complete the project
 The project manager will make sure that development team members are available
throughout the development lifecycle of the project for the successful completion of the
project.
 The client will respond in a timely manner to all questions from the team

7
  Change in functional and technical requirements during the project life cycle may have
an impact on the project schedule. Any impact on schedule to these changes will be
intimated to ADDS which may result in project delay.
 Involvement of Supervisor in timely approval of documents and consultation is required.
 Consultation between the project team and steering committee shall come at no cost to
the project.
 Communications Plan will be strictly followed by the Project team members.
 The guidelines specified in the project plan will be followed by the Project team
members.
 The Project Plan may be subject to change based on various information and issues that
may occur.
 A document to be reviewed by the Supervisor shall be done within 7 days. If no
comments are received within this period of time, it will be considered as approved.

1.6.3. Constraint
The project will be planned with the following constraints
 Human resource: Additional human resource will not be available to assist the project
development.
 Time: The project team must complete the project exactly by the end period of the project
schedule. There will be no extra time to the project in a case the project may not be
completed within its schedule.

1.6.4. Risk control

This section details the major project risks that the project could face and explains the plans to
alleviate or control them. The project members identify the less probable risks that are caused by
the environmental situation, project member and the ways to manage risks in the co-operation of
the whole project work. Some of the possibilities that hinder the successful completion of our
project are:
Frequent electric power failure and fluctuations: the failure of electric power, again and
again, might affect our project progress. Since our project depends on the existence of
electric power, the project member might be disturbed with frequent power off. This leads

8
 the incompletion of the project according to a timeschedule. Even though we cannot stop
the problem, we will try to salivate this problem by working day and night
Technical, quality, or performance risks: Changes to organizational standards during the
project can also be lump into this category of risks. In order to get insight and address these
problems, we will work cooperatively with long experienced IT professionals in the project
area.

1.6.5. Project Risk Assessment

Risk Risk Level Likelihood of Mitigation Strategy

L/M/H Event
Person Hours H: Over 180 Certainty Assigned Project Manager,
communications plan
Estimated Project H: 3month Certainty Created a comprehensive project
Schedule timeline with frequent baseline
reviews
Team Size at Peak H: 5 members Certainty A
comprehensivecommunications
plan,
frequent meetings
Project Team’s M: Some have Somewhat Comprehensive
Shared Work worked together likely Communications Plan
Experience creates before
poor working
relationship

1.7. Progress control

The development methodology to be used for this project is Agile Scrum Software Development
Method. Therefore according to scrum methodology, daily meeting for 15 minutes will be held
to track project progress. The tasks will be divided and distributed and the project manager
verifies whether it’s being done according to the project schedule. Progress reports of the project
development status will be written to the supervisor every two weeks.

The team uses the following table to accomplish the project and the PM controls the progress
using the schedule.
WBS# WBS Element (work packages)Name Date Responsible
Person

9
Project Active Directory Domain Service for
title CBE
Gondar district
1 Project planning 19/09/2018-15/10/2018
1.1 Understand project domain
1.1.1 Collect the organization’s background
information
1.1.2 Identify the purpose of the system
All Team
1.1.2.1 Identify problems of the current system
Members
1.1.2.2 Identify advantages of the proposed
system
1.1.3 Identify scope of the project
1.1.4 Identify limitations of the project
1.1.5 Identify project objectives
1.1.5.1 Identify general objectives
1.1.5.2 Identify specific objectives
1.1.6 Identify project deliverables
1.2 Project organization
1.2.1 Identify the process model Abenet
1.2.2 Organize team members of the project
1.2.3 Identify roles and responsibilities
1.2.3.1 Assign roles and responsibilities
1.3 managerial process
1.3.1 Identify project tracking and control
strategy
1.3.1.1 Identify status reporting strategy
1.3.1.2 Identify management meetings strategy
1.3.1.3 Identify team members meetings
strategy
1.3.1.4 Identify stage exit strategy

10
1.4 Identify methods and tools to be used All Team
1.4.1 Identify data sources Members
1.4.2 Identify data collection methods
1.4.3 Identify analysis and design tools
1.4.4 Identify networking resources and their
Specification
1.4.4.1 Identify server specification
1.4.4.2 Identify client- server configurations
1.4.5 Identify shared materials PM
1.4.6 Identify the development environment
1.4.7 Prepare project schedule
1.4.8 Estimate project budget
2 Define Software requirement 16/10/2018-27/10/2018
2.1 Gather requirements

2.1.1 Identify functional requirements

2.1.2 Identify non-functional requirements
2.1.3 Identify security requirements
All Team
2.1.4 Identify scalability requirements
Members
2.1.5 Identify resource requirements
2.1.6 Identify miscellaneous requirements
2.2 Collecting software’s
2.3 Identify nodes
2.3.1 Identify the appropriate place of each
node
2.3.2 Identify nodes link
2.4 Hardware-software mapping
2.4.1 Identifying hardware components

1.8. Technical Procedure

11
 1.8.1. Methods and Tools
In this section, we describe the different methods, tools, and techniques to be used to develop the
ADDS for CBE Gondar district. The Project team member uses the following tools for the
development of the project
Tool Version Description
EDraw 7.5 To draw UML Diagrams
Visual Paradigm for UML 11.0 Alternative to draw UML Diagrams
MS office 2010 Word, Excel, PowerPoint used for documents,
metrics, presentations
Adobe Acrobat Creating/viewing PDF files
Dreamweaver 8.0 Used for writing server-side code
Java JDK 7u45 Java Development Kit
Eclipse IDE
Android SDK 4.4.2 Programming support
Wamp server 2.4 Store information for job search
PHP Programming languages to implement the project
Android Programming languages to implement the project

1.8.2. Data Collection Methods

A wide variety of tools and techniques exist to elicit user requirements. The data collection
methods to be adopted in this project are the following:
Interview- will have an interview with Bank managers, Employees and ICT teams and other
workers about the utilization of common resources and the new system.
1.8.3. Development methods
The team uses scrum methodology for this project. Scrum is an agile method for project
management. Its goal is to dramatically improve productivity in teams previously paralyzed by
heavier, process-laden methodologies.
Scrum is characterized by:
 A living backlog of prioritized work to be done.
 Completion of a largely fixed set of backlog items in a series of short iterations or sprints.

12
  A brief daily meeting (called a scrum), at which progress is explained, upcoming work is
described, and obstacles are raised.
 A brief planning session in which the backlog items for the sprint will be defined.
 A brief heartbeat retrospective, at which all team members reflect about the past sprint.

The development environment to be used by our team is

Microsoft server 2008 is an integrated development environment for a number of tasks, has an
“easy-to-use” interface of which the development team has experience and more secure, it will be
an optimal solution to use this configuration environment
Ms. office 2007/2010/2013

1.9. Supporting Process Plan

1.9.1. Configuration management

It is the process of identifying and defining the items in the system, controlling the changes to
these items throughout their life cycle, recording and reporting the status of items and change
requests and verifying the completeness and correctness of items.

1.9.1.1. Configuration identification method

On this Configuration identification stage:
 The components of the application will identify
 The versions of the application and documents will be identified

1.9.1.2. Configuration control method

Configuration control will consist of the following activities, as follows:
 Change requests
 Changes to a configuration item will be requested through the project manager of
active directory service project.
 Change evaluation
 The impact of a chance to the configuration item will be evaluated, usually based on
perceived risk vs. benefit with respect to schedule and the impact on other
configuration items. This evaluation will be performed by the steering committee,
client, and group of team members who are required to participate in the evaluation
of a change.
 Change approval/rejection
13
  Based on an evaluation of the change to the configuration item, permission to
change the team will be approved or rejected by the team of the project.
 Change implementation
 If the change is approved, change to the configuration item will be allowed to take
place
Team configuration and management
The team has their own roles in the documentation and implementation of the project.
Team Member Responsibility
Abenet Alazar Project Manager, Developer, Software Risk
Manager
Nigus Oumer Analyst & Design, SCM

1.10. Quality Plan

The project delivers something at the end of the project execution. When it comes to the project
initiation, the project management, and the client collaboratively define the objectives and the
deliveries of the project together with the completion timelines. During the project execution,
there are a number of project deliveries made. All these deliveries should adhere to certain
quality standards (industry standards) as well as specific client requirements. Therefore, each of
these deliveries should be validated and verified before delivering to the client. For that, there
should be a quality assurance function, which runs from start to the end of the project

1.10.1.Documentation plan

There are a number of documents that will be produced during the lifetime of the project. All
documents are the responsibility of the project team members. The lists of documents that will be
created and maintained under version control include:

 Requirement Analysis document

 System design document
 Implementation
 Software testing
 Installation
 User Manual document
 Project delivery document

14
  Self-evaluation

1.11. Change control

Review the document when changes are needed or required. Each quality review will be in a
meeting format and will require the attendance of the following participants:
 Project Manager
 Quality Analyst
 Configuration Manager

1.12. Internal communication

The ability to effectively communicate with team members is very important inprovide greater
customer satisfaction.
An internal communication strategy should:
 Enable a two-way flow of information between team members and management
 Communicate clear values and goals.
 Be comprehensive.
 Utilize appropriate methods of communication.
 Have consistent messages.
Involve the management team committed to reinforcing perceptions delivered via the
communication strategy

Item Purpose Audience Write Revie Notes (with typical

r/ wers content as an example)
Owne
r
User’s Reference manual for All technical users Cautions and license
Manual details of how to use of the terms to be reviewed
certain software(ADDS): by Legal.
Features of the The person at a Determine whether
software. client doing online help and written

15
 Provide case studies customization Abnet Nigus reference manual will
also to show how to (reports, interface) be sourced from the
use it in specific same material.
situations.
Provide instructions
on how to customize.
Quick- Provide instructions All users of the Limit initial production
Start for fast start-up using software. Nigus Abnet quantities,
Guide the software.
Trainin Quickly train users of All customers who May have to create
g the software to obtain will use the different courses or
courses the business answers software. Daily course modules for
they need with a hands-on users for Abnet Nigus different users in the
minimum of time. data entry & low- audience.
Internal hand-off level planning; and
training for customer for interpretation of
support personnel reports.

1.12.1.Internal communication plan

We planned to work for this project 2hours per day and planned to meet each member two times
per a week and to conduct the formal meeting and to perform the project.

No. Communication Frequency Means of Remark

with communication
Client One time within Face-to-Face Depend on the situation
two weeks may change
Supervisor 2 times per week Email
In the team 2 time per a week Face-to-Face, Depend on the situation the
email & phone frequency may increase

16
 2. Planning

2.1. Work packages, sub-projects, activities, and milestones

No. Tasks Duration Starting Finishing Deliverables

per day date time
1 Project planning 17 days 19/09/2018 11/10/2018
1.1 Understanding the project 2 19/09/2018 26/09/2018
domain
1.2 Project organization 3 22/09/2018 26/09/2018 Assignment

1.3 Defining the managerial 1 27/09/2018 30/09/2018 description

process document

1.4 Identifying method and tools 2 01/10/2018 02/10/2018

1.5 Preparing project scheduling 2 03/10/2018 04/10/2018
1.6 Estimate project budget 3 05/10/2018 07/10/2018
1.7 Interview users to define 2 08/10/2018 09/10/2018
needs
1.8 Producing Final configuration 2 10/10/2018 11/10/2018
management plan
2 Defining software 7 days 18/10/2018 24/10/2018 Project
Requirement checklists
2.1 Gather requirement 2 18/10/2018 19/10/2018 and Project
2.2 Define server requirements 1 20/10/2018 23/10/2018 plan
such as hardware, OS, and document
services
2.3 Collecting comment 1 21//10/2018 24/10/2018
2.4 Produce final result 3 22/10/2017 24/10/2018

2.2. Planned Budget

Activities Unit Quantity Payment type Unit Total in

cost in Birr
Per- Per-

17
 diem hour Birr
Data collection No. 2 persons
Design No. 2 persons
Analysis No. 2 persons
Workshop Employees No. 40 Tea 30 1200
break
Guests No. 12 250 3000
Communication No. 3 100 300
and Transport
Contingency cost 3500
Total cost No. 8,000.00

2.2.1. Manual preparation

Activity Unit amount Unit cost Total cost
Copy Page 50 0.75 37.50
Binding Manual 50 8.00 400
Total cost 437.50
Overall cost 8,874.50

2.3. Communication

Communications management is another key component to project success. So to be

accomplishing this project we use email, mobile phone, and face-to-face communication. If there
is the unwanted situation occurs, we will have an urgent meeting rather that formal preliminary
meeting. During our formal meeting, each team members must actively participate and plan their
work for the next phase of the project. Generally, the team plans to communicate with the
supervisor and the clients two times a week via email and phone [3].
The PM generates and provides weekly project status to the Project Advisor and the steering
committee through email. There are 5 weekly status or progress reports and meeting minutes in
detail. All team members are required to present in all as needed daily status meetings.

18
In addition to the aforementioned means of reporting and project communication, the team
members are recommended to communicate through different communication channels as
needed.
2.4. Information

The stakeholders of this project are:

 Clients
 Supervisor
 Project manager
 Project team members

The stakeholders have the following general information requirements:

Stakeholder Description Format(s) Frequency

Clients  Schedule  Paper As needed
Steering  Assignment description & Project  Email Weekly
committee plan (Two weeks)
 Minutes
 Progress report
 Project documents
Supervisor  Assignment description & Project  Email Weekly
plan (Two weeks)
 Minutes
 Progress report
 Project documents
ADDS Project  Assignment description & Project  Email As created or
Manager plan  Oral changed
 Minutes
 Progress report
 Project documents
 Project status updates
Project team  Assignment description & Project  Email As created or
members plan  oral changed
 Minutes
 Progress report
 Project documents
 Project status updates

2.5. Distribution

19
The following distribution matrix illustrates which participants should receive which specific
items of communication.

Steering committee

Project Manager

Quality Analyst

Configuration
Management
Programmer
Document /Item Distribution

Supervisor

Risk Mgt
Designer
Method

Analyst

Client
Weekly status meeting minutes
Email x X X x x x x x X
Weekly progress report Email x X X x x X
Assignment description Email x X X x x x X X
Hard copy
Requirement Analysis Email x X X x x x x x X
System Design Email x X X x x x x x X
Software Project Management Email X X X x x x x x X
Plan (SPMP)
SPMP updates Email x X X x x x x x X
Implementation documents Email X X X x x x x X
User manual documents Email, X X X X
Hard copy
Project status updates Email X X X x x x x x X

3. Approvals
Document acceptance and release form of the project Describe document acceptance and release
for this project plan. The following approval signatures are required in order to confirm approval
to and validity of the above acceptance plan.

Name Role Date Signature

Nigus Oumer ______________ _______________ _______________

Abenet Alazar ______________ _______________ ________________
_
Customer Representative ______________ _______________ ________________
_
Accepted By:

Name: _____________________
20
 Signature: ___________________

Date: _______________________

4. References

[1] Open Group Student Guide HP-UX System and Network Administration II H3065S F.00,
Hewlett-Packard Development Company, L.P, USA, 2005.

[2] "http://www.icde.org/filestore/Resources/Handbooks/e-earningAndDistanceEducation.pdf,"
[Online].

[3] S. Johnson, Key issues for e-resource collection development: a guide for libraries, January
2012.

21