Software Project Management imp qustions

1) Project Portfolio management (ppm) ?

Ans:
1. What is PPM?

o PPM is about managing multiple projects together as a portfolio to make sure

they align with the company’s goals and provide the most value.
2. Main Goals of PPM
o Choose the Right Projects: Select projects that bring the highest value.
o Balance Resources: Use resources wisely across all projects (money, people,
time).
o Minimize Risks: Look at risks across all projects and plan to reduce them.
o Measure Success: Track project progress and see if they are meeting goals.
3. Steps in PPM
o Portfolio Selection: Decide which projects to take on based on their potential
benefits.
o Resource Allocation: Assign resources to each project to avoid conflicts.
o Risk Assessment: Identify and prepare for risks affecting the whole portfolio.
o Monitoring and Reporting: Regularly check if projects are on track and adjust
if needed.
4. Benefits of PPM
o Efficient Resource Use: Focuses on high-value projects.
o Better Decision-Making: Gives a clear view of all projects.
o Risk Management: Helps in reducing risks by planning at the portfolio level.
5. Popular Tools for PPM
o Tools like Microsoft Project, Smartsheet, and [Link] help manage PPM
by providing features for scheduling, tracking, and reporting.
*Why PPM is Important
 PPM helps ensure that projects not only succeed individually but also contribute to
the company’s overall strategy and goals.
Software Project Management imp qustions

2) Activite's methodologies ?
Ans :
1. Definition of Activite’s Methodologies: Activite’s methodologies refer to a set of
organized approaches used in managing software projects. These methodologies aim
to streamline project management processes, including planning, monitoring, and
execution.
2. Key Methodologies:
o Waterfall Model: This linear, sequential approach is best suited for projects
with well-defined requirements. It breaks down the process into distinct
phases, such as requirement analysis, system design, implementation, testing,
deployment, and maintenance.
o Agile Methodology: Agile promotes flexibility and collaboration, especially
for projects with evolving requirements. It breaks the project into sprints or
iterations, enabling incremental delivery and continuous feedback.
o Scrum: Scrum is a framework under Agile, emphasizing team roles,
ceremonies (like sprints and daily standups), and artifacts (such as product
backlogs). It is effective for projects needing adaptive planning and quick
delivery.
o Kanban: Kanban focuses on visualizing tasks and work-in-progress limits. It
helps streamline workflow by making it easier to spot bottlenecks.
o Critical Path Method (CPM) and Program Evaluation Review Technique
(PERT): These are project scheduling techniques. CPM identifies essential
tasks and estimates project duration, while PERT focuses on estimating the
time for project milestones.
3. Importance in SPM:
o Ensures efficient resource allocation.
o Helps in meeting deadlines and staying within budget.
o Minimizes risks by anticipating challenges early on.
4. Exam Tip: Explain these methodologies concisely, highlighting their key
characteristics and when each is most effective. Diagrams or flowcharts (like the
Waterfall model’s sequence or Agile’s iteration cycles) can make answers more
effective.
3) Catrgarzation Of Software Project ?
Ans:
1. Based on Size:
 Small Projects: Limited scope and resources, typically handled by a small team.
Examples include personal or startup projects.
 Medium Projects: Moderate scope and complexity, often requiring multiple teams.
Examples include departmental or organizational software.
 Large Projects: High complexity and resource needs, usually with multiple teams
and stakeholders. Examples include enterprise systems or government projects.
2. Based on Complexity:
 Simple Projects: Straightforward requirements and minimal risk, usually with a
single objective. Examples include utility software or simple web apps.
 Complex Projects: Involve challenging requirements, often with multi-layered
objectives and high risk. Examples include operating systems or ERP systems.
Software Project Management imp qustions

3. Based on Application Domain:

 Business Software: Focuses on tasks such as accounting, HR, and inventory
management.
 Engineering and Scientific Software: Used for technical fields requiring
simulations, calculations, and modeling.
 Embedded Software: Designed for hardware control, such as software for
appliances, cars, or medical devices.
4. Based on Ownership and Usage:
 Commercial Software: Developed for sale to end-users or companies.
 Custom Software: Created for a specific client’s needs.
 Open-Source Software: Freely available, often developed by communities.
5. Based on Delivery Schedule:
 Contract-Based: Delivered on a fixed timeline with predetermined requirements.
 Product-Based: Developed incrementally, often with ongoing releases

4) Management Principals ?
Ans :
1. Planning:
 Involves setting goals, defining strategies, and outlining tasks to achieve objectives.
 Example: Creating a project timeline and assigning deadlines.
2. Organizing:
 Structuring resources (people, materials, finances) to accomplish goals efficiently.
 Example: Assigning roles and responsibilities within a team.
3. Staffing:
 Involves recruiting, training, and retaining the right people for the job.
 Example: Conducting interviews and providing skill-based training to new hires.
4. Leading:
 Motivating and directing employees to work towards the organization's objectives.
 Example: Inspiring team members through positive reinforcement and setting clear
expectations.
5. Controlling:
 Monitoring and assessing performance to ensure that goals are met.
 Example: Conducting regular reviews to compare progress with the initial plan.
6. Coordinating:
 Ensuring that different departments or team members work harmoniously.
Software Project Management imp qustions

 Example: Facilitating communication between the marketing and product

development teams.
7. Decision-Making:
 Choosing the best course of action among alternatives to solve problems.
 Example: Deciding on a cost-effective solution to manage a budget overrun.

8. Innovation:
 Embracing change and encouraging new ideas to improve processes or products.
 Example: Implementing new technology to increase productivity.
9. Communication:
 Ensuring clear and effective information flow within the organization.
 Example: Holding regular team meetings to keep everyone updated on project
