UNIT-01:Project evaluation and project planning: Importance of Software Project

Management, Activities Methodologies, types of Software Projects, Setting objectives,

Management Principles, Management Control, Project portfolio Management, Cost-benefit
evaluation technology, Strategic program Management, Stepwise Project Planning.

Introduction:
Software Project Management (SPM) is a proper way of planning and leading software projects. It is a
part of project management in which software projects are planned, implemented, monitored, and
controlled.
Software Project Management (SPM) is all about planning, organizing, observing the software
development process, and controlling software projects to ensure successful delivery of software
products that meet client requirements, quality standards, time schedules, and budget constraints. It
involves tasks like planning, defining the project scope, calculating how much time and resources are
needed, scheduling tasks, allocating resources, and tracking progress.
Software project management is the process of overseeing and coordinating software development
projects. This includes everything from planning and budgeting to development and testing. In order to
be successful, software project managers must have a strong understanding of the software development
process and be able to communicate with all members of the development team effectively.
The ultimate goal is to deliver a high-quality software product that meets the needs and expectations of
the users.
A project is a temporary and unique endeavor undertaken to create a specific product, service, or
result within defined constraints such as time, cost, resources, and quality.
Attribute of a project:
Temporary: Projects have a clear beginning and an end. They are not ongoing processes or operations.
Unique Outcome: Each project delivers something distinct — a new software application, a new
building, etc.
Defined Objectives: Projects are initiated to fulfill specific goals aligned with business or organizational
strategy.
Progressive Elaboration: Project details become clearer as the project progresses and more information
is available.
Cross-functional: Projects often require coordination across multiple departments or specialties
Uncertainty & Risk: Projects often involve uncertainty and risks that must be managed proactively.
Key Reasons for Importance:
 Efficient resource utilization
 Improved risk management
 Quality assurance
 Stakeholder communication and satisfaction
 Predictability and control over software delivery
Software Project Management Activities:

1. Project Planning and Tracking – Defining scope, schedule, cost, quality, and risk plans.
The development process of a software project can be broadly divided into two distinct phases:
the planning phase and the execution phase. In the planning phase, all of the necessary tasks are
identified and scheduled. The development team then works on completing these tasks in the
execution phase.
 It is important to track the progress of analysis phases of programming in order to ensure that the
