SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Module-04

Introduction to Project Management

Introduction

1. Comparison of Software and Other Projects:

 Evaluates whether software project management differs significantly from
managing other types of projects.

2. Key Ideas in Software Project Management:

 Focuses on planning, monitoring, and controlling software projects.

3. Objective of All Projects:

 All projects, including software projects, aim to meet specific objectives and
satisfy real needs.

4. Stakeholders and Objectives:

 Identifying the project's stakeholders and their objectives is crucial.

 Ensuring that these objectives are met is the primary aim of project management.

5. Assessing the Project's Progress:

 Knowing the current state of the project is essential to predict whether it will meet
its objectives in the future.

Project and Importance of Project Management

Definition of a Project:

 A project is a planned activity, according to dictionary definitions.

P a g e 1 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Planning Emphasis:

 Planning involves determining how to carry out a task before starting.

 Essential for careful consideration even with uncertain or exploratory projects,
where plans should be seen as provisional.

Routine vs. Non-Routine Activities:

 Routine maintenance tasks are often well-known and documented, making

detailed planning unnecessary.
 Documentation ensures consistency and aids newcomers.

Optimal Use of Conventional Project Management:

 Most beneficial for activities that fall between routine and highly uncertain
exploratory projects.

Boundary between Routine and Non-Routine:

 There is a hazy boundary where the first instance of a routine task can resemble a
project.
 Conversely, developing a system similar to previous ones can have significant
routine elements.

P a g e 2 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Importance of Project Management:

 Technical students might resist studying project management as it diverts them

from coding.

Financial Stakes:

 Significant amounts of money are involved in ICT projects.

 Example: In the UK during 2002-2003, the central government spent more on ICT
projects (£2.3 billion) than on road contracts (£1.4 billion).
 The Department for Work and Pensions alone spent over £800 million on ICT.

Consequences of Mismanagement:

 Poor management of ICT projects can lead to reduced funding for essential
services like hospitals.

Project Success Rates:

 A 2003 report by the Standish Group in the US analysed 13,522 projects:

o Only a third were successful.
o 82% were late.
o 43% exceeded their budget.

Causes of Project Failures:

 Mismanagement is often the root cause.

 The National Audit Office in the UK highlighted a 'lack of skills and a proven
approach to project management and risk management' as factors contributing to
project failures.

P a g e 3 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

The following characteristics distinguish projects:

 non-routine tasks are involved;
 planning is required;
 specific objectives are to be met or a specified product is to be created;
 the project has a predetermined time span;
 work is carried out for someone other than yourself;
 work involves several specialisms;
 people are formed into a temporary work group to carry out the task;
 work is carried out in several phases;
 the resources that are available for use on the project are constrained;
 The project is large or complex.

Project Size and Difficulty:

 Larger projects (e.g., 20 developers) are disproportionately more difficult than

smaller ones (e.g., 10 developers) due to increased coordination needs.
 Examples and exercises in the book focus on smaller projects for ease of
understanding, but the discussed techniques are relevant to larger projects as well.

Nature of Projects as Temporary Sub-organizations:

 Projects are temporary sub-organizations formed to carry out specific tasks.

 This setup can disrupt existing organizational authority but allows specialists to
focus on a single important task.

Advantages and Disadvantages:

 Advantage: A specialized group can concentrate on a specific task.

 Disadvantage: Projects can be seen as disruptive by others within the
organization.

P a g e 4 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

 Disadvantage: Expertise gained during the project may be lost when the team
disbands at the project's end.

Software Projects versus Other Types of Project

General Project Management Techniques:

 Many general project management techniques are applicable to software project

management.
 Fred Brooks identified unique characteristics of software projects that add
difficulty.

Characteristics of Software Projects:

 Invisibility:
o Unlike physical artifacts (e.g., bridges), software progress is not
immediately visible.
o Software project management involves making the invisible progress
visible.
 Complexity:
