Printed Page 1 of 2 Sub Code: KOE-068

Paper Id: Roll No.

B.TECH
(SEM VI) THEORY EXAMINATION 2021-22
SOFTWARE PROJECT MANAGEMENT

Time: 3 Hours Total Marks: 100

Note: Attempt all Sections. If you require any missing data, then choose suitably.

SECTION A

1. Attempt all questions in brief. 2*10 = 20

Q.no Questions Marks CO
(a) Define Software Project Management. 2 1

Solution: Software project management is an 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 fulfils requirements.

In software Project Management, the client and the developers need to

know the length, period and cost of the project.
(b) Briefly discuss about the Project Evaluation. 2 1

Solution: Project evaluation is a systematic and objective assessment

of an ongoing or completed project.

The aim is to determine the relevance and level of achievement of

project objectives, development effectiveness, efficiency, impact and
sustainability. Evaluation is research to inform decisions—an
opportunity to push for adaptations and mid-course corrections that
will maximize success. Evaluation results benefit the immediate
project as well as enhance future initiatives with lessons learned.

(c) Define Project Life Cycle. 2 2

Solution: The project life cycle includes the steps required for project
managers to successfully manage a project from start to finish. There
are 5 phases to the project life cycle (also called the 5 process
groups)—initiating, planning, executing, monitoring/controlling, and
closing. The Project Life Cycle consists of four main phases through
which the Project Manager and his team try to achieve the objectives
that the project itself sets.
(d) Discuss about the Effort Estimation. 2 2

Solution: Effort estimation is the process of forecasting how much

 effort is required to develop or maintain a software application. This
effort is traditionally measured in the hours worked by a person, or the
money needed to pay for this work. Effort estimation is the process of
forecasting how much effort is required to develop or maintain a
software application. This effort is traditionally measured in the hours
worked by a person, or the money needed to pay for this work.

(e) Briefly discuss about the need of Activity Planning. 2 3

Solution: The activity plan should provide a means of evaluating the

consequences of not meeting any of the activity target dates and
guidance as to how the plan might most effectively be modified to
bring the project back to target.

(f) What do you mean by Risk Management? 2 3

Solution: Risk management is the process of identifying, assessing and

controlling threats to an organization's capital and earnings. These
risks stem from a variety of sources including financial uncertainties,
legal liabilities, technology issues, strategic management errors,
accidents and natural disasters.

(g) What do you mean by Project Management and Control? 2 4

Solution: Project management focuses on keeping the entire project on

track, including people, processes, and deliverables, project controls
focus specifically on quality control in order to save time and money.
Project controls are a set of processes used to understand and influence
the amount of time or money spent on a project. Each project control
focuses on a distinct part of the project plan, like the schedule,
resources, or potential risks.

(h) Define Framework for Management. 2 4

Solution: A project management framework is a set of standard project

management processes, templates and tools that can be used to initiate,
plan, execute, control and close a project. A management framework
(like the Business Model Canvas or SWOT) is a combination of
interlinked items that support a particular approach to a specific
objective. Various management frameworks are widely used even
though their origins, adoption, and value remain vague.

(i) What do you understand by the Organizational behavior? 2 5

Solution: Organizational behavior is the academic study of how people

interact within groups and its principles are applied primarily in
attempts to make businesses operate more effectively. Organizational
behavior is a combination of responses to external and internal stimuli
by a person as an individual or as a part of a group. This is a brief
introductory tutorial that explains the methodologies applied in the
rapidly growing area of organizational behavior in an organization.

(j) Discuss about the need of Staffing in Software Projects. 2 5

 Solution: Project staffing is important in software scheduling
which defines the organization of different project teams used in
scheduling. It also includes the identification of the right person for
handling the project, assignment of required responsibilities to the
selected team. Staffing deals with the appoint personnel for the
position that is identified by the organizational structure. It involves:
Defining requirement for personnel. Recruiting (identifying,
interviewing, and selecting candidates)

SECTION B

2. Attempt any three of the following: 10*3 = 30

Q.no Questions M
(a) Explain in detail about the Best methods of staff selection Motivation. 1

Solution: Staff selection is a term that refers to one of the personnel activities. The
purpose of the selection is to choose for the position (job) and for the organization (co-
workers, organizational culture, etc.) probably the most suitable candidate. Staff
Deployment & Staffing. Human Resources Management. Employee selection methods are
criteria for choosing an optimal candidate for a particular job position. They involve
reviewing an individual's capabilities, education, experiences and personality to determine
if they can perform key tasks and align with a company's overall culture. There are several
categories of employee selection methods, including tests or examinations, interviews and
background research. Hiring teams often use them to identify top candidates from a larger
list and see how they approach different work situations.