project is on track. Tracking allows managers to see where the project stands in progress and
identify potential issues. There are a variety of tools that can be used for tracking, such as Gantt
charts and project management software.
2. Project Monitoring & Control – Tracking progress and performance.
Performance Measurement: Tracking key performance indicators (KPIs) to assess project health.
Variance Analysis: Identifying deviations from the plan and investigating the reasons for those
variances.
Corrective Actions: Implementing necessary adjustments to get the project back on track.
3. Risk Management – Identifying and mitigating risks.
Risk management is the process of identifying and assessing risks that could potentially impact
the project. This includes things like schedule delays, cost overruns, and scope creep. There are
a variety of tools that can be used to help with risk management, such as risk registers and SWOT
analysis.
4. Resource Management – Allocating human and technical resources.
In order to successfully manage a software development project, it is important to have a clear
understanding of the required resources. This includes both human and material resources.
Human resources include the development team, as well as any other individuals who are
involved in the project.
Material resources include things like computers, software, and office supplies. It is important to
have a clear understanding of what resources are required to avoid any potential issues.
5. Stakeholder Management – Communication and expectation alignment.
Communication is a key part of project management. This includes things like sending updates
to stakeholders, as well as communicating changes to the development team. There are a variety
of tools that can be used to help with communication, such as project management software and
email. It is also important to have a clear understanding of all the software development stages in
order to communicate with stakeholders effectively.
6. Quality Management – Ensuring product meets required standards.
Quality Planning: Defining the quality standards and criteria for the software.
Quality Control: Implementing processes to ensure that the software meets the defined quality
standards through testing and other quality assurance activities.
Defect Management: Identifying, tracking, and resolving defects in the software.
7. Scope Management – One of the most important aspects of project management is scope
management. This is the process of ensuring that all of the work required to complete the project
is included in the scope. There are a variety of tools that can be used to help with scope
management, such as project templates and WBS (work breakdown structure) charts.
8. Estimation Management – Estimation is the process of determining how long a project will
take to complete and how much it will cost. This is an important part of project management, as
it allows managers to set realistic expectations for the project. A variety of tools can be used for
estimation, such as historical data and bottom-up analysis. It is also important to have a clear
understanding of the development process in order to make accurate estimates.
9. Scheduling Management – Scheduling is the process of creating a schedule for the project. This
includes things like identifying when each task will be completed and who will be responsible
for completing it. Scheduling is an important part of project management, as it allows managers
to ensure that the project is on track. There are a variety of tools that can be used for scheduling,
such as Gantt charts and project management software.
10. Configuration Management – Configuration management is the process of managing the
development team’s work. This includes things like keeping track of code changes and managing
development tools. Configuration management is an important part of project management, as it
allows managers to keep track of the project’s progress. A variety of tools can be used for
configuration management, such as version control software and development platforms. It is
also important to have a clear understanding of the development process in order to manage the
development team’s work effectively.
Types of Projects: In Software Project Management (SPM), projects can be categorized based on
various factors like size, purpose, development model, platform, and license. Understanding these
classifications helps in tailoring the management approach and selecting appropriate methodologies.
1. Based on Size:
Small-Scale Projects: Typically involve a single user or a small group, with limited complexity and
scope. Examples include personal websites, simple mobile apps, or small business tools.
Medium-Scale Projects: Involve a larger team and more complex features, requiring more planning and
coordination. Examples include medium-sized web applications, or specialized software for a specific
department.
Large-Scale Projects: Involve large teams, complex architectures, and high-risk, with significant
resources and long development cycles. Examples include enterprise resource planning (ERP) systems,
large e-commerce platforms, or complex mobile applications.
2. Based on Purpose:
System Software: Designed to manage and control the computer hardware and provide a platform for
other software to run. Examples include operating systems, device drivers, and utilities.
Application Software: Designed for specific user tasks and applications. Examples include word
processors, spreadsheets, games, and web browsers.
Web Applications: Software accessed and used through web browsers, often involving client-server
architectures.
Mobile Applications: Software designed for mobile devices like smartphones and tablets.
Embedded Software: Software embedded within hardware devices, controlling their functionality.
3. Based on Development Model:
Waterfall Model: A traditional, linear approach where development progresses through distinct phases
(requirements, design, implementation, testing, deployment).
Agile Model: An iterative and incremental approach that emphasizes flexibility, collaboration, and
continuous improvement. Commonly used frameworks include Scrum and Kanban.
Setting Objectives for Software Projects: Setting clear, well-defined objectives is critical for the
success of any software project. Objectives act as guiding principles, help align stakeholder expectations,
and provide a basis for planning, decision-making, and performance measurement.
Characteristics of Good Project Objectives:
SMART Element Description Example
S – Specific Clearly state what is to be achieved? "Develop an online food delivery
system."
M – Measurable Quantify progress or success. "Support 1,000 concurrent users."
A – Achievable Should be realistic given the resources. "Deliver MVP in 3 months with 5
developers."
R – Relevant Aligned with business goals and user "Reduce customer wait time by
needs. 20%."
T – Time-bound Include deadlines or timeframes. "Complete testing phase by Oct
15."

S – Specific: The objective must be clear and unambiguous.