progress.

5) Risk Evalution ?
Ans:
Risk Evaluation
Risk evaluation is the process of analyzing and assessing identified risks to determine their
level of impact and likelihood of occurrence. It involves prioritizing these risks based on their
potential to affect the objectives of a project, organization, or system. The goal is to make
informed decisions on which risks require attention, mitigation, or acceptance.
Key Steps in Risk Evaluation
1. Identify the Risks
Recognize potential threats or vulnerabilities that could impact objectives.
2. Assess Likelihood and Impact
o Likelihood: Estimate the probability of each risk occurring. Ratings are often
categorized (e.g., High, Medium, Low).
o Impact: Evaluate the severity of the consequences if the risk materializes.
This can also be ranked (e.g., Critical, Major, Minor).
3. Develop a Risk Matrix
A risk matrix is a tool used to visualize and prioritize risks by mapping them based on
their likelihood and impact. Higher-ranked risks are typically addressed first.
4. Prioritize the Risks
Based on the matrix, identify which risks need immediate action and which can be
monitored or accepted.
Software Project Management imp qustions

5. Decision Making
After prioritization, determine the appropriate response for each risk:
o Avoidance: Altering plans to eliminate the risk.
o Mitigation: Implementing measures to reduce the likelihood or impact.
o Transfer: Shifting the risk to another party (e.g., through insurance).
o Acceptance: Acknowledging the risk and planning for potential impacts.
6. Document and Monitor
Document the evaluation results, and regularly monitor the risks to identify any
changes in their status.
Importance of Risk Evaluation
Risk evaluation allows organizations to:
 Efficiently allocate resources to address critical risks.
 Reduce uncertainties and minimize potential losses.
 Improve decision-making by providing a clear understanding of risk impacts.

Unit-2
1) Software Process ?
Ans:
Software Process
The software process is the framework that guides the development of software
applications. It defines the stages and steps to be followed from the initial idea to the final
product. A well-defined process helps ensure that software is developed efficiently, on
time, and within budget.
Key Stages in the Software Process
1. Requirements Gathering
o What it is: Collecting and defining the software's requirements.
o Purpose: Understand what the software needs to do based on user needs and
system constraints.
o Outcome: A clear requirements document.
2. Design
o What it is: Planning how the software will work and look.
o Purpose: Decide on the system architecture, database design, user interface,
and more.
Software Project Management imp qustions

o Outcome: Design specifications that guide the development.

3. Implementation (Coding)
o What it is: Writing the actual code to create the software.
o Purpose: Convert the design into a working system using programming
languages.
o Outcome: The software codebase.
4. Testing
o What it is: Checking the software for bugs or errors.
o Purpose: Ensure that the software works as intended and meets the
requirements.
o Outcome: A tested and reliable software product.
5. Deployment
o What it is: Installing the software on users' systems or servers.
o Purpose: Make the software available for use.
o Outcome: The software is live and in use by the end users.
6. Maintenance
o What it is: Making updates and fixing issues after the software is deployed.
o Purpose: Ensure the software remains functional and up-to-date.
o Outcome: Improved or bug-free software over time.

Types of Software Processes

1. Waterfall Model
o Description: A linear and sequential approach where each stage is completed
before moving to the next.
o Pros: Easy to understand and manage.
o Cons: Rigid and doesn’t accommodate changes well.
2. Agile Model
o Description: An iterative and flexible approach where development happens
in short cycles (sprints), allowing for frequent changes.
o Pros: Fast delivery, adaptable to changes.
o Cons: Less predictability and can be hard to manage.
Software Project Management imp qustions

3. V-Model
o Description: An extension of the waterfall model, where each development
phase is directly associated with a testing phase.
o Pros: Clear stages and easy to manage.
o Cons: Not as flexible as Agile.

4. Spiral Model
o Description: A risk-driven model that combines iterative development with
the systematic approach of the waterfall model.
o Pros: Focuses on risk management and allows for flexibility.
o Cons: Can be complex and expensive.
Why a Software Process is Important
 Consistency: Helps teams follow a clear, repeatable approach.
 Quality: Ensures software meets user needs and is free of bugs.
 Efficiency: Streamlines development, reducing time and cost.
 Risk Management: Identifies and manages risks early on.

2) Choice Of Process Modle ?

Ans :
Waterfall Model:
 Sequential and rigid, suitable for projects with clear, fixed requirements.
 Works best for smaller projects or exams where you need to follow step-by-step
processes.
V-Model (Verification and Validation):
 Extends the Waterfall model with a focus on testing at each phase.
 Useful when you need to emphasize testing and quality assurance in the exam
scenario.
Agile Model:
 Iterative and flexible, focusing on collaboration, customer feedback, and adaptability.
 Best if the exam involves dynamic or evolving requirements.
Spiral Model:
 Combines elements of both design and prototyping in stages, with an emphasis on risk
management.
 A good choice for exams requiring risk analysis or gradual refinement.
Incremental Model:
 Develops the system in small, manageable segments or increments.
Software Project Management imp qustions

 Can be beneficial if the exam focuses on delivering functional prototypes or stages of

work.
RAD (Rapid Application Development):
 Focuses on rapid prototyping and user feedback.
 Ideal for exams requiring quick prototyping or user-centered design.
DevOps Model:
 Focuses on collaboration between development and operations teams, with an
emphasis on continuous integration and delivery.
 Suitable for exams related to software deployment and automation.

3) Rapid Application Development?