o Software products are more complex per dollar/pound/euro spent compared
to other engineered artifacts.
 Conformity:
o Traditional engineers work with consistent physical laws (e.g., cement and
steel).
o Software developers must conform to the inconsistent requirements of
human clients and organizations.
o Organizations can exhibit "organizational stupidity" due to lapses in
memory, communication, or decision-making.
 Flexibility:
o Software's ease of change is a strength but also a challenge.

P a g e 5 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

o Software is expected to adapt to changes in physical or organizational

systems, making it particularly subject to change.

Contract Management

In-House Projects:

 Users and developers work for the same organization.

Outsourced Projects:

 Organizations increasingly contract out ICT development to external developers.

 The client organization appoints a project manager to supervise the contract.
 This project manager delegates many technical decisions to the contractors and
focuses on budget and timeline.

Roles and Responsibilities:

 Client-side project managers prioritize overall project budget and schedule.

 Supplier-side project managers handle technical issues.

Focus of the Book:

 The book primarily addresses the concerns of technical project managers on the
supplier side.

Activities Covered by Software Project Management

1. Scope of Software Projects:

o Software projects involve more than just writing software.
o Even when using "off the shelf" software, the project remains a software project
due to the presence of other software-related activities.
2. Successive Processes:
o There are typically three successive processes that bring a new system into being
(as depicted in Figure 1.2).

P a g e 6 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Would you like more details on what those three processes typically involve, or any specific
details about Figure 1.2 if you have it?

The feasibility study and subsequent phases of project development are critical steps in
determining whether a project is worth pursuing and ensuring its successful execution.
Here's a structured overview based on the information provided:

Feasibility Study

 Purpose: To assess whether a project has a valid business case and is worth
starting.
 Activities:
o Gather information about the requirements of the proposed application.
o Identify the aims of the stakeholders and determine the means to achieve
them.
o Estimate developmental and operational costs.
o Evaluate the value of the benefits of the new system.
o For large systems, the feasibility study itself could be a separate project
with its own plan.
o It could also be part of a strategic planning exercise examining a range of
potential software developments.
o Assess a program of development that includes multiple projects.

P a g e 7 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Planning

 Initiation: Begins if the feasibility study indicates that the project is viable.
 Approach:
o Create an outline plan for the entire project.
o Develop a detailed plan for the first stage.
o Planning for later stages is postponed until more detailed and accurate
information is available after the earlier stages are completed.

Project Execution

 Execution Phase: Involves design and implementation sub-phases.

 Challenges:
o New project planners often find the boundary between design and planning
to be hazy.
o Design involves making decisions about the form of the products to be
created, such as the user interface and internal architecture.
o The plan details the activities to create these products, which can be
influenced by design decisions.
o Detailed planning and design are interconnected, as design decisions can
determine planning activities.

Sequence of Software Development Activities (ISO 12207)

 Standard: ISO 12207 provides a recommended sequence of software

development activities.
 Scope:
o Some activities are concerned with the system as a whole.
o Others are specific to software development.
o Software development may be only one part of a broader project, which
could also include:

P a g e 8 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

 Installation of ICT infrastructure.

 Design of user jobs.
 User training.

Understanding and properly executing these phases are essential for the successful
development and implementation of a project, ensuring that it meets stakeholder needs
and achieves its intended benefits.

Requirements Analysis

Start:

 Begins with requirements elicitation or requirements gathering.

Purpose:

 Establish what potential users and their managers require of the new system.

Types of Requirements:

1. Functional Requirements:
o What the system should do.
o Example: Dispatching an ambulance in response to an emergency call.
2. Quality Requirements:
o How well the functions must work.
o Example: Transaction time affected by hardware, software performance,
and human operation speed.

System Requirements:

 Training operators to use the system efficiently.

 Resource requirements related to application development costs.

P a g e 9 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Architecture Design

Purpose:

 Identify components of the new system that fulfill each requirement.