List of employee selection methods: A recruiter chooses top candidates from resumes and
other application materials sent through online job boards and portals. They typically use
a set of guidelines that show attributes a company prefers top candidates to have,
including relevant work experiences, skill sets and past training.

Screening: A recruiter might use this method to identify candidates from a previously
curated shortlist. It typically involves sending these candidates a series of questions by
email that further assess their qualifications and professionalism.

Assignment test: This selection method involves administering a test prompt that
resembles a similar work assignment that a candidate might receive in a company.
Recruiters often send the prompt through email to candidates from a shortlist. It can
provide more information about a candidate's practical skills for a job position, including
how they manage their time to meet a deadline efficiently. For example, a hiring manager
may require a copywriter to submit a writing sample using a company's internal style
guide or require a software engineer to prepare some lines of code for the organization's
website.

(b) Write short notes on any two of the following: 1

(i) Software process and Process Models
(ii) Choice of Process models
(iii) Rapid Application development(RAD)

Solution:
(i) Software process and Process Models: Software is the set of instructions in the form of
 programs to govern the computer system and to process the hardware components. To
produce a software product the set of activities is used. This set is called a software
process. The four basic process activities of specification, development, validation, and
evolution are organized differently in different development processes. The term software
specifies to the set of computer programs, procedures and associated documents
(Flowcharts, manuals, etc.) that describe the program and how they are to be used. A
software process is the set of activities and associated outcome that produce a software
product. a software process model is the mechanism of dividing software development
work into distinct phases to improve design, product management, and project
management. It is also known as a software development life cycle. The software
engineering paradigm which is also referred to as a software process model or Software
Development Life Cycle (SDLC) model is the development strategy that encompasses the
process, methods and tools.

Types Of Software Process Models:

 -Waterfall Model. The Waterfall model represents a breakdown of software project

activities in a linear sequential phase.
 -Iterative Mode.
 -V Model.
 -Incremental Model.
 -Spiral Model.
 -Agile Model.

(ii) Choice of Process models: 'The word "process* is sometimes used to emphasize the
idea of a system in action. In order to achieve an outcome, the system will have to execute
one or more activities: this is its process. This idea can be applied to the development of
computer-based systems where a number of interrelated activities have to be undertaken
to create a linal product. These activities can be organized in different ways and we can
call these process models.

A major part of the planning will be the choosing of the development methods to be used
and the slotting of these into an overall process model.

The planner needs not only to select methods but also to specify how the method is to be
applied. With methods such as SSADM, there is a considerable degree of choice about
how it is to be applied: not all parts of SSADM are compulsory. Many student projects
have the rather basic failing that at the planning stage they claim that. Say. SSADM is to
be used: in the event, all that is produced are a few SSADM fragments such as a top level
data flow diagram and a preliminary logical data structure diagram. If this is all the
particular project requires, it should be stated at the outset.

Choice of Process Models

-The word process is sometimes used to emphasize the idea of a system in action. In order
to achieve an outcome, the system will have to execute one or more activities: this is its
process.
-This idea can be applied to the development of computer-based systems where a number
of interrelated activities have to be undertaken to create a local product. These activities
can be organized in different ways and we can call these process models.

-A major part of the planning will be the choosing of the development methods to be used
and the slotting of these into an overall process model.

-The planner needs not only to select methods but also to specify how the method is to be
applied. With methods such as SSADM, there is a considerable degree of choice about
how it is to be applied: not all parts of SSADM are compulsory. Many student projects
have the rather basic failing that at the planning stage they claim. say. SSADM is to be
used: in the event, all that is produced are a few SSADM fragments such as a top level
data flow diagram and a preliminary logical data structure diagram. If this is all the
particular project requires, it should be stated at the outset.

(iii) Rapid Application development (RAD): Rapid Application Development (RAD) is a

development model that prioritizes rapid prototyping and quick feedback over long drawn
out development and testing cycles. With rapid application development, developers can
make multiple iterations and updates to a software quickly without starting from scratch
each time.