Ans :
Key Components of RAD:
1. Prototyping:
o Rapid development of prototypes that can be quickly modified based on user
feedback.
o In an exam, this could mean creating a working model or prototype of a
system as part of the exam deliverables.
2. User Feedback:
o Continuous interaction with end-users to refine and improve the product.
o Your exam might require you to design a system that allows for user input,
which will influence the development direction.
3. Time-boxed Phases:
o Short development cycles that allow you to deliver working models or parts of
a system quickly.
o This could translate to creating a specific module or feature within a limited
timeframe during your exam.
4. Collaboration:
o Strong emphasis on collaboration between developers and users.
o This means ensuring that stakeholders' needs are met quickly, which might
involve group work or team collaboration in an exam.
RAD Phases:
1. Requirements Planning:
o Gather high-level requirements, typically focusing on the most important
functionalities.
Software Project Management imp qustions

o In your exam, outline the key features and functionalities your system will
focus on, keeping it minimal but functional.
2. User Design:
o Prototypes are built based on user requirements and feedback.
o In the exam, you might need to develop wireframes or basic system interfaces
that can be refined later.
3. Construction:
o The system is built using the prototypes and refined based on testing and user
feedback.
o This phase could involve coding small sections of the system rapidly, ensuring
you demonstrate key functionalities.
4. Cutover (Implementation):
o Final system integration and deployment.
o You may be asked to present how you would deploy or finalize a system based
on the feedback collected.
How RAD Works in Exams:
 Speed and Iteration: Focus on rapid prototyping and quick development. Ensure
your deliverables are functional even if they are not fully polished.
 User-Centered: If applicable, demonstrate how your design is based on user feedback
(you may need to justify design decisions).
 Focus on Core Functionality: Rather than a full system, focus on delivering working
pieces that demonstrate core functionality within the exam timeframe.
 Documentation: You might need to briefly document the iterative process,
emphasizing how feedback and changes led to improvements.
Best Practices for RAD in an Exam:
 Prioritize key features that address the main problems or requirements.
 Make sure your prototypes or designs can be easily modified based on potential
feedback.
 Keep your development process well-organized, even if it is iterative.
 Ensure that your time management allows for completion of at least one functional
part of the system.
4) Cosmic Full Funtion Point?
Ans:
Simplified Explanation of COSMIC FFP:
Software Project Management imp qustions

1. Focus on Data Movement:

o COSMIC FFP measures how data moves into or out of a system and how data
is stored or retrieved.
o It considers data movements such as:
 Data Entry: When data is entered into the system.
 Data Exit: When data is retrieved or sent out of the system.
 Data Read: When data is read from a storage or external source.
 Data Write: When data is written to a storage or external destination.
2. Key Components in COSMIC FFP:
o Data Groups: Logical entities that are involved in the data movements. These
include entities like user inputs, database records, etc.
o Function Types: Defines the type of function that is performed based on the
data movement (e.g., input, output, storage).
o Four Types of Data Movements:
 Entry: Moving data into the system.
 Exit: Moving data out of the system.
 Read: Retrieving data from storage.
 Write: Storing data in the system.
3. Calculation of Function Points:
o The COSMIC FFP method assigns function points based on the type and
complexity of the data movements.
o Each type of data movement has a specific weight or score, which is used to
calculate the total function points.
o For example, entering a small piece of data might be worth fewer points than
writing complex data to storage.
Steps for Simplified COSMIC FFP Counting:
1. Identify Data Movements: Break down the system's operations and identify all the
data movements (entries, exits, reads, and writes).
2. Classify Data Movements: Classify the data movements according to their type
(entry, exit, read, write).
3. Assign Weights: Assign weights to each data movement based on its complexity. The
weights are typically predefined for common system functions (e.g., user inputs,
database retrievals).
Software Project Management imp qustions

4. Count Function Points: Add up the points for each data movement to calculate the
total function points for the system or module.
5. Total Function Points: The sum of the points gives you the Total Function Points,
which reflect the system’s size and complexity.
Example:
 Suppose you have a system where:
o Data is entered by a user (1 point for entry).
o Data is read from a database (1 point for read).
o Data is written to a file (2 points for write).
o Data is exited for a report (2 points for exit).
Total function points: 1 (entry) + 1 (read) + 2 (write) + 2 (exit) = 6 function points.
Key Takeaways for Your Exam:
 Focus on Data Movements: Understand the four main types of data movements—
entry, exit, read, and write.
 Understand Weights: Different data movements have different weights depending on
their complexity.
 Total Function Points: Calculate the total function points based on the sum of
individual data movements.

Unit-3
1) Project Schedules ?
Ans:
1. Break Down the Project into Tasks (Work Breakdown Structure):
 Identify Tasks: List all the tasks or activities that need to be done. Break large tasks
into smaller, manageable pieces.
 Example: For a software development project, tasks might include:
o Requirement gathering
o Design
o Coding
o Testing
o Deployment
2. Sequence the Tasks:
Software Project Management imp qustions

 Determine Dependencies: Identify which tasks depend on others to be completed

first.
o Example: You can’t start coding until the design is done.
 Create a Flow: Arrange the tasks in the correct order of execution, considering any
dependencies.
3. Estimate Time for Each Task:
 Time Estimates: Estimate how long each task will take to complete.
o Example: If coding will take 2 weeks, testing will take 1 week, etc.
 Be realistic with your time estimates.
4. Assign Resources:
 Who will do the work? Identify who will perform each task or what resources (tools,
software, etc.) are needed.
 Example: "John will handle the design, Sarah will do the testing."
5. Create a Timeline (Gantt Chart or Calendar):
 Use a Gantt Chart: This is a simple visual tool that shows tasks on a timeline.