P a g e 10 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Components:

 Could be existing or new.

 May include software, hardware, or work processes.

Considerations:

 Integration with existing legacy systems.

 System architecture design influences software requirements.
 A second architecture design process maps software requirements to software
components.

Detailed Design

Purpose:

 Each software component consists of multiple software units.

Process:

 Detailed design of these units.

 Code and test each unit separately.
 Initial testing to debug individual software units.

Integration

Purpose:

 Test components together to meet overall requirements.

Process:

 Combine different software components.

 Test software with hardware platforms and user interactions.

P a g e 11 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Qualification Testing

Purpose:

 Ensure all requirements have been fulfilled.

Process:

 Thorough testing of the entire system, including software components.

Installation

Purpose:

 Make the new system operational.

Activities:

 Set up standing data (e.g., employee details in a payroll system).

 Configure system parameters.
 Install software onto hardware platforms.
 Provide user training.

Acceptance Support

Purpose:

 Resolve problems with the newly installed system.

Activities:

 Correct errors.
 Implement agreed extensions and improvements.
 Software maintenance as a series of minor software projects.

P a g e 12 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

 Most software development in many environments is maintenance.

Plans, Methods and Methodologies

Planning an Activity

Foundation:

 A plan for an activity is based on a method of work.

Example - Testing Software:

1. Analyze the requirements for the software.

2. Devise and write test cases to check that each requirement is satisfied.
3. Create test scripts and expected results for each test case.
4. Compare the actual results with the expected results and identify
discrepancies.

Method vs. Plan:

 Method:
o Relates to a type of activity in general.
o Provides a systematic approach, e.g., steps to test software.
 Plan:
o Converts methods into real activities.
o Identifies details for each activity:
 Start and end dates.
 Responsible personnel.
 Tools and materials needed, including information.

P a g e 13 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Interrelationship:

 The output from one method might be the input to another.

 Methods and techniques are often grouped into methodologies (e.g., object-
oriented design).

Some Ways of Categorizing Software Projects

Purpose:

 Identify project characteristics that affect planning and management.

Categories

1. Compulsory vs. Voluntary Users

o Compulsory Users:
 Users must use the system to perform tasks (e.g., recording a sale).
 Easier to elicit precise requirements from users.
o Voluntary Users:
 Users choose to use the system (e.g., computer games).
 Difficult to elicit precise requirements.
 Relies on developers' ingenuity, market surveys, focus groups, and
prototype evaluation.
2. Information Systems vs. Embedded Systems
o Information Systems:
 Enable staff to carry out office processes.
 Example: Stock control system.
o Embedded Systems:
 Control machines.
 Example: Air conditioning control in a building.
o Hybrid Systems:

P a g e 14 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

 Combine elements of both information and embedded systems.

 Example: Stock control system that also controls an automated
warehouse.

Software Products verses services

All types of software projects can broadly be classified into software product development
projects and software services projects. It can be further classified as shown in below Fig.1.7
A software product development concerns developing the software by keeping the
requirements to the general customers in mind and developed software is usually sold-off-the
shelf to a large number of customers. Examples of generic software development are
Microsoft’s Windows operating system and Oracle Corporatism’s Oracle 8i database
management software. Domain-specific software targets specific segments of
customers(verticals) Example BANCS from TCS. FINACLE from Infosys.

Fig: 1.7 A Classification of software projects

Software services cover a large gamut of software projects such as customization, outsourcing, maintenance,
testing and consultancy.
Projects may be distinguished by whether their aim is to produce a product or to meet certain
objectives.
P a g e 15 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Outsourced Projects

1. Commercial Sense of Outsourcing: Companies may outsource parts of a project

if they lack expertise or find it cost-effective.
2. Project Characteristics: Outsourced projects are typically small and need to be
completed within a few months.
3. Management Challenges: Managing outsourced projects entails special
challenges due to their size and time constraints.
4. Indian Software Companies: Indian companies are renowned for executing
outsourced software projects and are beginning to focus on product development.
5. Revenue Impact: Generic software products provide long-term revenue, while
outsourced projects offer one-time revenue.