The RAD (Rapid Application Development) model is based on prototyping and iterative
development with no specific planning involved. The process of writing the software itself
involves the planning required for developing the product.
Rapid Application Development focuses on gathering customer requirements through
workshops or focus groups, early testing of the prototypes by the customer using iterative
concept, reuse of the existing prototypes (components), continuous integration and rapid
delivery.
What is RAD?
Rapid application development is a software development methodology that uses minimal
planning in favor of rapid prototyping. A prototype is a working model that is functionally
equivalent to a component of the product.
In the RAD model, the functional modules are developed in parallel as prototypes and are
integrated to make the complete product for faster product delivery. Since there is no
detailed preplanning, it makes it easier to incorporate the changes within the development
process.
RAD projects follow iterative and incremental model and have small teams comprising of
developers, domain experts, customer representatives and other IT resources working
progressively on their component or prototype.
The most important aspect for this model to be successful is to make sure that the
prototypes developed are reusable.
 RAD Model Design
RAD model distributes the analysis, design, build and test phases into a series of short,
iterative development cycles.
Following are the various phases of the RAD Model −
Business Modelling
The business model for the product under development is designed in terms of flow of
information and the distribution of information between various business channels. A
complete business analysis is performed to find the vital information for business, how it
can be obtained, how and when is the information processed and what are the factors
driving successful flow of information.
Data Modelling
The information gathered in the Business Modelling phase is reviewed and analyzed to
form sets of data objects vital for the business. The attributes of all data sets is identified
and defined. The relation between these data objects are established and defined in detail
in relevance to the business model.
Process Modelling
The data object sets defined in the Data Modelling phase are converted to establish the
business information flow needed to achieve specific business objectives as per the
business model. The process model for any changes or enhancements to the data object
sets is defined in this phase. Process descriptions for adding, deleting, retrieving or
modifying a data object are given.
Application Generation
The actual system is built and coding is done by using automation tools to convert process
and data models into actual prototypes.
Testing and Turnover
The overall testing time is reduced in the RAD model as the prototypes are independently
tested during every iteration. However, the data flow and the interfaces between all the
components need to be thoroughly tested with complete test coverage. Since most of the
programming components have already been tested, it reduces the risk of any major
issues.

RAD Benefits:

 -Quicker delivery. We'll start with the easy one, since it's built into the name. ...
 Quicker adjustments.
 -Fewer errors.
 -Lower development cost.
 -Lower maintenance costs.
 -Faster release of versions.
 -Better adoption of new technologies.
 -More involvement from business.

RAD Model Representation:

(c) What do you mean by Project schedules? Mention the Objectives of Activity planning. 1

Solution: A project schedule indicates what needs to be done, which resources must be
utilized, and when the project is due. It's a timetable that outlines start and end dates and
milestones that must be met for the project to be completed on time. A project
management schedule is a calendar or timeline that project managers use to keep track of
tasks and deadlines. Managers schedule start and end dates for individual tasks within the
project timeline to make sure the entire project advances at an appropriate speed.

Project scheduling involves creating a document, these days usually a digital document,
that details the project timeline and the organizational resources required to complete each
task. The project schedule must be accessible to every team member.

Project schedule simply means a mechanism that is used to communicate and know about
that tasks are needed and has to be done or performed and which organizational resources
will be given or allocated to these tasks and in what time duration or time frame work is
needed to be performed. Effective project scheduling leads to success of project, reduced
cost, and increased customer satisfaction. Scheduling in project management means to list
out activities, deliverables, and milestones within a project that are delivered. It contains
more notes than your average weekly planner notes. The most common and important
form of project schedule is Gantt chart.
(d) Discuss about the concept and need of Cost monitoring Earned Value Analysis. 1

Solution: As earned value analysis provides better clarity and control on the activities
involved, it enables project managers to respond to issues early. As a part of EVM,
employees need to track their time and report their progress against the baseline.

Cost Control and Earned Value Management

Cost control includes monitoring cost, task completion, and time. If total cost of a project
at a given time is over the cost baseline, cost control measures may be necessary. Such
project management actions may range from ensuring that only tasks within the scope of
the work are being performed to alerting stakeholders of potential cost overruns. As a
project manager, it is important, professional, and ethical to identify and report on these
issues as soon as they are identified. Effective techniques exist to help you in this matter.

Earned Value Analysis (EVA) is a method that allows the project manager to measure the
amount of work actually performed on a project beyond the basic review of cost and
schedule reports. EVA provides a method that permits the project to be measured by
progress achieved.

Earned value management (EVM) is an effective technique for tracking costs and
examining project expenditures relative to completed work. Its strength is that it looks at
cost, time, and task completion within the scope of the project simultaneously. It uses a
WBS and budget created during the development stage, but tracks these metrics during
the implementation stage of a project life cycle.

