ITT 06105: PROJECT MANAGEMENT

LECTURE 2: Project Management and Tools

A project is a group of tasks that need to be completed to reach a clear result. A project also defined
as a set of inputs and outputs that are required to achieve a goal.
Projects can vary from simple to difficult and can be operated by one person or a hundred.
Projects are usually described and approved by a project manager or team executive.
They go beyond their expectations and objectives, and it's up to the team to handle logistics and
complete the project on time. For good project development, some teams split the project into
specific tasks so they can manage responsibility and utilize team strengths.
What is software project management?
Software project management is the art and discipline of planning and supervising software
projects. It
is a sub-discipline of software project management in which software projects planned,
implemented, monitored and controlled
It is a procedure of managing, allocating and timing resources to develop computer software that
fulfills requirements.
In software Project Management, the client and the developers need to know the length, period
and cost of the project.
Three tenets of software project management
There are three needs for software project management. These are:
1. Time
2. Cost
3. Quality
It is an essential part of the software organization to deliver a quality product, keeping the cost
within the client's budget and delivering the project as per schedule.
There are various factors, both external and internal, which may impact this triple factor. Any of
the factors can severely affect the other two.
Project Manager
A project manager is a character who has the overall responsibility for the planning, design,
execution, monitoring, controlling, and closure of a project.
A project manager represents an essential role in the achievement of the projects.
A project manager is a character who is responsible for giving decisions, both large and small
projects. The project manager is used to manage the risk and minimize uncertainty.
Every decision the project manager makes must directly profit their project.
Role of a Project Manager:
1. Leader
A project manager must lead his team and should provide them direction to make them understand
what is expected from all of them.
2. Medium:
The Project manager is a medium between his clients and his team. He must coordinate and transfer
all the appropriate information from the clients to his team and report to the senior management.
3. Mentor:
He should be there to guide his team at each step and make sure that the team has an attachment.
He provides a recommendation to his team and points them in the right direction.
Responsibilities of a Project Manager:
1. Managing risks and issues.
2. Create the project team and assigns tasks to several team members.
3. Activity planning and sequencing.
4. Monitoring and reporting progress.
5. Modifies the project plan to deal with the situation.
Software Project Management Activities
Software Project Management consists of many activities, that includes planning of the project,
deciding the scope of product, estimation of cost in different terms, scheduling of tasks, etc.
This activities are as follows:
1. Project planning and Tracking
2. Project Resource Management
3. Scope Management
4. Estimation Management
5. Project Risk Management
6. Scheduling Management
7. Project Communication Management
8. Configuration Management
 1. Project Planning: It is a set of multiple processes, or we can say that it a task that
performed before the construction of the product starts.
2. 2. Scope Management: It describes the scope of the project.
Scope management is important because it clearly defines what would do and what would
not. Scope Management create the project to contain restricted and quantitative tasks,
which may merely be documented and successively avoids price and time overrun.
3. Estimation management: This is not only about cost estimation because whenever we start
to develop software, but we also figure out their size (line of code), efforts, time as well as
cost.
If we talk about the size, then Line of code depends upon user or software requirement.
If we talk about effort, we should know about the size of the software, because based on the
size we can quickly estimate how big team required to produce the software.
If we talk about time, when size and efforts are estimated, the time required to develop the
software can easily determine.
When we talk about cost, it includes all the elements such as:
• Size of software
• Quality
• Hardware
• Communication
• Training
• Additional Software and tools
• Skilled manpower

4. Scheduling Management: Scheduling Management in software refers to all the activities to

complete in the specified order and within time slotted to each activity.
Project managers define multiple tasks and arrange them keeping various factors in mind.
Scheduling activities includes:
• Find out multiple tasks and correlate them.
• Divide time into units.
• Assign the respective number of work-units for every job.
• Calculate the total time from start to finish.
• Break down the project into modules
5. Project Resource Management: In software Development, all the elements are referred to as
resources for the project. It can be a human resource, productive tools, and libraries.
Resource management includes:
• Create a project team and assign responsibilities to every team member
• Developing a resource plan is derived from the project plan.
• Adjustment of resources

6. Project Risk Management: Risk management consists of all the activities like identification,
analyzing and preparing the plan for predictable and unpredictable risk in the project.
Several points show the risks in the project:
• The Experienced team leaves the project, and the new team joins it.
• requirement changes.
• Change in technologies and the environment.
• Market competition.
6. Project Communication Management: Communication is an essential factor in the
success of the project. It is a bridge between the client, organization, team members, and
as well as other stakeholders of the project such as hardware suppliers