Objective-Driven Development

1. Project Distinctions: Projects can aim to produce a product or meet certain

objectives.
2. Client Responsibility: In product creation, the client justifies the product.
3. Objective-Driven Projects: These projects identify solutions to problems, leading
to product recommendations.
4. Two-Stage Projects: Initial objective-driven stage leads to recommendations,
followed by product creation if needed.
5. Technical Work by External Group: Useful when user needs are unclear,
allowing for a preliminary design and subsequent implementation based on agreed
requirements.

P a g e 16 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Stakeholders

Definition: People who have a stake or interest in the project.

Early Identification: Important for setting up adequate communication channels.

Categories of Stakeholders:

o Internal to the Project Team: Under direct managerial control of the project
leader.
o External to the Project Team but within the Same Organization: For
example, users assisting with system testing; requires negotiated commitment.
o External to Both the Project Team and the Organization: Includes
customers or users benefiting from the system and contractors working on the
project; relationships based on contracts.

Diverse Objectives: Different stakeholders have different objectives that need to be

recognized and reconciled by the project leader (e.g., ease of use for end-users vs. staff
savings for managers).

Theory W: Proposed by Boehm and Ross, where the project manager aims to create win-
win situations for all parties involved.

Overlooked Stakeholders: Important stakeholder groups can sometimes be missed,

especially in unfamiliar business contexts.

Communication Plan: Recommended practice to create a communication plan at the

start of a project to coordinate stakeholder efforts effectively.

P a g e 17 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Setting Objectives

1. Project Owners: Stakeholders who own the project control its financing and set the
objectives.
2. Objectives Definition: Objectives define what the project team must achieve for
project success and identify shared intentions among stakeholders.
3. Outcome Focused: Objectives focus on desired outcomes (post-conditions) rather
than specific tasks.
o Example: "The project will be a success if customers can order our products
online" vs. "to build an e-commerce website".
4. Multiple Routes to Success: There are often several ways to meet an objective,
which is advantageous.
5. Project Authority: When multiple stakeholders claim project ownership, a project
steering committee (or similar body) with overall authority is needed to set, monitor,
and modify objectives.
6. Project Manager's Role: The project manager runs the project daily and reports
regularly to the steering committee.

Sub-Objectives and Goals

1. Effective Objectives: Must be within the control of the individual or team

responsible.
o Example: A business objective might be to reduce staff costs, but a
software developer's sub-objective would be to keep development costs
within a budget.
2. Steps to Achieving Objectives: Sub-objectives or goals are steps toward
achieving the main objective.
o Informal statement example: "To reach objective X, the following must be
in place..."

P a g e 18 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

SMART Objectives

1. Specific: Objectives should be concrete and well-defined.

o Example: Instead of "to improve customer relations", use "to reduce customer
complaints".
2. Measurable: There should be measures of effectiveness to determine success.
o Example: "Did we install the new software by June 1?" (Yes/No question)
3. Achievable: The objective must be within the power of the individual or group to
achieve.
4. Relevant: The objective must be relevant to the true purpose of the project.
5. Time Constrained: There should be a defined point in time by which the objective
should be achieved.

Measures of Effectiveness

1. Purpose: Provide practical methods to check if an objective has been met.

2. Example: 'Mean time between failures' (MTBF) is used to measure reliability.
o This is a performance measurement that can only be taken once the system is
operational.
3. Predictive Measures: Used during the construction of the system to estimate future
performance.
o Example: A large number of errors found during code inspections might
indicate potential reliability problems later.

Business Case
Justification or Business Case

1. Purpose: Ensure that the effort and expense of the project are worthwhile in terms of
eventual benefits.
2. Cost-Benefit Analysis: Part of the project's feasibility study that itemizes and
quantifies costs and benefits.

