Software project management (SPM)

Lecture # 09
 List of Topics
• Software Effort Estimation
• Challenges of Outsourcing in Project Management
• Review and Evaluation
 Software Effort Estimation
• Software effort estimation is the process of predicting the amount of
resources (e.g., time, money, personnel) that will be required to
develop or maintain a software system.
• This estimation is typically done early in the software development
process, before detailed design and implementation.
• It is used to plan and budget for the project.
 Software Effort Estimation (Cont…)
• There are several techniques that can be used for effort estimation,
including:
• Expert judgment: This technique relies on the experience and
expertise of project team members or external experts to estimate
the effort required for a project.
• Analogous estimation: This technique uses the data from similar past
projects to estimate the effort required for a current project. The data
may include historical project data or data from industry benchmarks.
• Parametric estimation: This technique uses statistical models to
estimate the effort required for a project.
 Software Effort Estimation (Cont…)
• Three-point estimation: This technique uses three estimates for each
task: best-case, most likely and worst-case scenarios. The expected
value is then calculated by taking the average of these three
estimates.
• Function point analysis (FPA): This technique uses a measure of the
functionality provided by the software system to estimate the effort
required. The function points are calculated by counting the number
of inputs, outputs, inquiries, and files used by the system.
 Software Effort Estimation (Cont…)
• Regardless of the technique used, it is important to recognize that
software effort estimation is inherently uncertain and that the actual
effort required may differ from the estimate.
• To reduce the uncertainty, it is important to use multiple estimation
techniques and to involve a diverse set of stakeholders in the
estimation process.
• Additionally, it's important to track progress, and re-estimate as the
project progresses.
Challenges of Outsourcing in Project Management
• Outsourcing is a common strategy used by organizations to access
specialized skills, expertise, and resources that may not be available
in-house.
• However, outsourcing can also present a number of challenges for
project managers, including:
• Communication difficulties: Outsourcing often involves working with people
in different locations, time zones, and cultures, which can make
communication difficult. This can lead to misunderstandings, delays, and
other issues.
• Cultural differences: Outsourced workers may have different values, work
ethics, and communication styles, which can lead to misunderstandings and
conflicts.
Challenges of Outsourcing in Project Management
(Cont…)
• Lack of control: Outsourcing projects can lead to a loss of control for project
managers, as they may not have direct access to the outsourced team. This can
make it difficult to ensure that the project is on track and that the work is being
done to the desired quality.
• Quality control: Outsourcing can lead to quality control issues, as project
managers may not have the same level of oversight over the outsourced team
as they would have over an in-house team.
• Security concerns: Outsourcing can also present security concerns, as sensitive
information may be shared with third-party vendors.
• Dependence on single vendor: Relying too much on a single vendor can create
a risk of vendor lock-in, where the organization becomes dependent on that
vendor and is unable to switch to another vendor without incurring significant
costs.
Challenges of Outsourcing in Project Management
(Cont…)
• To mitigate these challenges;
• Project managers should develop clear communication plans.

• PM should establish regular check-ins.

• Build trust and rapport with the outsourced team.

• Should have a plan in place to manage risks.

• Additionally, it is important to have clear SLA's and contracts that define the
responsibilities, expectations and rights of both parties.
 Review and Evaluation
• Review and evaluation are two separate but related activities that are
often used in the context of project management and quality assurance.
• Review: It is the process of examining and evaluating a product, service,
or project to identify any issues or improvements that may be needed.
• Reviews can take many forms, such as code review, peer review, design
review, or requirements review.
• The goal of a review is to identify any errors, inconsistencies, or areas
for improvement before the product or service is released to customers.
 Review and Evaluation (Cont…)
• Evaluation:
It is the process of assessing the effectiveness, value or quality of a
product, service or project.
• Evaluation can take place at any stage of the project or product
lifecycle and can be done through various methods, such as surveys,
interviews, testing, or metrics.
• The goal of evaluation is to determine if the project or product is
meeting its goals and objectives, and to identify any areas that may
need to be improved.
 Review and Evaluation (Cont…)
• In summary, review is a process of identifying issues and
improvements, while evaluation is a process of assessing the
effectiveness, value or quality of something.
• Both are important in ensuring that projects and products are of high
quality and meet their intended goals and objectives.
THANKS