Performing EVM on a project requires that the project Scope, Schedule, and Budget be
integrated into a time-phased Performance Measurement Baseline (PMB). The PMB is
maintained with strict change control to ensure the integration of scope, schedule, and
budget.

(e) Describe the activities and Importance of Software Project Management. 1

Solution: One significant benefit of project management software is that it improves

decision-making & overall project productivity. It becomes much easier to make informed
decisions in the shortest amount of time because all of the important details are in one
centralized place. Software development projects tend to be complex and multi-faceted.
To complete a project on time and in budget, software developers must engage in efficient
planning, organization and monitoring. Project management involves the use of various
policies, procedures and principles to plan implement and complete a project. To ensure a
satisfactory result, projects must begin with specified parameters designed to produce the
desired outcome. Every project that goes through the project management process follows
 a project life cycle that essentially guides the project from start to completion. Software
project management focuses on developing a product that will have a positive effect on an
organization. Without project management, a software development team may begin
working on a project without any clear vision or guidance, resulting in more frequent
errors and confusion.

Part of software project management involves making everyone involved aware of the
purpose of the project and what steps are required to meet the end goal. Learn more about
project management for software development and what it entails.

Benefits of the Agile Methodology for Software Development:

Agile software development is an umbrella term for a set of practices and methodologies
based on iterative development. Also referred to as simply Agile, this form of project
management for software development focuses on the clean delivery of each individual
part of the software rather than the software as a whole. By using Agile, software
development teams can reduce costs, lessen stress on development teams, and improve
turnaround times.

Printed Page 2 of 2 Sub Code: KOE-068

Paper Id: Roll No.

SECTION C
3. Attempt any one part of the following: 10*1 = 10
Q.no Questions Marks C
(a) What is the concept and need of Agile methods in Project Life Cycle? 10 2
Solution: The Agile software development life cycle is the structured series of
stages that a product goes through as it moves from beginning to end. It contains
six phases: concept, inception, iteration, release, maintenance, and retirement.

The Agile life cycle will vary slightly depending on the project management
methodology chosen by a team. For example, Scrum teams work in short time
periods known as sprints, which are similar to iterations. They also have clearly
defined roles, such as Scrum master. On the other hand, Kanban teams have more
of a continuous flow with no required roles. Another example is Extreme
Programming, where teams tend to work in shorter iterations and place an extra
focus on engineering practices.

However, the goal of all software development teams is the same: to deliver
working software to users on time.The six phases of the agile life cycle

As mentioned, the Agile software development life cycle consists of six phases.
Let’s examine each of these Agile phases in more detail.

1. Concept

First up is the concept phase. Here, a product owner will determine the scope of
their project. If there are numerous projects, they will prioritize the most
important ones. The product owner will discuss key requirements with a client
and prepare documentation to outline them, including what features will be
supported and the proposed end results. It is advisable to keep the requirements to
a minimum as they can be added to in later stages. In the concept stage, the
product owner will also estimate the time and cost of potential projects. This
detailed analysis will help them to decide whether or not a project is feasible
before commencing work.

2. Inception

Once the concept is outlined, it is time to build the software development team. A
product owner will check their colleagues’ availability and pick the best people
for the project while also providing them with the necessary tools and resources.
They can then start the design process. The team will create a mock-up of the user
interface and build the project architecture. The inception stage involves further
input from stakeholders to fully flesh out the requirements on a diagram and
determine the product functionality. Regular check-ins will help to ensure that all
requirements are built into the design process.

3. Iteration

Next up is the iteration phase, also referred to as construction. It tends to be the

longest phase as the bulk of the work is carried out here. The developers will
work with UX designers to combine all product requirements and customer
feedback, turning the design into code. The goal is to build the bare functionality
of the product by the end of the first iteration or sprint. Additional features and
tweaks can be added in later iterations. This stage is a cornerstone of Agile
software development, enabling developers to create working software quickly
and make improvements to satisfy the client.

4. Release: The product is almost ready for release. But first, the quality

assurance team needs to perform some tests to ensure the software is fully

functional. These Agile team members will test the system to ensure the code is

clean — if potential bugs or defects are detected, the developers will address them

swiftly. User training will also take place during this phase, which will require

more documentation. When all of this is complete, the product’s final iteration

can then be released into production.

5. Maintenance: The software will now be fully deployed and made available to

customers. This action moves it into the maintenance phase. During this phase,

the software development team will provide ongoing support to keep the system

running smoothly and resolve any new bugs. They will also be on hand to offer
 additional training to users and ensure they know how to use the product. Over