P a g e 19 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

3. Impact of Completion Date: Sooner completion means sooner benefits.

4. Business Model: Explains how the new application can generate the claimed benefits.
o Example: A new web-based application allowing global customers to order
products online, increasing sales and profits.

Ensuring the Business Case

1. Control Development Costs: Ensure costs do not rise to a level that exceeds the
value of benefits.
2. Maintain System Features: Do not reduce features to a level where expected
benefits cannot be realized.
3. Adhere to Delivery Dates: Avoid delays that result in an unacceptable loss of
benefits.

Project Success and Failure

1. Ensuring Project Success: The project plan should aim to preserve the business case
for the project.
2. Problems in Projects: Every non-trivial project will have problems, and stakeholders
may have different views on success and failure.

Distinguishing Objectives

1. Project Objectives: Targets the project team is expected to achieve, typically

including:
o Delivering the agreed functionality
o Meeting the required level of quality
o Completing on time
o Staying within budget
2. Business Objectives: Ensure that the project's deliverables meet the business case
(i.e., the value of benefits exceeds the costs).

P a g e 20 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Project and Business Success

1. Project Success: A project can be deemed successful if it meets its project objectives.
2. Business Failure: Despite meeting project objectives, the application might not meet
the business case (e.g., a product doesn't sell, or a website isn't used).
3. Business Success: A project could be late and over budget, yet still be a business
success if the deliverables generate long-term benefits that outweigh the costs.

Reducing the Gap between Project and Business Concerns

1. Broader View: Incorporate business issues into project management (e.g., market
surveys, competitor analysis, focus groups, prototyping, and evaluation by potential
users).
2. Sequence of Projects: Recognize that projects are often part of a sequence, where
technical skills and expertise developed in earlier projects benefit later ones.

Long-Term Benefits

1. Technical Learning: Increases costs on early projects but provides long-term benefits
through quicker, cheaper, and more accurate deployment of learned technologies.
2. Reusable Assets: Additional software assets, such as reusable code, provide long-
term value.
3. Customer Relationships: Building trust with clients over multiple projects can lead
to repeat business, which is more cost-effective than acquiring new clients.

Outsourcing Considerations

1. Immediate Savings vs. Long-Term Benefits: Outsourcing can provide immediate

savings, but may result in the loss of long-term benefits of increased expertise and
customer relationships.

P a g e 21 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

2. Astute Management: Managers should assess areas of technical expertise beneficial

to develop in-house versus outsourcing.

Management and Management Control

What is Management?

Management in the context of software project management involves several key

activities:

1. Planning: Deciding what is to be done.

2. Organizing: Making arrangements.
3. Staffing: Selecting the right people for the job.
4. Directing: Giving instructions.
5. Monitoring: Checking on progress.
6. Controlling: Taking action to remedy hold-ups.
7. Innovating: Coming up with new solutions.
8. Representing: Liaising with clients, users, developers, suppliers, and other
stakeholders.

Focus of Project Managers

Project managers spend most of their time on three primary activities:

1. Project Planning: Creating an initial plan, estimating project attributes (cost,

duration, effort), and planning subsequent activities.
2. Monitoring: Continuously tracking the progress of the project.
3. Control: Ensuring that the project proceeds as planned and making necessary
adjustments to address any deviations.

P a g e 22 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Project Management Stages

Project management is carried out over three well-defined stages, regardless of the
methodology used:

1. Project Initiation:
o Initial Planning: Undertaken immediately after the feasibility study and
before starting requirements analysis and specification.
o Estimations: Estimating cost, duration, and effort.
o Scheduling: Developing schedules for manpower and resources based on
estimations.
o Staffing: Organizing staff and making staffing plans.
o Risk Management: Identifying, analyzing, and planning to mitigate risks.
o Miscellaneous Plans: Creating quality assurance plans, configuration
management plans, etc.
2. Project Execution:
o Monitoring: Tracking the progress of the project.
o Control: Taking corrective actions to ensure the project stays on track.
3. Project Closing:
o Completing all activities logically.
o Formally closing all contracts.