From the planning to closure, communication plays a vital role. In all the phases,
communication must be clear and understood. Miscommunication can create a big blunder
in the project.
8. Project Configuration Management: Configuration management is about controlling
the changes in software like requirements, design, and development of the product.
The primary goal is to increase productivity with fewer errors.

Reasons show the need for configuration management:

• Several people work on software that is continually updated.
• Help to build coordination among suppliers.
• Changes in the requirement, budget, schedules need to be accommodated.
• Software should run on multiple systems.

Tasks perform in Configuration management:

• Identification
 • Baseline
• Change Control
• Configuration Status Accounting
• Configuration Audits and Reviews

People involved in Configuration Management are:

LECTURE 4b: Project Management Tools

To manage the Project management system adequately and efficiently, we use Project management
tools.
GANTT CHART
Gantt Chart first developed by Henry Gantt in 1917. Gantt chart usually utilized in project
management, and it is one of the most popular and helpful ways of showing activities displayed
against time. Each activity represented by a bar.
Gantt chart is a useful tool when you want to see the entire landscape of either one or multiple
projects. It helps you to view which tasks are dependent on one another and which event is coming
up.
PERT CHART

PERT is an acronym of Programme Evaluation Review Technique. In the 1950s, it is developed

by the U.S. Navy to handle the Polaris submarine missile programme.
In Project Management, PERT chart represented as a network diagram concerning the number of
nodes, which represents events.
The direction of the lines indicates the sequence of the task. In the above example, tasks between
"Task 1 to Task 9" must complete, and these are known as a dependent or serial task. Between
Task 4 and 5, and Task 4 and 6, nodes are not depended and can undertake simultaneously. These
are known as Parallel or concurrent tasks. Without resource or completion time, the task must
complete in the sequence which is considered as event dependency, and these are known as
Dummy activity and represented by dotted lines
Logic Network
The Logic Network shows the order of activities over time. It shows the sequence in which
activities are to do.
Distinguishing events and pinning down the project are the two primary uses. Moreover, it will
help with understanding task dependencies, a timescale, and overall project workflow.
Product Breakdown Structure

Product Breakdown Structure (BBS) is a management tool and necessary a part of the project
designing.
It's a task-oriented system for subdividing a project into product parts.
The product breakdown structure describes subtasks or work packages and represents the
connection between work packages. Within the product breakdown Structure, the project work has
diagrammatically pictured with various types of lists.
The product breakdown structure is just like the work breakdown structure (WBS).
Work Breakdown Structure
It is an important project deliverable that classifies the team's work into flexible segments. "Project
Management Body of Knowledge (PMBOK)" is a group of terminology that describes the work
breakdown structure as a "deliverable-oriented hierarchical breakdown of the work which is
performed by the project team."
There are two ways to generate a Work Breakdown Structure.
• The top-down and
 • The bottom-up approach.
In the top-down approach, the WBS is derived by crumbling the overall project into subprojects
or lower-level tasks.
The bottom-up approach is more alike to a brainstorming exercise where team members are
asked to make a list of low-level tasks which is required to complete the project.
Resource Histogram
• The resource histogram is precisely a bar chart used for displaying the amounts of time that
a resource is scheduled to be worked on over a prearranged and specific period.
• Resource histograms can also contain the related feature of resource availability, used for
comparison on purposes of contrast.
Critical Path Analysis
• Critical path analysis is a technique that is used to categorize the activities that are required
to complete a task, as well as classify the time that is needed to finish each activity and the
relationships between the activities.
• It is also called a critical path method.
• CPA helps in predicting whether a project will expire on time.

LECTURE 4c: Software Cost Estimation

For any new software project, it is necessary to know how much it will cost to develop and how
much development time will it take. These estimates are needed before development is initiated,
but how is this done? Several estimation procedures have been developed and are having the
following attributes in common.
1. Project scope must be established in advanced.
2. Software metrics are used as a support from which evaluation is made.
3. The project is broken into small PCs which are estimated individually.
To achieve true cost & schedule estimate, several option arise.
4. Delay estimation
5. Used symbol decomposition techniques to generate project cost and schedule estimates.
6. Acquire one or more automated estimation tools.
Uses of Cost Estimation
 1. During the planning stage, one needs to choose how many engineers are required for the
project and to develop a schedule.
2. In monitoring the project's progress, one needs to access whether the project is progressing
according to the procedure and takes corrective action, if necessary.

END