o Each task is listed on the vertical axis, and time is shown on the horizontal
axis.
o Mark each task’s start and end dates on the chart.
 Example: If coding starts on Day 1 and ends on Day 14, you’ll show this duration on
the chart.
6. Set Milestones:
 Milestones are key points in the project, like the completion of a major task or phase.
 Example: "Design complete" or "First prototype delivered."
7. Monitor and Adjust:
 Track Progress: As tasks get completed, update your schedule.
 Adjust for Delays: If a task takes longer than planned, adjust the timeline for
subsequent tasks.
Example Project Schedule:
1. Task Breakdown:
o Requirement Gathering (2 days)
o Design (4 days)
o Development (7 days)
Software Project Management imp qustions

o Testing (3 days)
o Deployment (1 day)
2. Dependencies:
o Design depends on Requirement Gathering.
o Development depends on Design.
o Testing depends on Development.

3. Estimated Time:
o Requirement Gathering: 2 days
o Design: 4 days
o Development: 7 days
o Testing: 3 days
o Deployment: 1 day
4. Gantt Chart:

Task | Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | Day 6 | Day 7 | Day 8 | Day 9 | Day 10 |
Day 11 | Day 12 | Day 13 | Day 14 | Day 15
Requirement Gathering | X |X | | | | | | | | | | | |
Design | | |X |X |X |X | | | | | | | |
Development | | | | |X |X |X |X |X |X |X | | |
Testing | | | | | | | | |X |X |X | | |
Deployment | | | | | | | | | | | |X | |
8. Review and Update:
 Periodically review the schedule and adjust based on progress.
 Ensure that any delays or unexpected events are accounted for.
Key Tips for Exams:
 Clear Breakdown: Make sure to break down the project into manageable tasks.
Software Project Management imp qustions

 Time Management: Use realistic time estimates for each task.

 Dependencies: Clearly identify tasks that depend on others and sequence them
accordingly.
 Use Tools: If allowed, use simple Gantt charts, tables, or even lists to visualize the
schedule.

2) Backward & Froward Pass?

Ans:
1. Forward Pass:
 Purpose: To calculate the earliest start time (ES) and earliest finish time (EF) for each
task in the project.
 Process:
o Start from the first task in the project (the start of the project).
o For each task, calculate:
 Earliest Start (ES): The earliest time the task can start.
 Earliest Finish (EF): The earliest time the task can finish (EF = ES +
Duration).
o Move through the tasks, from the start to the end, applying these calculations.
Steps:
1. Start at the beginning of the project.
2. For each task, calculate the ES and EF, based on the task duration and the finish time
of its predecessor.
3. Move forward to subsequent tasks, updating their ES and EF.
Example:
 Task A: Duration = 3 days → ES = Day 1, EF = Day 3.
 Task B: Duration = 4 days → ES = Day 4, EF = Day 7 (since it depends on Task A).
 Task C: Duration = 2 days → ES = Day 7, EF = Day 9 (depends on Task B).
2. Backward Pass:
 Purpose: To calculate the latest start time (LS) and latest finish time (LF) for each
task without delaying the project.
 Process:
o Start from the last task in the project (the end of the project).
o For each task, calculate:
 Latest Finish (LF): The latest time the task can finish without
delaying the project.
Software Project Management imp qustions

 Latest Start (LS): The latest time the task can start (LS = LF -
Duration).
o Move backward through the tasks, updating their LF and LS.
Steps:
1. Start at the end of the project.
2. For each task, calculate the LF and LS, based on the LF of the next task (if there's
more than one subsequent task, use the earliest LF from them).
3. Move backward to previous tasks, updating their LF and LS.
Example:
 Task C: Duration = 2 days → LF = Day 9, LS = Day 7.
 Task B: Duration = 4 days → LF = Day 7, LS = Day 3 (since Task C follows it).
 Task A: Duration = 3 days → LF = Day 3, LS = Day 1.
Free Slack and Total Slack:
 Free Slack: The amount of time a task can be delayed without affecting the start
time of any subsequent tasks.
 Total Slack: The amount of time a task can be delayed without affecting the overall
project completion.
Key Takeaways for Exams:
1. Forward Pass: Calculates the earliest times for starting and finishing tasks.
2. Backward Pass: Calculates the latest times for starting and finishing tasks.
3. Use both to find the critical path (tasks with zero slack time).
4. Slack helps in understanding where delays can occur without affecting the project
deadline.

Example Breakdown:
Task List:
Task Duration Predecessors

A 3 days None

B 4 days A

C 2 days B

Forward Pass:
 Task A: ES = 1, EF = 3
 Task B: ES = 4, EF = 7 (depends on Task A)
 Task C: ES = 7, EF = 9 (depends on Task B)
Backward Pass:
 Task C: LF = 9, LS = 7
 Task B: LF = 7, LS = 3 (depends on Task C)
 Task A: LF = 3, LS = 1 (depends on Task B)

3) Critical Path Method (CPM)?

Critical Path Method (CPM):
Software Project Management imp qustions

It’s a project management technique used to determine the longest sequence of activities in a
project, which dictates the shortest possible project duration.
Key Points to Remember:
1. Activities: Tasks that need to be completed in a project.
2. Dependencies: Some activities must be completed before others can start.
3. Critical Path: The longest path through the network of tasks. It determines the
minimum time needed to complete the project. If any task on this path is delayed, the
whole project is delayed.
Steps to Find the Critical Path:
1. List all activities: Break down the project into tasks and list them.
2. Identify dependencies: Determine which tasks depend on others before they can
start.
3. Estimate durations: Estimate how long each task will take.
4. Draw a network diagram: Use arrows to show the flow of tasks and dependencies.
5. Calculate project duration: Add up the durations along each possible path.
6. Find the critical path: The path with the longest total duration is the critical path.
Simple Example:
Let’s say you have a project with the following tasks and durations:
 A: 3 days
 B: 4 days (depends on A)
 C: 2 days (depends on A)
 D: 5 days (depends on B and C)