Iterative Planning and Adjustment

 As the project progresses, more data becomes available, leading to a better

understanding of project complexities and risks.
 Project parameters are re-estimated periodically, and plans are adjusted accordingly to
ensure more accurate future planning.
 This iterative process involves continuous feedback between monitoring, control, and
plan revision activities.

P a g e 23 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Importance of Initial Project Planning

 Initial project planning is crucial and occurs right after the feasibility study phase.
 Involves estimating project attributes such as cost, duration, and effort, which
influence subsequent project activities.
 Regular revision of initial plans as the project progresses ensures alignment with the
project's evolving requirements and constraints.

By focusing on planning, monitoring, and control, project managers aim to guide projects
to successful completion while adapting to changes and resolving issues as they arise.

Project Planning Responsibilities of the Project Manager

Project planning is a critical responsibility of the project manager, involving several well-
defined activities.

These activities include estimation, scheduling, staffing, risk management, and creating
miscellaneous plans.

Estimation
The project manager estimates the following project attributes:

1. Cost: Determining the total cost to complete the project.

P a g e 24 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

2. Duration: Estimating the time required to complete the project.

3. Effort: Assessing the amount of effort necessary to complete the project.

The accuracy of these estimations significantly impacts the effectiveness of subsequent

activities such as scheduling and staffing.

Scheduling

 Based on the estimations of effort and duration, schedules for manpower and other
resources are developed.

Staffing

 Organizing the project team and creating staffing plans.

Risk Management

 Includes risk identification, analysis, and planning to mitigate risks.

Miscellaneous Plans

 Creating additional plans such as quality assurance plans and configuration

management plans.

Project Monitoring and Control

After the initiation of development activities, project monitoring and control activities are
undertaken to ensure the project proceeds as planned. These activities involve:

 Monitoring: Tracking the progress of the project.

 Control: Taking corrective actions to address deviations from the plan.

P a g e 25 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Iterative Planning and Adjustment

 As the project progresses, the project manager gains more detailed knowledge
about the project, allowing for more accurate planning.
 The project parameters are periodically re-estimated, incorporating new
information and changes in project conditions.
 This iterative process involves continuous feedback between monitoring, control,
and plan revision activities, allowing the project manager to adjust subsequent
activities with increasing confidence.

Methodologies and Best Practices

 The Step Wise method, based on the PRINCE2 (Projects IN Controlled

Environments) method, is extensively used in the UK and Europe.
 In the USA, the Project Management Institute’s PMBOK (Project Management
Body of Knowledge) offers similar best practices for software project
management.

By focusing on these activities and following established methodologies, project

managers can effectively plan, monitor, and control software development projects,
ensuring that they meet their objectives within the constraints of cost, time, and effort.

Management Control

Management control involves setting objectives for a system and monitoring its
performance. This process transforms raw data into useful information to guide decision-
making. Here's a breakdown:

1. Setting Objectives:
o Establish clear goals for the system or project.
2. Monitoring Performance:

P a g e 26 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

o Continuously track the performance of the system against the set

objectives.
o Use local managers for data collection to ensure accurate and up-to-date
information.
3. Data Collection:
o Collect raw data from various sources within the system.
o Example: "Location X has processed 2000 documents."
4. Data Processing:
o Transform raw data into meaningful information.
o This involves calculating metrics that are useful for higher management
decision-making.
5. Transforming Data into Information:
o Calculate percentages: e.g., "Percentage of records processed."
o Determine averages: e.g., "Average documents processed per day per
person."
o Estimate timelines: e.g., "Estimated completion date."

By following these steps, management can effectively control the system, ensuring it
meets its objectives and identifying areas that require attention or improvement.

P a g e 27 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Dynamic Project Management

In project management, especially in complex endeavors, continual monitoring and