It should answer what, why, and who is involved.
M – Measurable: You should be able to track progress and quantify results.
A – Achievable: The objective should be realistic, given the resources, time, and team skills.
R – Relevant: Objectives must be aligned with the overall project and business goals.
T – Time-Bound: Every objective should have a deadline or time frame.
It provides the foundation for successful planning, execution, and delivery. When objectives are
SMART, aligned with stakeholder expectations, and well-communicated, they become a powerful tool
for project control and success.
Management Principles:
In Software Project Management (SPM), "Management Principles" refer to the fundamental guidelines
and practices that guide the overall management of a software project, while "Management Control"
focuses on monitoring and regulating project execution to ensure alignment with plans and objectives.
Software project management involves a set of principles that guide the planning, execution, monitoring,
and completion of software projects. These principles help ensure that projects are completed
successfully, on time, and within budget. Here are some key management principles in software project
management:
1. Define Clear Objectives: Clearly define the project's objectives, scope, deliverables, and success
criteria. This helps in setting realistic expectations and measuring progress throughout the project
lifecycle.
2. Effective Communication: Communication is key in any project. Ensure that all stakeholders are
kept informed of project progress, changes, and risks. Use various communication channels such
as meetings, emails, and project management tools.
3. Risk Management: Identify potential risks early in the project and develop strategies to mitigate
them. Regularly review and update the risk management plan to address new risks that may arise
during the project.
4. Agile Methodologies: Agile methodologies, such as Scrum or Kanban, promote iterative and
incremental development. This allows for flexibility in responding to changing requirements and
ensures that the project stays on track.
5. Resource Management: Allocate resources effectively based on project requirements and
constraints. This includes human resources, budget, and equipment. Ensure that resources are
utilized efficiently throughout the project.
6. Quality Assurance: Implement quality assurance processes to ensure that the software meets the
specified requirements and standards. This includes testing, code reviews, and quality audits.
Management Control:
The process by which management ensures that organizational goals and plans are achieved efficiently
and effectively.
Monitoring and control is one of the key processes in any project management which has great
significance in making sure that business goals are achieved successfully. These processes enable the
ability to supervise, make informed decisions, and adjust in response to changes during the project life
cycle are critical.
Monitoring in project management is the systematic process of observing, measuring, and evaluating
activities, resources, and progress to verify that a given asset has been developed according to the terms
set out. It is intended to deliver instant insights, detect deviations from the plan, and allow quick decision-
making.
Objectives of Management Control:
 Ensure resources are used efficiently.
 Achieve organizational goals.
 Identify deviations from plans.
 Take corrective actions.
Steps in Management Control Process:
Establish Standards: Set performance benchmarks.
Measure Performance: Collect data on actual performance.
Compare Performance Against Standards: Identify variances.
Analyse Deviations: Understand reasons for deviations.
Take Corrective Action: Adjust activities or standards as needed.
Feedback: Information from control process used to improve future plans.
Project Portfolio Management (PPM): Project portfolio management (PPM) is the centralized
management of the processes, methods, and technologies used by project managers and project
management offices (PMOs) to analyse and collectively manage current or proposed projects based on
numerous key characteristics.
A project portfolio is a collection of all the projects a company is doing. It's like having a list of different
tasks or jobs that need to be done. Each project in the portfolio is like a piece of the bigger picture,
helping the company reach its goals. Just like a mix of different investments in a portfolio, there are
different projects in a project portfolio, each at various stages. These projects can be anything from
making new products to improving how things work or promoting products. The goal is to have a
balanced portfolio with different kinds of projects, each important in its way. By managing the portfolio
well, a company can make sure it's spending its time and money wisely and moving closer to its big
goals.
Project Portfolio Management vs Project Management
PPM PM
Focus Project Portfolio Management looks at Project Management focuses on handling
all the projects together as a whole to one project at a time.
manage them.
Scope Project Portfolio Management considers Project Management deals with the specific
the overall picture of all projects in the details of each project.
portfolio.
Decision In Project Portfolio Management, In Project Management, decisions are made
Making decisions are made about which projects about how to carry out and finish a
to prioritize based on strategic goals. particular project.

Resource Project Portfolio Management allocates Project Management allocates resources

Allocation resources like money and people across within a single project to meet its specific
all projects to meet overall objectives. needs.
Risk Project Portfolio Management handles Project Management manages risks within
Management risks across all projects, considering how the context of one project.
they affect the whole portfolio.
Performance Project Portfolio Management keeps Project Management monitors the
Monitoring track of the overall performance and performance and progress of each project.
progress of all projects in the portfolio.

Project Portfolio Management Process:

Project Portfolio Management (PPM) is all about managing a bunch of different projects in a structured
way.
1. Define Business Objectives: This step involves understanding the strategic goals and objectives of
the organization. It includes identifying key performance indicators (KPIs), market trends, competitive
landscape, and stakeholder expectations. The aim is to align project initiatives with the overarching
business strategy to ensure that every project contributes to the organization's success.
Example: If the business objective is to increase market share, PPM would prioritize projects that focus
on product development, marketing campaigns, or market expansion strategies.
2. Collect Project Ideas for Your Portfolio: In this phase, project ideas are gathered from various
sources such as stakeholders, employees, customers, market research, and industry trends. Idea
generation techniques like brainstorming sessions, surveys, and feedback mechanisms are used to
capture a diverse range of project proposals. Each project idea is evaluated based on its potential to
contribute to the business objectives, feasibility, resource requirements, risks, and expected benefits.
Example: Project ideas may include launching a new product line, improving customer service
processes, implementing a digital transformation initiative, or expanding into new markets.
3. Select the Best Project for Your Portfolio: Once project ideas are collected, they undergo a selection
process to determine which projects should be included in the portfolio. Criteria for project selection
may include strategic alignment, ROI potential, resource availability, risk assessment, market demand,
and technological feasibility. Projects that align closely with business objectives, offer high ROI, and fit
within resource constraints are prioritized for inclusion in the portfolio.
Example: A project to implement a customer relationship management (CRM) system may be selected
due to its potential to improve customer satisfaction, streamline processes, and increase sales efficiency.
4. Validate Project Portfolio Feasibility: Before finalizing the project portfolio, each selected project
undergoes a feasibility analysis to assess its technical, financial, and organizational viability. Technical
feasibility evaluates whether the project can be successfully implemented given the available technology
and expertise. Financial feasibility assesses the project's cost estimates, potential revenue or cost savings,
and ROI projections. Organizational feasibility considers factors such as alignment with organizational
culture, resource availability, skills gaps, and change management requirements.
Example: The CRM system project undergoes feasibility analysis to ensure it can be implemented within
budget, meets technical requirements, and aligns with the organization's capabilities.
5. Execute and Manage Your Project Portfolio: Once the project portfolio is finalized and approved,
the projects are executed according to their respective plans and timelines. Project portfolio management
involves monitoring and controlling each project's progress, managing resources, mitigating risks, and
ensuring alignment with business objectives. Regular performance evaluations, status reports, and
stakeholder communications are essential for effective portfolio management.
Example: The CRM system project is executed with regular progress updates, milestone reviews, and
feedback loops to ensure it meets expectations and delivers the intended benefits.

Strategic Program Management: Strategic Management is a comprehensive approach to planning,

executing, and controlling programs that align with an organisation's strategic objectives. It provides a
framework for managing multiple related projects in a coordinated manner, ensuring that resources are
effectively allocated, and goals are achieved. In this blog, we will delve into the fundamental concepts
of Strategic Program Management and how you can plan your programs strategically.
Strategic program management in software projects involves aligning project execution with the overall
business strategy to ensure that projects contribute to the organization's long-term goals. It's about more
than just completing individual projects; it's about managing a collection of related projects (a program)
to achieve specific strategic objectives and drive organizational value.
Strategic project management (SPM) defines how a project may benefit a company's efficiency and
strategic plan as a whole. It is the process of thinking about your projects in light of their connection to
your strategic plan.
It involves making clear goals, knowing what other companies are doing, understanding what your
company is good at, and putting plans into action. It’s about making smart choices and being ready to
change those choices if needed to help the company grow and flourish in the long term.
Strategic management process:
1. Goal-setting: First things first. Where do you want to go? Effective goal-setting involves
understanding what your organization stands for and what it wants to achieve. For this, you’ll need your
company mission, vision, and long-term objectives.
Begin by revisiting and deeply understanding your organization’s mission and vision. These are values
that encapsulate the essence of what your organization is and aspires to be.
Think about how your goals can reflect and advance these fundamental principles in the long term. These
values act as a guiding compass and should be evident in every goal you set. For example, if ‘innovation’
is a core value, your goals should reflect a commitment to new ideas.
2. SWOT Analysis:
Strengths: Internal factors that give the program a competitive advantage, such as skilled team members,
robust processes, or strong stakeholder relationships.
Weaknesses: Internal factors that hinder the program's progress or make it vulnerable, such as limited
resources, lack of expertise, or inefficient processes.
Opportunities: External factors that can be leveraged to enhance the program's success, such as new
technologies, market trends, or strategic partnerships.
Threats: External factors that could negatively impact the program, such as economic downturns,
increased competition, or changing regulations.
3. Strategy formulation: This could involve diversification, market penetration, product development,
partnerships, cost leadership, or differentiation strategies, among others. The secret is to generate
multiple options that align with the results of your SWOT diagram.
4. Strategy implementation: The implementation stage involves allocating resources, assigning tasks,
and making sure everyone in your organization knows what they’re supposed to be doing.
5. Evaluation and control: As you move along, you need to check you’re still on the right path. This
stage is about monitoring your progress, comparing it with your plan, and making adjustments like the
captain of a ship. Maybe you’ve hit some unexpected challenges, or maybe there are new opportunities
you hadn’t considered before. The more you check, the more you’ll know.
Stepwise Project Planning:
The framework of basic steps in project planning illustrates the various activities involved in the
development process.
 Selecting project
 Project scope & objectives
 Project infrastructure
 Analyse project characteristics
 Project products and activities
 Estimation effort
 Activity risks
 Allocate resources
 Review plan
 Execute plan