time, new iterations can take place to refresh the existing product with upgrades

and additional features.

6. Retirement: There are two reasons why a product will enter the retirement
phase: either it is being replaced with new software, or the system itself has
become obsolete or incompatible with the organization over time. The software
development team will first notify users that the software is being retired. If there
is a replacement, the users will be migrated to the new system. Finally, the
developers will carry out any remaining end-of-life activities and remove support
for the existing software.

(b) Explain about the Oldham Hackman job characteristic model under the Staffing in 10 5
Software Projects.

Solution: The job characteristics model, designed by Hackman and Oldham,

is based on the idea that the task itself is key to employee motivation.
Specifically, a boring and monotonous job stifles motivation to perform well,
whereas a challenging job enhances motivation. Hackman and Oldham's (1974)
job characteristics model suggested that five core job dimensions affect certain
personal and work related outcomes, including job satisfaction. The five core job
dimensions identified are autonomy, feedback, skill variety, task identity, and task
significance. The Job Characteristics Model is a theory that is based on the idea
that a task in itself is the key to the employee's motivation. In short, a boring and
monotonous job is disastrous to an employee's motivation whereas a challenging,
versatile job has a positive effect on motivation.

The Oldham Hackman job characteristic model

five components:

-Skill variety

-Task identity

-Task significance

-Autonomy

-Feedback
 Each one of these components can be adjusted to recalibrate a job, making it more
engaging for the employee.

How to apply the job characteristics model:

 -Delegate tasks to the lowest level that you can. One step you can follow to apply
the JCM in your workplace is to delegate tasks to the lowest level that you can.
 -Vary the tasks involved in a job.
 -Assign teamwork.
 -Complete performance evaluations.
 -Encourage employees to rotate jobs.

4. Attempt any one part of the following: 10 *1 = 10

Q.no Questions Marks CO
(a) Discuss in detail about the Categorization of Software Projects. 10 1

Solution: There are many different types of software development.

Often, the various kinds of developers work together to bring your
project to fruition. Some of them overlap and can be found in a single
professional, while others require a distinct skill set.

Categorizing Software Projects:

1. Compulsory vs. Voluntary systems (projects): Compulsory

systems are the systems which the staff of an organization has
to use if they want to do a task. Voluntary systems are the
systems which are voluntarily used by the users e.g. Computer
gaming, school project, etc.

2. Information Vs. Embedded systems (projects): Information

 systems are used by staff to carry out office processes and tasks
e.g. stock control system. Embedded systems are used to
control machines e.g. system controlling equipment in a
building.

3. Objective-based Vs. Product-based systems (projects): Project,

whose requirement is to meet certain objectives which could be
met in a number of ways, is objective-based project. Project
whose requirement is to create a product, the details of which
have been specified by the client, is product-based project.

(b) Discuss about the Forward Pass and Backward Pass techniques in 10 3
Activity Planning and Risk Management.

Solution: Forward pass is a technique to move forward through

network diagram to determining project duration and finding the
critical path or Free Float of the project. Whereas backward pass
represents moving backward to the end result to calculate late start or
to find if there is any slack in the activity. A forward pass in project
management is a technique used to move through a project network
diagram. The forward pass helps you understand the project duration
and calculate the early start and early finish values (meaning, the
earliest day each project task can begin and wrap up). The "forward
pass" refers to calculation process, values of the output layers from the
inputs data. It's traversing through all neurons from first to last layer.

Forward Pass:

1. Early Start = Maximum (or Highest) EF value from immediate

Predecessor(s)
2. Early Finish = ES + Duration.

A backward pass in the area of project management refers to the

calculation of late finish dates and late start dates for the portions of
schedule activities that have not been completed. This is determined by
starting at the project's scheduled end date and working backwards
through the schedule network logic.

5. Attempt any one part of the following: 10*1 = 10

Q.no Questions Marks CO
(a) Discuss in detail about the Change control Software Configuration 10 4
Management.

Solution: Change Control is the process of identifying, documenting,

approving or rejecting, and controlling changes to the project
baselines (including scope baselines, schedule baselines, cost
baselines, etc.). In other words, it is used to control changes to all
aspects of an approved project plan. Change control is a systematic
approach to managing all changes made to a product or system. The
purpose is to ensure that no unnecessary changes are made, all changes
are documented, services are not unnecessarily disrupted and resources
are used efficiently.
 Identification, control, audit, and status accounting are the four basic