The paths would be:
 A → B → D: 3 + 4 + 5 = 12 days
 A → C → D: 3 + 2 + 5 = 10 days
The Critical Path is A → B → D because it takes the longest (12 days).
Key Terms:
 Slack/Float: The amount of time that a task can be delayed without delaying the
project.
 Earliest Start (ES): The earliest time an activity can start.
 Latest Finish (LF): The latest time an activity can finish without delaying the project.
Software Project Management imp qustions

4) PERT Techniqus?
Ans:
What is PERT?
PERT is a project management tool used to plan, schedule, and control complex
projects. It focuses on the time needed to complete tasks and helps determine the
minimum time required to finish a project.
Key Concepts:
1. Activities/Tasks: Individual work that needs to be done.
2. Dependencies: Some tasks must be completed before others can start.
3. Time Estimates: PERT uses three time estimates for each task:
o Optimistic Time (O): The shortest possible time to complete the task.
o Pessimistic Time (P): The longest possible time to complete the task.
o Most Likely Time (M): The best guess for how long the task will take under
normal conditions.
PERT Formula:
To calculate the expected time (TE) for each task, use this formula:
TE=O+4M+P6TE = \frac{O + 4M + P}{6}TE=6O+4M+P
This gives you a weighted average that accounts for all possible outcomes.
Steps to Use PERT:
1. List all activities: Break the project into tasks and list them.
2. Determine dependencies: Identify which tasks must be done before others.
3. Estimate times: For each task, estimate the optimistic, most likely, and pessimistic
times.
4. Draw a network diagram: Create a flowchart showing the tasks and their
dependencies.
5. Calculate the expected time: Use the formula above to get the expected time for
each task.
6. Find the critical path: Determine the longest path through the network, which will
give the project’s duration.
Example:
Let’s say you have a task with the following time estimates:
 Optimistic Time (O) = 2 days
 Most Likely Time (M) = 5 days
 Pessimistic Time (P) = 8 days
Using the PERT formula:
TE = 62+4(5)+8 = 2+20+8=30= 5days
6 6 6
Key Terms:
 Critical Path: The longest path through the network of tasks, which determines the
project’s duration.
 Slack/Float: The amount of time a task can be delayed without affecting the project.
 Expected Time (TE): The average time it will take to complete a task using PERT’s
weighted approach.
Summary:
 PERT is used for projects with uncertain activity durations.
 It focuses on time estimation and helps schedule tasks.
Software Project Management imp qustions

 Three time estimates are used for each task: Optimistic, Pessimistic, and Most Likely.
 The Critical Path shows the longest sequence of tasks and determines the project
duration.

5) Risk management & Planning?

Ans:
What is Risk Management?
Risk Management is the process of identifying, assessing, and controlling risks to ensure
that the project achieves its objectives without being affected by unexpected events.
Key Steps in Risk Management:
1. Risk Identification:
o Identify potential risks that could affect the project.
o Examples: Financial risks, technical issues, resource shortages, weather
conditions.
2. Risk Assessment (Risk Analysis):
o Qualitative Analysis: Assess the likelihood and impact of each risk based on
experience or judgment.
o Quantitative Analysis: Use data to calculate the probability and impact of
risks.
o Prioritize risks based on their potential impact on the project.
3. Risk Response Planning:
o Decide on strategies to handle identified risks:
Software Project Management imp qustions

 Avoid: Change the plan to eliminate the risk.

 Mitigate: Take steps to reduce the likelihood or impact of the risk.
 Transfer: Shift the risk to a third party (e.g., insurance).
 Accept: Acknowledge the risk and decide to deal with it if it occurs.
4. Risk Monitoring and Control:
o Continuously monitor the project for new risks and assess existing risks.
o Adjust the risk management plan if new risks arise or if current risks change.
Risk Management Plan:
A Risk Management Plan outlines the process for identifying, analyzing, and managing
risks throughout the project. It includes:
 Risk identification process: How risks will be identified.
 Risk assessment approach: Methods used to analyze and evaluate risks.
 Risk response strategies: Plans for mitigating or addressing risks.
 Risk monitoring procedures: How risks will be tracked and reviewed over time.
Key Terms to Remember:
 Risk: An event that may affect the project in a negative or positive way.
 Risk Impact: The potential effect a risk will have on the project (e.g., schedule, cost,
quality).
 Risk Probability: The likelihood that a risk will occur.
 Mitigation: Reducing the severity of the risk’s impact.
 Contingency Plan: A backup plan if a risk occurs.
Simple Example:
Imagine you're planning a project to build a new product:
1. Risk Identification: The team identifies potential risks like equipment failure or
delay in receiving materials.
2. Risk Assessment:
o Equipment failure might have a high impact and moderate probability.
o Material delay might have a moderate impact but high probability.
3. Risk Response Planning:
o For equipment failure, the team buys backup equipment (mitigation).
o For material delay, they set a new delivery schedule (acceptance).
Software Project Management imp qustions

4. Risk Monitoring and Control: The project manager regularly checks the status of
equipment and suppliers to ensure no new risks emerge.

