Q1.

Briefly explain the different phases of project management

life cycle.
1. Initiation: First, you need to identify a business need,
problem, or opportunity and brainstorm ways that your Team
can meet this need, solve this problem, or seize this
opportunity. During this step, you figure out an Objective for
your project, determine whether the project is feasible, and
identify the major deliverables for the Project.
W5HH Principle: Boehm suggested that during project initiation,
the project champions should have Comprehensive answers to a
set of key questions pertaining to the project.
• 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 each resource is needed?
2. Planning: During this phase, a detailed project plan is
created. This plan includes tasks, resources required,
Timelines, costs, etc. In addition, further planning for
prioritizing requirements is doneCommunication Plan ,
Resource Plan , Quality Plan, Deployment Plan
3.Execution Phase: In this phase the tasks are executed as per the
project plan developed during the planning phase .A series of
management processes are undertaken to ensure that the tasks
are executed as per plan Monitoring Control processes are
executed to ensure that the tasks are executed as per plan and
corrective actions are initiated Whenever any deviations from the
plan are noticed.
4.project closure : Project closure involves completing the release
of all the deliverables to the customers along with The necessary
necessary documentation.

Q.2) project portfolio management

Project Portfolio Management (PPM) is about overseeing all the
projects a company has going on. It’s like organizing a bunch of
different tasks to reach a big goal. PPM helps decide which tasks
are most important, how to manage them well, and when to make
changes to keep everything running smoothly.It’s all about making
smart choices to use time, money, and resources wisely to
achieve success.

What is a Project Portfolio?

• 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.

What is Project Portfolio Management? (PPM)

 • Project Portfolio Management (PPM) is like being a team
manager where each member has their tasks to do. It’s
about overseeing and controlling all the projects a company
is working on.
• PPM means deciding which projects are most important and
how to divide up resources like time and money among
them. It’s about steering everything in the right direction to
reach the company’s goals and making sure things stay on
track.
• PPM also involves keeping an eye on progress, spotting and
dealing with any problems, and making changes when
necessary. By doing PPM well, a company can make sure its
projects fit with its overall plans and that it’s getting the best
results.
Q.3)What is Project? What are its characteristics?
Ans :
A project is an activity to meet the creation of a unique product
or service and thus Activities that are undertaken to accomplish
routine activities cannot be considered Projects.
A project is a combination of interrelated activities to achieve a
specific objective Within a schedule, budget, and quality.
It involves the coordination of group activity, wherein the
manager plans, organizes, Staffs directs, and controls to achieve
an objective, with constraints on time, cost, And performance of
the end product.
Characteristics of Project :-
1. Invisibility :
When a physical artefact such as a bridge or road is being
constructed the progress Being made can actually be seen.
 With software, progress is not immediately visible to others and
may be difficult to Quantify In terms of the percentage of work
done.
2. Complexity :
Software projects are complex in nature than other engineering
projects and the Complexity can be gauged by the success rate of
these projects.
3. Flexibility:
The ease with software can be changed is usually seen as one of
its strengths.
However, this means that where the software system interfaces
with a physical or Organizational system, it is expected that,
where necessary, the software will Change to accommodate the
other components rather than vice versa.
This means the software systems are likely to be subject to a
high degree of change.
4. Conformity :
These physical systems have complexity, but are governed by
consistent physical Laws. Software developers have to conform
to the requirement of human clients.
It is not just that individuals can be inconsistent.
Organizations, because of lapses in collective memory, in
internal communication or In effective decision making can
exhibit remarkable, ‘organizational stupidity’.

Q.4) State Capers Jones rules of thumb for software