requirements for a software configuration management system.
“Configuration control is focused on the specification of both the
deliverables and the processes, while change control is focused on
identifying, documenting, and approving or rejecting changes to the
project documents, deliverables, or baselines”. “Configuration control
is focused on the specification of both the deliverables and the
processes, while change control is focused on identifying,
documenting, and approving or rejecting changes to the project
documents, deliverables, or baselines”. “Configuration control is
focused on the specification of both the deliverables and the processes,
while change control is focused on identifying, documenting, and
approving or rejecting changes to the project documents, deliverables,
or baselines”.

“Configuration control is focused on the specification of both the

deliverables and the processes, while change control is focused on
identifying, documenting, and approving or rejecting changes to the
project documents, deliverables, or baselines”.

(b) Explain in detail about any two of the following. 10 5

(i) Stress.
(ii) Health and Safety.
(ii) Ethical and Professional concerns.

Solution:

(i) Stress: Stress is a feeling of emotional or physical tension. It can

come from any event or thought that makes you feel frustrated, angry,
or nervous. Stress is your body's reaction to a challenge or demand. In
short bursts, stress can be positive, such as when it helps you avoid
danger or meet a deadline. Stress management is a wide spectrum of
techniques and psychotherapies aimed at controlling a person's level of
stress, especially chronic stress, usually for the purpose of and for the
motive of improving everyday functioning.

Some of the most common reasons we experience stress:

1.
2. -Financial obligations
3. -Death of a loved one
4. -Job loss
5. -Traumatic events
6. -Problems at work
7. -Emotional well-being struggles

(ii) Health and Safety: A safety and health management system

means the part of the Organization’s management system which
covers: the health and safety work organization and policy in a
company. The planning process for accident and ill health prevention.
The proven method of reducing risk, maintaining a culture of safety
and improving productivity. A good health and safety management
 system can help minimize risk and protect against accidents in the
workplace. It is not acceptable for anyone to be hurt or fatally injured
at their place of work. Implementing a health and safety system can
help to reduce accidents and boost morale within the business.

(ii) Ethical and Professional concerns: Fundamental ethical issues in

business include promoting conduct based on integrity and trust, but
more complex issues include accommodating diversity, empathetic
decision-making, and compliance and governance that is consistent
with the organization's core values. Ethical issues occur when a given
decision, scenario or activity creates a conflict with a society's moral
principles. Both individuals and businesses can be involved in these
conflicts, since any of their activities might be put to question from an
ethical standpoint. Ethics include a number of features such as secrecy,
respect and honesty while professionalism can be defined as the
expertise, ability and the behavior displayed by an individual of a
certain occupation.

6. Attempt any one part of the following: 10*1 = 10

Q.no Questions Marks CO
(a) Describe any two of the following. 10 2
(i) Basics of Software estimation.
(ii) Effort and Cost estimation.
(iii) Dynamic System Development Method.

Solution:

(i) Basics of Software estimation: There are two basic models for
estimating software development effort (or cost): holistic and activity-
based. The single biggest cost driver in either model is the estimated
project size. Software test estimation is a process of measuring and
managing the duration and actions required to run a complete test on
the software. Time and effort is considerably simple to calculate for
small-scale assignments. But for larger projects. Efficient strategies
must be in place so that no mistakes are made.

(ii) Effort and Cost estimation: Estimates of effort and cost

are generally based on results of analysis using models or historical
data applied to size, activities, and other planning parameters.
Confidence in these estimates is based on rationale for the selected
model and the nature of the data. Effort estimation is the process of
forecasting how much effort is required to develop or maintain a
software application. This effort is traditionally measured in the hours
worked by a person, or the money needed to pay for this work.

(iii) Dynamic System Development Method: Dynamic System

Development Method (DSDM) is an Agile method that focuses on the
full project lifecycle, DSDM (formally known as Dynamic System
Development Method) was created in 1994, and after project managers
using RAD (Rapid Application Development) sought more governance
and discipline to this new iterative way of working. The DSDM
 model prioritizes business cases, ensuring that any projects they
deliver have critical business value. You can provide basic product
functionality at a rapid pace. Developers can easily access their end-
users. Easier for the project to remain within budget.

(b) Write down about any two of the following. 10 3

(i) Critical path (CRM) method.
(ii) Risk identification.
(iii) PERT technique.