Step 0: Selecting Project

 This is the initial step which starts well outside the project planning process.
 Feasibility study of the project helps in choosing the appropriate one.
 Strategic planning process helps in evaluating the metrics of selecting the project.
 Different methodologies are inevitable, stemming directly from the questions of what constitutes
a methodology and what are a methodology's underlying principles.
Step 1: Project Scope and Objectives
 Every stakeholder involved in the project must agree on the objectives defined in determining
the success of the project.
 Scope statements may take many forms depending on the type of project being implemented and
the nature of the organization.
 The scope statement details the project deliverables and describes the major objectives.
 The objectives should include measurable success criteria for the project.
Step 2: Project Infrastructure
 Project Infrastructure refers to the organizational structure, processes, tools, techniques and
training an organisation puts in place to make projects more successful.
 Organisational Structure – Organisational structure including such support mechanisms as
project management office, project recruiting function, financial monitoring area etc. It also
covers lines of communication and escalation.
 Processes – Typically methodologies, checklists and guidelines
 Tools – Software and templates
 Techniques – Repeatable processes such as kick off meetings, PIRs, analysis techniques, etc.
Step 3: Analyse Project Characteristics
 The project is categorized as either product-driven or an objective-driven.
 A project has several characteristics:
o Projects are unique.
o Projects are temporary in nature and have a definite beginning and ending date.
o Projects are completed when the project goals are achieved or it’s determined the project
is no longer viable.
Step 4: Project Products and Activities
 Identify the project deliverables i.e. the end product that has to been given over to the client.
 Some products are identified as intermediate products during the creation of deliverables.
 Project products can be System products, module products or management products.
 Technical products include training materials and operating instructions in managing the quality
of the project.
Step 5: Estimating Effort
 The effort estimation for the staff required, the probable duration and the non- staff resources
needed for every activity is determined.
 These estimates depend on the type of the activity.
 Effort is the amount of work that has to be done.
 Software development efforts estimation is the process of predicting the most realistic use of
effort required to develop or maintain software based on incomplete, uncertain and/or noisy
input.
Step 6: Identify Activity Risks
 Activity based risks are identified for every activity based on number of assumptions.
 Risk planning reduces the impact of identified risks.
 To materialize the risk, contingency plans are specified.
 New activities can reduce risks to a certain extent when there is change in plans.
 Risks fall into three broad categories — controllable known, uncontrollable known and
unknown.
Step 7: Allocate Resources
 Resource allocation is used to assign the available resources in an economic way. It is part of
resource management. In project management, resource allocation is the scheduling of activities
and the resources required by those activities while taking into consideration both the resource
availability and the project time.
 Staff needed and available are identified for each activity and allocated their respective tasks.