adjustment are crucial for success. Here’s how it works:

1. Monitoring Performance Against Objectives:

o Project managers compare actual performance metrics, like the estimated
completion date for data transfer in different branches, against established
targets.
2. Identifying Issues and Making Decisions:
o If some branches are falling behind, decisions need to be made. For instance,
reallocating staff from one branch to another to meet deadlines.

P a g e 28 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

o Managers must assess the impact of decisions carefully. While one branch
might meet its deadline early, transferring staff could delay another branch.
3. Modeling Consequences:
o Various solutions are modeled to predict their impact before implementation.
This ensures informed decision-making and minimizes risks.
4. Implementing Solutions:
o Once a decision is made, it’s crucial to implement it effectively.
5. Continuous Review and Adjustment:
o Progress is continually monitored and data processed to assess the
effectiveness of implemented solutions.
o Adjustments are made as new information becomes available or circumstances
change.
6. Dynamic Nature of Project Planning:
o Project plans are not static documents but evolve throughout the project
lifecycle.
o While extensive planning is essential, successful project execution depends on
adaptive management and intelligent decision-making.

By maintaining flexibility and responsiveness, project managers can navigate challenges

effectively and enhance the likelihood of project success despite unforeseen obstacles.

P a g e 29 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Software development and Project Management Life Cycle

Software development life cycle denotes (SDLC) the stages through which a software is developed. In
contrast to SDLC, the project management life cycle typically starts well before the software
development activities start and continues for the entire duration of SDLC. (Fig 1.7)
In Project Management process, the project manager carries out project initiation, planning,
execution, monitoring, controlling and closing.

The different phases of the project management life cycle are shown in Fig: 1.8

P a g e 30 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Project Management Life Cycle

Project Initiation: The project initiation phase starts with project concept development. During
concept development the different characteristics of the software to be developed are thoroughly
understood, which includes, the scope of the project, the project constraints, the cost that would be
incurred and the benefits that would accrue. Based on this understanding, a feasibility study is
undertaken to determine the project would be financially and technically feasible.
Based on feasibility study, the business case is developed. Once the top management agrees to the
business case, the project manager is appointed, the project charter is written and finally project
team is formed. This sets the ground for the manager to start the project planning phase.

W5HH Principle: Barry Boehm, summarized the questions that need to be asked and answered in
order to have an understanding of these project characteristics.

 Why is the software being built?

What will be done?
When will it be done?
Who is responsible for a function?

Where are they organizationally located?
How will the job be done technically and managerially?
How much of these each resource is needed.

Project Bidding: Once the top management is convinced by the business case, the project charter is
developed. For some categories of projects, it may be necessary to have formal bidding process to select
suitable vendor based on some cost-performance criteria. The different types of bidding techniques are:

Request for quotation(RFQ) : An organization advertises an RFQ if it has good understanding of the
project and the possible solutions.

Request for Proposal(RFP) : An organization had reasonable understanding of the problem to be solved,
however, it does not have good grasp of the solution aspects. i.e. may not have sufficient knowledge about
different features to be implemented. The purpose of RFP is to get an understanding of the alternative
solutions possible that can be deployed and not vendor selection. Based on the RFP process, the requesting
organization can form a clear idea of the project solutions required, based on which it can form a statement
work (SOW) for requesting RFQ for the vendors.

P a g e 31 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT
Request for Information (RFI): An organization soliciting bids may publish an RFI. Based on the vendor
response to the RFI, the organization can assess the competencies of the vendors and shortlist the vendors
who can bid for the work

3. Project Planning: An importance of the project initiation phase is the project charter. During the project
planning the project manger carries out several processes and creates the following documents:
Project plan: This document identifies the project the project tasks and a schedule for the project tasks
that assigns project resources and time frames to the tasks.
Resource Plan: It lists the resources , manpower and equipment that would be required to execute the
project.
Functional Plan: It documents the plan for manpower, equipment and other costs.
Quality Plan: Plan of quality targets and control plans are included in this document.
Risk Plan: This document lists the identification of the potential risks, their prioritization and a plan for the
actions that would be taken to contain the different risks.