Unit-4
1) Framework For Management And Control ?
Ans:
What is a Framework for Management and Control?
A Framework for Management and Control is a structured approach to managing and
overseeing a project or organization. It ensures that resources are used efficiently, objectives
are met, and any issues are addressed promptly.
Key Components of a Framework for Management and Control:
1. Planning:
o Objective Setting: Define clear, measurable goals for the project or
organization.
o Resource Allocation: Plan how resources (time, money, manpower) will be
used to achieve these objectives.
2. Organizing:
o Structure: Set up teams, define roles, and create processes for task execution.
o Delegation: Assign tasks and responsibilities to the right people or teams.
3. Monitoring:
o Performance Measurement: Track progress towards goals using key
performance indicators (KPIs).
o Control Mechanisms: Implement systems to detect and correct any
deviations from the plan.
o Regular Reviews: Periodic evaluations of progress, identifying issues and
risks early.
4. Controlling:
o Adjustments: When deviations from the plan occur, adjustments are made to
get back on track.
o Corrective Actions: If problems are found (e.g., delays, budget overrun),
corrective actions are taken.
o Feedback Loops: Continuous feedback helps in refining processes and
improving performance over time.
5. Decision-Making:
Software Project Management imp qustions

o Managers make informed decisions based on the monitoring and control data.
o They may adjust strategies, reallocate resources, or change goals to align with
new realities.
Example of the Framework in Action:
Imagine you are managing a construction project:
1. Planning: Set a goal to finish the building in 6 months and allocate resources like
labor, materials, and budget.
2. Organizing: Form teams for different tasks like design, procurement, and
construction, and delegate responsibilities.
3. Monitoring: Track construction progress using KPIs like completion percentage,
budget spending, and quality checks.
4. Controlling: If construction is delayed due to bad weather, adjust the timeline and
allocate extra resources to make up for lost time.
5. Decision-Making: If cost overruns occur, decide to source cheaper materials or
negotiate with suppliers for discounts.
Key Terms to Remember:
 Planning: Setting objectives and determining how to achieve them.
 Organizing: Structuring teams and resources.
 Monitoring: Tracking progress and performance.
 Controlling: Making adjustments when there are deviations from the plan.
 Decision-Making: Using data to make strategic choices.
Summary:
A Framework for Management and Control ensures that projects or organizations stay on
track by:
1. Planning effectively.
2. Organizing resources and teams.
3. Monitoring progress.
4. Controlling deviations and making adjustments.
5. Making informed decisions based on data.

2) Eanrned Value Analysis ?

Ans:
What is Earned Value Analysis (EVA)?
Software Project Management imp qustions

Earned Value Analysis is a project management technique used to assess a project’s

performance in terms of cost and schedule. It compares the planned progress with the actual
progress to help identify issues early and take corrective actions.
Key Concepts:
1. Planned Value (PV): The value of the work that was planned to be completed by a
certain time.
2. Earned Value (EV): The value of the work actually completed by a certain time,
based on the budgeted cost.
3. Actual Cost (AC): The actual costs incurred for the
4. work completed by that time.
Key Formulas:

o SPI > 1: The project is ahead of schedule (good performance).

o SPI < 1: The project is behind schedule (bad performance).
Steps to Use Earned Value Analysis:
1. Define the Baseline: Set the project plan, including the schedule and budget.
2. Measure Actual Progress: Track the work completed at different points in time.
3. Compare Planned and Earned Value: Use the formulas to compare the actual
progress (EV) against what was planned (PV).
4. Calculate Variances and Indices: Use CV, SV, CPI, and SPI to evaluate
performance.
Software Project Management imp qustions

5. Take Corrective Actions: If variances indicate problems, adjust the plan or allocate
more resources to get back on track.
Example:
Imagine a project with the following details at a given point:
 Planned Value (PV) = $100,000 (the value of work planned to be completed)
 Earned Value (EV) = $80,000 (the value of work actually completed)
 Actual Cost (AC) = $90,000 (the cost of work completed)
Now, calculate:
 Cost Variance (CV) = EV - AC = $80,000 - $90,000 = -$10,000 (over budget).
 Schedule Variance (SV) = EV - PV = $80,000 - $100,000 = -$20,000 (behind
schedule).
 CPI = EV / AC = $80,000 / $90,000 = 0.89 (inefficient, over budget).
 SPI = EV / PV = $80,000 / $100,000 = 0.8 (behind schedule).
Key Terms to Remember:
 Planned Value (PV): What was planned to be done.
 Earned Value (EV): What has actually been done.
 Actual Cost (AC): How much has actually been spent.
 Cost Variance (CV): Difference between earned value and actual cost.
 Schedule Variance (SV): Difference between earned value and planned value.
 CPI and SPI: Indices to measure cost and schedule performance.
Summary:
 Earned Value Analysis (EVA) helps track a project's cost and schedule performance.
 Use the PV, EV, and AC values to calculate variances and performance indices.
 Cost Variance (CV) and Schedule Variance (SV) help identify if a project is
ahead/behind schedule or under/over budget.
 CPI and SPI help assess efficiency in cost and scheduling.
3) Cost Monitoring
Ans:
What is Cost Monitoring?
Cost Monitoring is the process of tracking and controlling the costs of a project to ensure it
stays within the budget. It helps identify any cost overruns early and take corrective actions to
prevent financial issues.
Software Project Management imp qustions

Key Steps in Cost Monitoring:

1. Setting a Budget:
o Establish a baseline budget for the entire project, which includes all expected
costs (labor, materials, overhead, etc.).
2. Tracking Costs:
o Regularly record actual expenditures as the project progresses. This includes
the costs for tasks completed, materials used, labor hours worked, etc.
3. Comparison of Planned vs Actual Costs:
o Compare the actual costs (AC) to the planned costs (PV) to assess if the
project is staying within budget.
o If actual costs are higher than planned, investigate the reasons and take
corrective actions.