estimation.
• Rule 1: SLOC-function point equivalence: One function point =
125 SLOC for C programs.
• Rule 2: Project duration estimation: Function points raised to
the power 0.4 predicts the approximate Development time in
calendar months.
• Rule 3: Rate of requirements creep: User requirements creep in
at an average rate of 2% per month from the Design through
coding phases.
• Rule 4: Defect removal efficiency: Each software review,
inspection, or test step will find and remove 30% of the Bugs that
are present.
• Rule 5: Project manpower estimation: The size of the software
(in function points) divided by 150 predicts the Approximate
number of personnel required for developing the application
• Rule 6: Number of personnel for maintenance Function points
divided by 500 predicts the approximate number of Personnel
required for regular maintenance activities.
• Rule 7: Software development effort estimation: The
approximate number of staff months of effort required to Develop
a software is given by the software development time multiplied
with the number of personnel required.
Q5)Explain Scrum. What do you understand by the term
‘ceremonies’ in a Scrum Project ?
Ans :
Scrum is an efficient framework within which you can develop
software with teamwork. It Is based on agile principles. It is a
framework for developing and sustaining complex products.
Ken Schwaber and Jeff Sutherland developed Scrum. Together,
they stand behind the Scrum Rules. Scrum is not a process or a
technique for building products; rather, it is a framework Within
which you can employ various processes and techniques. Scrum
makes the relative Efficacy of your product management and
development practices so that you can improve.
Scrum is:
Lightweight
Simple to understand
Difficult to master
Scrum has been used to develop software, hardware,
embedded software, networks of Interacting function,
autonomous vehicles, schools, government, marketing,
managing The operation of organizations and almost everything
we use in our daily lives, as Individuals and societies.
In order to provide transparency and regular communication in
the midst of such Environments are held. Scrum ceremonies are
meetings that are unique to scrum Teams.
Scrum is executed in what are called sprints, or short iterations
of work lasting usually No more than two weeks. The scrum
ceremonies are outlined below:
1. Sprint Planning: This is where the team meets and decides
what they need to complete In the coming sprint.
2. Daily Scrum: This is a stand up meeting, or a very short – 15-
minute mini-meeting – for The team to make sure they are all
on the same page.
3. Sprint Review: This is another type of meeting, but one in
which the team demos what They shipped in the sprint.
4. Sprint Retrospective: This is when the team reviews their
work, identifying what they
Did well and what didn’t go as planned, so they can make the next
sprint better.

Q6) 5 major components of Albrecht function.

Function Point Analysis (FPA) is a method used to measure the
functionality provided by a software application.
The major components of an FPA are:
1. Internal Logical Files (ILF): ILFs represent data maintained
within the software and are under the control of the
Application. They are essentially collections of data that the
software stores, retrieves, and maintains. Examples Include
databases, files, or tables used by the application.
2. External Interface Files (EIF): EIFs represent data used by the
software but maintained by external applications. They are
data shared between the application being analyzed and
other external systems. This can include files, Databases, or
interfaces with other software systems.
3. External Inputs (EI): These are processes or functions
through which the software receives data from external
Sources, processes it, and updates the ILFs. These inputs
might involve data validation, calculations, or data Storage.
EIs are a way of quantifying the number of ways users can
interact with the system.
4. External Outputs (EO): EO processes generate data for the
external world based on data in ILFs. They involve
Formatting, summarizing, or otherwise transforming data
from the system for presentation to users or external
Systems. EO functions quantify the number of distinct types
of outputs.
5. External Inquiries (EQ): EQs are processes that provide
information to the user without updating internal data. They
are typically used for retrieving information or reporting. EQ
functions measure the number of different Types of inquiries
a system can respond to.
Q7)What is Contract? Explain the advantages and
disadvantages of fixed price-contracts.
Ans : Contracts are used for establishing business deals and
partnerships. The parties involved In the business engagement
 decide the type of the contract. Usually, the type of the contract
Used for the business engagement varies depending on the type
of the work and the nature of The industry.
1. Advantages of Fixed Price Contracts:
• Budget Certainty: One of the main advantages of fixed price
contracts is that they Provide budget certainty to the client. Since
the price is agreed upon before the project Starts, the client knows
exactly how much they will have to pay, allowing for better Financial
planning.
• Reduced Client Risk: Fixed price contracts shift the risk from the
client to the software Development company. The development
company is responsible for managing the Project efficiently and
delivering the agreed-upon scope within the fixed budget.
• Simplified Contract Management: Fixed price contracts are usually
simpler to manage Because the terms and conditions are well-
defined, leaving less room for disputes and Changes during the
project.
• Incentive for Efficiency: Since the development company has a
fixed budget, they are Incentivized to be efficient in their work and
find ways to deliver the project within the Agreed-upon cost.
2. Disadvantages of Fixed Price Contracts:
• Limited Flexibility: Fixed price contracts offer little room for
changes in project scope or Requirements. If the client wants to
make changes during the development process, it Can lead to
additional costs and potential conflicts.
• Scope Creep Impact: Scope creep, which refers to the gradual
expansion of project Scope beyond what was originally agreed
upon, can be problematic in fixed price Contracts. Dealing with
scope changes can be challenging and may require negotiation And
additional costs.
• Quality Concerns: In some cases, the development company may
be incentivized to cut Corners to meet the fixed budget, potentially
compromising the overall quality of the Software product.
Q8)Consider the cash flows estimates for four projects as
shown in the table: Negative levels represent expenditure and
positive values income. Rank the four projects in order of
financial desirability and make a note of your reasons for
ranking them in that way. Conclusion should be based on Net
Profit, and ROI (Return On Investment)