Solution:
(i) Critical path (CRM) method: Critical path is the sequential
activities from start to the end of a project. Although many projects
have only one critical path, some projects may have more than one
critical paths depending on the flow logic used in the project.
If there is a delay in any of the activities under the critical path, there
will be a delay of the project deliverables.
Most of the times, if such delay is occurred, project acceleration or re-
sequencing is done in order to achieve the deadlines.
Critical path method is based on mathematical calculations and it is
used for scheduling project activities.
The initial critical path method was used for managing plant
maintenance projects. Although the original method was developed for
construction work, this method can be used for any project where there
are interdependent activities.
In the critical path method, the critical activities of a program or a
project are identified. These are the activities that have a direct impact
on the completion date of the project.

Step 1: Activity specification:

You can use the Work Breakdown Structure (WBS) to identify the
activities involved in the project. This is the main input for the critical
path method.
In activity specification, only the higher-level activities are selected for
critical path method.
When detailed activities are used, the critical path method may become
too complex to manage and maintain.
Step 2: Activity sequence establishment
In this step, the correct activity sequence is established. For that, you
need to ask three questions for each task of your list.
-Which tasks should take place before this task happens?
-Which tasks should be completed at the same time as this task?
-Which tasks should happen immediately after this task?
Step 3: Network diagram
Once the activity sequence is correctly identified, the network diagram
 can be drawn (refer to the sample diagram above).
Although the early diagrams were drawn on paper, there are a number
of computer software, such as Primavera, for this purpose nowadays.
Step 4: Estimates for each activity
This could be a direct input from the WBS based estimation sheet.
Most of the companies use 3-point estimation method or COCOMO
based (function points based) estimation methods for tasks estimation.
Step 5: Identification of the critical path
For this, you need to determine four parameters of each activity of the
network.
-Earliest start time (ES) - The earliest time an activity can start once
the previous dependent activities are over.
-Earliest finish time (EF) - ES + activity duration.
-Latest finish time (LF) - The latest time an activity can finish without
delaying the project.
-Latest start time (LS) - LF - activity duration

Step 6: Critical path diagram to show project progresses

Critical path diagram is a live artifact. Therefore, this diagram should
be updated with actual values once the task is completed.
This gives more realistic figure for the deadline and the project
management can know whether they are on track regarding the
deliverables.
(ii) Risk identification: Risk identification is the process of
determining risks that could potentially prevent the program,
enterprise, or investment from achieving its objectives. It includes
documenting and communicating the concern. Keywords: risk, risk
identification, risk management. The purpose of risk identification is to
reveal what, where, when, why, and how something could affect a
company's ability to operate. For example, a business located in central
California might include “the possibility of wildfire” as an event that
could disrupt business operations.

Ways to identify risk in business:

 -Brainstorming
 -Stakeholder interviews
 -NGT technique
 -Affinity diagram
 -Requirements review
 -Project plans
 -Root cause analysis.
 -SWOT analysis.

(iii) PERT technique: The Program Evaluation Review Technique, or

PERT, is a visual tool used in project planning. Using the technique
 helps project planners identify start and end dates, as well as interim
required tasks and timelines. The information is displayed as a network
in chart form.

To implement a PERT chart:

1. -Identify the different tasks needed to complete a project. Make sure to

add these in the right order and indicate the duration of each task.
2. -Create a network diagram. Use arrows to represent the activities and
use nodes as milestones.
3. -Determine the critical path and possible slack.

7. Attempt any one part of the following: 10*1 = 10

Q.no Questions Marks CO
(a) Briefly discuss any two of the following through an example. 10 1
(i) Cost-benefit evaluation technology
(ii) Risk evaluation
(iii) Stepwise Project Planning

Solution:

(i) Cost-benefit evaluation technology: A cost-benefit analysis (CBA)

is a tool to evaluate the costs vs. benefits in an important business
proposal. A formal CBA lists all project expenses and tangible benefits,
and then calculates the return on investment (ROI), internal rate of
return (IRR), net present value (NPV), and payback period. Cost-
benefit analysis (CBA) is a technique used to compare the total costs of
a programed/project with its benefits, using a common metric (most
commonly monetary units). This enables the calculation of the net cost
or benefit associated with the program.

The Process of Cost-Benefit Analysis:

1. Step 1: Define Project Goals & Objectives

2. Step 2: List Down Alternative Scenarios
3. Step 3: Identify & Schedule Benefits & Costs
4. Step 4: Identify Project Stakeholders
5. Step 5: Track Measurement Metrics
6. Step 6: Convert to Common Currency
7. Step 7: Measure Net Present Value (NPV)

(ii) Risk evaluation: Anyone responsible for a company's data, server,