Key Terms to Remember:

 Budget: The planned cost for the entire project.
 Actual Cost (AC): The cost incurred to complete the work so far.
 Planned Value (PV): The cost planned for the work completed so far.
 Earned Value (EV): The value of work actually completed, in terms of the budget.
 Cost Variance (CV): The difference between EV and AC (to track budget
performance).
 Cost Performance Index (CPI): Measures cost efficiency. CPI=EVACCPI = \
frac{EV}{AC}CPI=ACEV
Software Project Management imp qustions

o CPI > 1: Under budget.

o CPI < 1: Over budget.
Example:
Imagine a project with the following details:
 Planned Value (PV) = $50,000 (planned cost for work completed)
 Actual Cost (AC) = $60,000 (actual cost spent)
 Earned Value (EV) = $55,000 (value of completed work)
Now, calculate:
 Cost Variance (CV) = EV - AC = $55,000 - $60,000 = -$5,000 (over budget).
 CPI = EV / AC = $55,000 / $60,000 = 0.92 (inefficient, over budget).
Summary:
 Cost Monitoring is about tracking and controlling project costs.
 Key actions: Set a budget, track actual costs, compare planned vs actual costs, and
calculate variances.
 Cost Variance (CV) and CPI are essential metrics for assessing budget performance.
 If the project is over budget, take corrective actions to control costs.

4) Change Contol Software Configuration Management ?

Ans:
Change Control is a process used in Software Configuration Management (SCM) to manage
and track changes to software, documents, and other project artifacts. It ensures that changes
are made in a controlled and systematic way, preventing errors and maintaining consistency
across the project.
Key Components of Change Control:
1. Change Request:
o Any modification to software, system configurations, or project
documentation must be initiated by a change request.
o The request describes the proposed change and why it is necessary.
2. Change Evaluation:
o After receiving a change request, the change is evaluated by a change control
board (CCB) or a relevant team.
o They assess the impact of the change on the project schedule, cost, and quality.
3. Approval/Denial:
Software Project Management imp qustions

o Based on the evaluation, the change request is either approved or denied.

o If approved, the change is planned, scheduled, and implemented.
4. Implementation:
o The change is made according to the approved plan. This includes modifying
code, documentation, or configurations.
o Changes are tracked to ensure they are correctly applied.
5. Testing and Validation:
o Once the change is implemented, it undergoes testing to verify that it
functions as intended and does not introduce new issues.
o Validation ensures the change aligns with the original requirements and
objectives.
6. Documentation:
o All changes, whether approved or denied, are documented to maintain a
version history and to ensure that the system remains traceable.
o This helps track what was changed, why, when, and by whom.
7. Release Control:
o Once changes are validated, they are included in the next release of the
software or system.
o This ensures that only stable and approved changes are part of the final
product.
Why is Change Control Important?
 Consistency: It ensures that all changes are made systematically and that everyone is
working with the most up-to-date version.
 Quality Assurance: It helps maintain the integrity of the software by ensuring that no
changes are made haphazardly.
 Traceability: It keeps a record of why, when, and how changes were made, which is
important for debugging, audits, and maintaining the software in the long term.
 Risk Management: Change control helps reduce the risk of introducing errors or
conflicts by properly reviewing and testing each change before it’s implemented.
Key Terms to Remember:
 Change Request: A formal request to modify the system, software, or documentation.
 Change Control Board (CCB): A group responsible for reviewing, approving, or
rejecting change requests.
Software Project Management imp qustions

 Version History: A log that tracks all changes made to the software or
documentation.
 Release Control: Managing when and how changes are deployed or released into the
system.
Example:
Suppose there is a bug in the software that affects performance. A change request is
submitted to fix the bug. The change control board evaluates the request and approves it.
The developers implement the change, and the updated software undergoes testing. After
passing the tests, the new version is documented and released, replacing the old version.
Summary:
 Change Control ensures that software changes are carefully reviewed, tracked, and
documented to maintain the system’s quality and integrity.
 The process involves requesting, evaluating, approving, and implementing
changes.
 Proper documentation and release control are essential to keep track of changes
over time and ensure consistency.
5) Contract Management ?
Ans:
Contract management is the process of creating, executing, and monitoring contracts between
parties to ensure compliance with the agreed terms. It involves several key stages:
1. Contract Creation: This involves drafting the contract with clear terms and
conditions that both parties agree to. It includes negotiation, defining deliverables,
timelines, and costs.
2. Contract Execution: This is the formal signing of the contract by the involved
parties. It marks the start of the agreement’s enforcement.
3. Performance Monitoring: Once the contract is in place, it is crucial to monitor the
performance of both parties. This includes tracking deadlines, milestones, quality, and
the fulfillment of obligations.
4. Amendments and Adjustments: During the contract period, unforeseen
circumstances may require amendments. These changes are negotiated and
documented as formal addendums or modifications to the contract.
5. Compliance: Ensuring that the parties involved comply with both legal and
regulatory requirements throughout the contract’s lifecycle. This is important to avoid
legal disputes and penalties.
6. Contract Closure: When all obligations are fulfilled, and the contract is complete,
the contract is formally closed. This step ensures that all deliverables have been met
and there are no further liabilities.
Software Project Management imp qustions

Objectives of Contract Management:

 Minimize risks and disputes.
 Ensure that both parties fulfill their obligations.
 Maintain compliance with legal and regulatory standards.
 Enhance operational efficiency and relationships between the contracting parties.
Effective contract management ensures that all terms are honored, helps resolve issues
efficiently, and provides a framework for dispute resolution when necessary.