YEAR PROJECT 1 PROJECT 2 PROJECT 3 PROJECT 4

0 -100000 -100000 -1000000 -120000

1 20000 20000 300000 30000

2 30000 30000 300000 30000

3 10000 20000 300000 30000

4 20000 20000 300000 30000

5 20000 30000 300000 50000

Net Profit ? ? ? ?
ROI ? ? ? ?
Ans :
Net Profit for Project 1: Sum of all cash flows over the years
Net Profit = (-100000) + 20000 + 30000 + 10000 + 20000 + 20000 =
80000
ROI for Project 1:
ROI = (Net Profit / Initial Investment) * 100
ROI = (80000 / 100000) * 100 = 80%
 Net Profit for Project 2: Sum of all cash flows over the years
Net Profit = (-100000) + 20000 + 30000 + 20000 + 20000 + 30000 =
20000
ROI for Project 2:
ROI = (Net Profit / Initial Investment) * 100
ROI = (20000 / 100000) * 100 = 20%
Net Profit for Project 3: Sum of all cash flows over the years
Net Profit = (-1000000) + 300000 + 300000 + 300000 + 300000 +
300000 = 500000
ROI for Project 3:
ROI = (Net Profit / Initial Investment) * 100
ROI = (500000 / 1000000) * 100 = 50%
Net Profit for Project 4: Sum of all cash flows over the years
Net Profit = (-120000) + 30000 + 30000 + 30000 + 30000 + 50000 =
58000
ROI for Project 4:
ROI = (Net Profit / Initial Investment) * 100
ROI = (58000 / 120000) * 100 = 48.33%
Now, let’s rank the projects based on financial desirability:
Project 3: It has the highest Net Profit (500000) and a moderate
ROI of 50%.
Project 1: It has the second-highest Net Profit (80000) and the
highest ROI of 80%.
Project 4: It has the third-highest Net Profit (58000) and a ROI of
48.33%.
Project 2: It has the lowest Net Profit (20000) and the lowest ROI
of 20%.
Q9)Q8. Suppose four risk namely R1,R2,R3,R4 have been
identified and assigned the probabilities of

Occurrence of 0.1,0.2,0.3,0.4 respectively .the likely damages

due to the four risks are Rs 50000; Rs 100000; Rs 70000; Rs
60000 respectively . Calculate he risk exposure of all the risks.
Risk exposure is calculated as the product of the probability of
the risk and the impact of the risk. It is Usually measured in terms
of financial loss.
Let’s calculate the risk exposure for each risk:
Risk Exposure for R1 = Probability of R1 * Impact of R1
Risk Exposure for R2 = Probability of R2 * Impact of R2
Risk Exposure for R3 = Probability of R3 * Impact of R3
Risk Exposure for R4 = Probability of R4 * Impact of R4
Substituting the given values:
Risk Exposure for R1 = 0.1 * Rs 50000 = Rs 5000
Risk Exposure for R2 = 0.2 * Rs 100000 = Rs 20000
Risk Exposure for R3 = 0.3 * Rs 70000 = Rs 21000
Risk Exposure for R4 = 0.4 * Rs 60000 = Rs 24000
So, the risk exposures for risks R1, R2, R3, and R4 are Rs 5000, Rs
20000, Rs 21000, and Rs 24000 Respectively.
Q10)What is CMM(Capability Maturity Model)? What are the
various levels of CMM?
Ans : Rather than just checking that a system is in place to defect
faults, a customer might wish To check that a supplier is using
software development methods & tools that are likely to Produce
good quality software. A customer will feel more confident, for
instance, if they know that the supplier is using structured
methods. This attempts to place organizations producing
Software at one of five level of process maturity to indicate the
sophistication and quality of Their software production practices.
There in all five levels in the model.
Level 1: Initial
The procedures followed tend to be haphazard. Some projects
will be successful, but this tends To be because of the skills of
particular individuals including project managers. There is no
level 0 as so any organization would be at this level by default.
Level 2: Repeatable
Organizations at this level will have basic project management
procedures in place. However, The way an individual task is
carried out will depend largely on the person doing it.
Level 3: Defined
The organization has defined the way in which each task in the
software development life cycle Is to be done.
Level 4: Managed
The product and process involved in software development are
subject to measurement and Control.
Level 5: Maturity
Improvement in procedures are designed and implemented using
the data gathered from the Measurement process.