network, or software must perform a risk evaluation. A risk evaluation
can help determine if those assets are at risk for a cyber-attack, virus,
data loss through natural disaster, or any other threat. Risk evaluation –
the process of comparing an estimated risk against given risk criteria to
determine the significance of the risk. Risk control – actions
implementing risk evaluation decisions.
STEPS TO PERFORM A PROJECT RISK ASSESSMENT:

Step 1: Identify risks. Analyze potential risks and opportunities. .

Step 2: Determine probability
Step 3: Determine the impact
Step 4: Treat the risk
Step 5: Monitor and review the risk

(iii) Stepwise Project Planning: Steps in Project Planning:

Step 0: Select project.

Step 1: Identify project scope and objectives.

Step 2: Identify project infrastructure.

Step 3: Analyze project characteristics.

Step 4: Identify project products and activities.

Step 5: Estimate effort for each activity.

Step 6: Identify activity risks.

Step 1: Identify Project Scope and Objectives
1.1. Identify objectives and practical measures of effectiveness in
meeting those objectives .How do we know we are successful?
1.2: Establish a project authority Who is the boss?
1.3. Stakeholder analysis – identify all stakeholders in the project and
their interests Who does what?
1.4. Modify objectives in the light of stakeholder analysis What shall
we do for the commitment of stakeholders to the project?
1.5. Establish methods of communication with all parties. How do we
stay in touch and informed?
Step 2: Identify Project Infrastructure
2.1. Identify relationship between the project and strategic planning
2.2. Identify installation standards and procedures
2.3. Identify project team organization
Step 3: Analyze Project Characteristics
3.1. Distinguish the project as either objective- or product-driven
3.2. Analyze other project characteristics (including quality-based
ones)
 3.3. Identify high-level project risks
3.4. Take into account user requirements concerning implementation
3.5. Select development methodology and life- cycle approach
3.6. Review overall resource estimates
Step 4: Identify Project Products & Activities
4.1. Identify and describe project products (or deliverables)
4.2. Document generic product flows

(b) Write down about the concept of Contract Management under the 10 4
Management Technique.

Solution: The basic elements required for the agreement to be a legally

enforceable contract are: mutual assent, expressed by a valid offer and
acceptance; adequate consideration; capacity; and legality. In some
states, element of consideration can be satisfied by a valid substitute.
Contract management is when someone takes on the responsibility of
managing contracts for employees or vendors or other parties. Contract
managers need legal knowledge to accurately lead the contract
management process.

Not all companies have set contract managers, but major defense firms
or companies that frequently work with the government tend to use
contract managers. Managing contracts is an overlooked form of
management. Managers interact frequently with employees, and some
of those discussions and situations naturally relate to compensation.
Some of these conversations will deal with contract management. Other
times, businesses need to manage contract agreements with other
businesses. It’s not talked about much, but contract management is an
important business topic. If you’re unsure of how the contract
management process works, it’s important to understand the basics.

When two companies wish to do business with each other, a contract

specifies the activities entered into by both organizations and the terms
through which they will each fulfill their parts of the agreement.
Contracts affect business profitability in a very large way due to the
emphasis on revenue and expenses.

When a contract is phrased poorly, one organization might lose

countless thousands of dollars over a simple technicality they lacked
the resources to identify. Effective contract management can ultimately
create a powerful business relationship and pave the road to greater
profitability over the long term, but only when managed correctly. It’s a
good idea to include a legal department or a lawyer in contract
management discussions.

The precise wording of contracts is crucial to contract management.

Generally, contract management involves a few key stages. There are
the early stages or pre-award phase. This is all the work that takes place
prior to a contract being given to someone, whether it is a business or
an employee. The middle stage is when the process is awarded. This
includes all the paperwork to make the agreement final. Third, there’s
the post-award stage. This is where a lot of contract management and
maintenance comes in.

Those three basic stages are a simple way of looking at contract

management in three phases, but the process is more complicated than
that and can be viewed in more stages depending on how detailed a
view. The foundation for contract management relies on the
implementation of successful post-award and upstream activities.
During the pre-award stage, employees should focus on the reason for
establishing the contract and if the supplier can fulfill the terms of the
agreement.

Additional consideration is needed to understand how the contract will

work once awarded. Avoiding unwanted surprises requires careful
research and clarity of purpose in the actual contract.

Contract management requires a level of flexibility for both parties

involved and a willingness to adapt contract terms to reflect any
changing circumstances. Problems are inevitable, which means
organizations must be prepared for the unexpected and be able to adjust
contract terms when needed.