Unit-5
1) Best Method Of Staff Selection?
Ans :
Staff selection is the process of hiring the right candidate for a job. The best method
combines various techniques to assess candidates thoroughly. Common steps in the selection
process include:
1. Job Analysis: Understand the job requirements, including skills, qualifications, and
responsibilities, to determine the ideal candidate profile.
2. Recruitment: Attract candidates through job advertisements, referrals, or recruitment
agencies. The broader the pool, the better the chances of finding the right person.
3. Screening of Applications: Review resumes and cover letters to shortlist candidates
who meet the basic qualifications and skills.
4. Interviews: Conduct structured or unstructured interviews to assess candidates'
suitability, skills, and cultural fit. Interviews can be one-on-one or panel-based.
5. Psychometric Testing: Use tests to evaluate a candidate's cognitive abilities,
personality, and behavior to ensure they fit the job requirements and company culture.
6. Assessment Centers: Involve group discussions, role-playing, and problem-solving
tasks to evaluate how candidates perform in real-world work situations.
7. Background and Reference Checks: Verify the candidate’s employment history,
qualifications, and character references to confirm the information provided.
8. Final Selection: Based on the evaluations, select the candidate who best fits the role.
The selected candidate is then offered the job.
Best Selection Method:
Software Project Management imp qustions

 Combining interviews, psychometric tests, and assessment centers gives the best
results.
 This ensures a well-rounded evaluation of the candidate's skills, personality, and
ability to perform in the role.

2) The Oldhem & Hachman Job Charactustiv?

Ans :
The Oldham & Hackman Job Characteristics Model identifies five key job characteristics that
affect employee motivation, satisfaction, and performance. These characteristics influence
how meaningful and satisfying a job is.
1. Skill Variety: The degree to which a job requires different skills and abilities. Jobs
with high skill variety are more engaging because they prevent monotony.
2. Task Identity: The extent to which a job involves completing a whole, identifiable
piece of work. When employees can see the outcome of their efforts, it increases their
sense of accomplishment.
3. Task Significance: The impact a job has on others, either inside or outside the
organization. Jobs with high task significance make employees feel that their work is
important and valued.
4. Autonomy: The degree of freedom, independence, and discretion an employee has in
planning and performing their work. Jobs with high autonomy give employees more
control over their tasks, which boosts motivation.
5. Feedback: The degree to which employees receive clear, direct information about
their performance. Regular feedback helps employees understand how well they’re
doing and where they can improve.
Application:
 When these five characteristics are present in a job, employees tend to be more
motivated, satisfied, and productive.
 The model suggests that job redesign can enhance these characteristics to improve
employee outcomes.
Software Project Management imp qustions

3) Health & Safety?

Ans:
Health and safety refer to the policies, procedures, and regulations designed to protect
employees' well-being and ensure a safe working environment. It aims to prevent accidents,
injuries, and illnesses at work.
Key Points of Health and Safety:
1. Risk Assessment: Identifying and assessing potential hazards in the workplace to
prevent accidents. This includes evaluating the likelihood of accidents and their
severity.
2. Workplace Safety Standards: Setting guidelines to ensure that workplaces are
physically safe. This includes proper lighting, ventilation, and equipment
maintenance.
3. Personal Protective Equipment (PPE): Providing employees with necessary gear
like helmets, gloves, goggles, etc., to protect against specific hazards.
4. Training and Awareness: Offering safety training to employees to ensure they
understand how to avoid risks and respond to emergencies, such as first aid or fire
drills.
5. Emergency Procedures: Having clear protocols in place for accidents, including
evacuation plans, first aid, and emergency contacts.
6. Health Promotion: Encouraging a healthy lifestyle, mental well-being, and
ergonomic work practices to reduce stress and prevent long-term health issues.
Legal Requirements: Employers must comply with local health and safety laws to avoid
fines and protect their workers' health.
Benefits:
 Reduces the risk of workplace accidents.
 Promotes employee well-being and productivity.
 Ensures compliance with legal and ethical standards.

4) Communication Plan & Leadership Plan?

Ans:
Communication Plan
A communication plan is a strategic document that outlines how information will be shared
within an organization or project. It ensures that the right messages reach the right people at
the right time.
Software Project Management imp qustions

Key Components:
1. Objectives: Define the goals of communication, such as informing, persuading, or
updating stakeholders.
2. Audience: Identify the target audience, including employees, clients, or stakeholders.
3. Key Messages: Specify the main points or information that need to be communicated.
4. Channels: Choose the communication methods (e.g., email, meetings, reports, social
media).
5. Frequency: Determine how often updates or communications will be sent.
6. Responsibility: Assign team members to manage communication tasks.
7. Feedback: Plan for receiving and responding to feedback from the audience.
A good communication plan ensures that everyone is aligned and informed, leading to better
coordination and decision-making.

Leadership
Leadership is the ability to guide, influence, and motivate a group of people to achieve
common goals. It involves setting a vision, making decisions, and inspiring others to follow.
Key Characteristics of Leadership:
1. Vision: A leader sets a clear direction and goals for the team.
2. Communication: Effective leaders communicate their vision, goals, and expectations
clearly.
3. Decision-Making: Leaders make informed decisions that guide the team toward
achieving its objectives.
4. Motivation: A good leader inspires and motivates others to give their best effort.
5. Adaptability: Effective leaders adjust their approach based on situations and
challenges.
6. Integrity: Leaders should be honest, ethical, and transparent in their actions.
Leadership Styles:
 Autocratic: Centralized decision-making with little input from others.
 Democratic: Encourages input from team members in decision-making.
 Transformational: Focuses on inspiring and motivating teams to achieve higher
levels of performance.
Software Project Management imp qustions