4. Project Execution: In this phase the tasks are executed as per the project plan developed during the
planning phase. Quality of the deliverables is ensured through execution of proper processes. Once all the
deliverables are produced and accepted by the customer, the project execution phase completes and the
project closure phase starts.

5. Project Closure: Project closure involves completing the release of all the required deliverables to the
customer along with the necessary documentation. All the Project resources are released and supply
agreements with the vendors are terminated and all the pending payments are completed. Finally, a
postimplementation review is undertaken to analyze the project performance and to list the lessons for use in
future projects.

TRADITIONAL VERSUS MODERN MANAGEMENT PRACTICES

Over the last two decades, the basic approach taken by the software industry to develop software has
undergone a radical change.
Software is not developed from scratch any more, Software development projects are based on either
tailoring some existing product or reusing certain pre-built libraries both will maximize code reuse and
compression of project durations.
Other goals include facilitating and accommodating client feedback and client feedbacks and customer
participation in project development work and incremental delivery of the product with evolving
functionality.

P a g e 32 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Some Important difference between modern management practices and traditional practices are:

 Planning Incremental Delivery: Earlier, projects were simpler and therefore more predictable than
the present-day projects. In those days, projects were planned with sufficient detail much before the
actual project execution started. After the project initiation, monitoring and control activities were
carried out to ensure that the project execution proceeded as per plan, Now, the projects are required
to be completed over a much shorter duration, and rapid application development and deployment are
considered key strategies.Instead of making a long-term project completion plan, the project manger
now plans all incremental deliveries with evolving functionalities. This type of project management
is often called extreme project management. Extreme project management is highly flexible
approach that concentrates on human side of projectmanagement(e.g.managingprojectstakeholders).

 Quality Management: Customer awareness about product quality has increased significantly. The
key responsibility of a project manager now includes assessment of project progress and tracking the
quality of all intermediate artifacts.

 Change Management: Earlier, when the requirements were signed off by the customer, any changes
to the requirements were rarely entertained. Customer suggestions are now actively solicited and
incorporated throughout the development process. To facilitate customer feedback, incremental
delivery models are popularly being used. Product development is being carried out through a series
of product versions implementing increasingly greater functionalities. The Project manager plays a
key role in product base lining and version control. This has made change management a crucial
responsibility of the project manager. Change Management is also known as configuration
management.

 Requirement Management: In older development methodologies , the requirements had to be

identified upfront and these were ‘signed off’ by the customer and frozen before the development
could start. At present , in most projects, the requirements change frequently during the development
cycle. Requirement management has therefore become a systematic process of controlling changes,
documenting , analyzing, tracing, prioritizing requirements and then communicating the changes to
the relevant stakeholders.

 Release Management: Release management concerns planning, prioritizing and controlling the
different releases of a software. Modern development processes such as Agile development processes
advocate frequent and regular releases of the software to be made to the customer during the software
development. Starting with the release of basic or core functionalities of the software, more complete
functionalities are made available to the customer every couple of weeks . Hence effective Release
Management has become important.

 Risk Management: In modern software development practices. Effective risk management is

considered very important to the success of a project. A risk is any negative situation that may arise
as the project progresses and may threaten the success of the project. Risk Management involves
identification of risks, assessment of the impacts of various risks, prioritization of the risks and
preparation of risk-containment plans.

P a g e 33 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT
 Scope Management: Modern software development encourages customer to come up with change
requests. While accepting the requests, three critical project parameters: scope , schedule and project
cost are interdependent and related.

P a g e 34 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

P a g e 35 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

P a g e 36 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

P a g e 37 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

P a g e 38 | 39
SOFTWARE ENGINEERING & PROJECT MANAGEMENT

P a g e 39 | 39