Step 8: Review Plan
 When a task is completed it leads to the quality review. These quality checks have to be passed
before the activity is completely signed-off.
 Every plan has to be documented and all stakeholders must have agreed to all constraints and
understand the project.
Step 9: Execute Plan
 Finally, the execution of the project is drawn with each specified activity as it is approached.
 Detailed planning of later stages is necessary because more information will be available than
the start stage.
 Project planning and execution becomes an iterative process where as each activity which is to
be carried out approaches, they should be reviewed in detail.

Cost-benefit evaluation technology: Cost-benefit evaluation techniques in software project

management help determine the economic viability of a project by comparing its anticipated costs with
its expected benefits. These techniques aid in making informed decisions about whether to proceed with
a project, select the most beneficial among several options, and assess the overall value of an investment.
1. Net Present Value (NPV): NPV calculates the present value of expected cash inflows and outflows
associated with a project, taking into account the time value of money. If the NPV is positive, the project
is considered financially viable.
2. Return on Investment (ROI): ROI measures the profitability of an investment by comparing the net
profit or benefit with the cost of the investment. It is expressed as a percentage, with a higher ROI
indicating a better return on the investment.
3. Cost-Benefit Analysis (CBA): CBA compares the total costs of a project with its total benefits, both
in monetary and non-monetary terms. The goal is to quantify the benefits and costs and determine
whether the benefits outweigh the costs.
A cost-benefit analysis (CBA) is still one of the most practical tools for making smart, data-backed
decisions, from launching new products to deciding if a policy is worth funding. Cost-benefit analysis
(CBA) is a decision-making framework that helps you evaluate whether the benefits of a project,
initiative, or investment outweigh the estimated costs. It’s a simple concept at its core: List out all the
potential gains and losses, assign values to them, and compare the two.
A cost-benefit analysis in project management is a practical way to weigh the value of a project against
what it’ll take to make it happen. It helps teams and decision makers look at the numbers, compare the
costs to the expected benefits, and decide if a project is worth the investment. In project management,
it’s a go-to method for making confident, data-backed choices that support business goals.
Key components of a cost-benefit analysis: A cost-benefit analysis works best when all key
components are clearly outlined beforehand. This gives a complete view of a project’s impact, helps
guide data-backed decisions, and varies depending on the type of project.
Key components are Identifying and quantifying costs and benefits, assigning monetary values, and
analysing the net present value (NPV) or benefit-cost ratio to make informed decisions.
Types of project costs:
 Direct vs. indirect costs: Direct costs are expenses that are directly tied to a specific project and
are easy to track, such as materials and labor. Indirect costs contribute to the project, but are not
directly related (e.g., legal services or general office supplies).
 Fixed vs. variable costs: Fixed costs stay the same no matter the project size (e.g., property
taxes, equipment purchases), while variable costs change depending on scale, like commissions
or raw material usage.
 Tangible vs. intangible costs: Tangible costs are easy to measure and have a numerical value
you can quantify, such as salaries or rent. Intangible costs, like damaged reputation or slower
team momentum, are harder to assign a monetary value.
 Opportunity costs: These are the benefits or opportunities foregone when a business chooses
one project or opportunity over others. To quantify opportunity costs, you must weigh the
potential benefits of the available alternatives.
 Future costs: These are the costs anticipated to come up later in the project (e.g., future training
or hiring more employees). Planning for these in advance helps prevent budget surprises and
keeps long-term goals on track.
4. Payback Period: The payback period calculates the time it takes to recover the initial investment
through expected cash flows. A shorter payback period is generally preferred as it indicates a quicker
return on investment.
5. Cost-Effectiveness Analysis (CEA): CEA evaluates the relative costs and outcomes of different
alternatives or interventions. It helps in determining the most efficient option in achieving a specific
objective, regardless of monetary values.
6. Break-Even Analysis: Break-even analysis determines the point at which total costs equal total
revenues, resulting in zero profit or loss. It helps in understanding the minimum level of sales or output
needed to cover costs.