Software Project Management

Q] What are the core components of the project management

framework?

Project management is about using knowledge, skills, tools, and

techniques to make sure a project meets its goals. Project managers
don’t just aim to finish on time, on budget, and within scope; they also
make sure everyone involved in the project is happy with the outcome.

1. Stakeholders
2. Knowledge Areas
3. Tools and Techniques
4. Project Success
Stakeholders :

Stakeholders are the people who are affected by the project.

Here are some examples of stakeholders :

 Project Sponsor: The people paying for the project.

 Project Manager: The person overseeing the entire project.
 Project Team: The workers involved in the project.
 Support Staff: People who support other stakeholders.
 Suppliers: People or companies providing materials.
 Opponents: People who might be against the project.

Project Management Knowledge Areas :

 Scope Management: Defines and manages what work is required.

 Time Management: Plans and tracks the project schedule.

 Cost Management: Prepares and tracks the project budget.
 Quality Management: Ensures the project meets quality standards.
 Human Resource Management: Organizes and manages the project
team.
 Communications Management: Manages how information is shared.
 Risk Management: Identifies and manages potential risks.
 Procurement Management: Manages buying goods/services for the
project.
 Stakeholder Management: Manages the needs and expectations of
stakeholders.
 Integration Management: Ties together all the other areas to ensure
smooth project execution.

Project Management Tools and Techniques :

Project managers use different tools to help them complete projects.

Some commonly used tools are:

 Gantt Charts: Used for scheduling tasks.
 Network Diagrams: Show how different tasks are connected.
 Critical Path Analysis: Helps find the shortest time to complete the
project.
Project Success :

A project is considered successful if it:

 Meets Scope, Time, and Cost Goals: Finishes the work on time,
within budget, and meets all requirements.
 Satisfies the Customer: The sponsor or customer is happy with the
results.
 Achieves the Main Objective: For example, the project makes or
saves money, or achieves some other major goal.

Q] What are the primary stages in a project life cycle

Concept Phase (Starting the Project) :

 This is where the idea for the project is born. It’s about figuring out
why we need the project and what it will achieve.
 A basic plan is made, including a rough estimate of how much it
might cost and what kind of work will be needed.
 This phase answers, “Does this project make sense?” If the answer is
yes, we move on.

Development Phase (Planning the Project) :

 Now that we know the project is a good idea, we start making

detailed plans.
 We create a clear roadmap with specific tasks, responsibilities, and a
better cost estimate.
 This phase is all about getting organized and preparing everything we
need to start the actual work.

Implementation Phase (Doing the Work) :

 This is where the real work happens. The team follows the plan to
create the project’s final product or service.
 Most of the project’s time and resources are spent here, and regular
updates are shared with everyone involved.
 If any issues come up, adjustments are made to keep the project on
track.
Close-out Phase (Finishing the Project) :

 Once all the work is done, it’s time to wrap up.

 The team ensures everything is complete, and the client or
stakeholders formally accept the final product.
 The team documents lessons learned, closes any contracts, and
makes sure everything is ready for future work.

Q] What is the role of project manager ?

A project manager (PM) plays a crucial role in leading projects to success.

They are responsible for making sure the project is completed on time,
within budget, and meets the required objectives. They do this by
working closely with different stakeholders, including the project team,
sponsors, and clients.

Project managers are expected to have a solid understanding of project

management knowledge areas (which are essential parts of managing a
project) and tools and techniques that help in managing projects.
Experience helps project managers lead better and solve problems more
effectively. Even if you never become a project manager, it’s still
important to understand their role, as you may work as part of a project
team.

Project Manager Job Description :

The job of a project manager can vary greatly depending on the industry,
organization, and type of project. Generally, project managers:

Plan and schedule tasks to meet project goals.

Coordinate and manage teams.
Build good relationships with clients and stakeholders.
Make sure the project stays on track, within budget, and on schedule.
Q] Explain Stakeholder Management.

In Software Project Management (SPM), stakeholder management is the

process of identifying, understanding, and managing the needs and
expectations of individuals or groups who are affected by or can impact
a software project.

Stakeholder Identification:

This is about identifying everyone who will be affected by the project.

Stakeholders include people who benefit from the project, such as
clients and end-users, as well as those involved in creating or managing
it, like the project team, management, and sometimes even regulatory
bodies. The aim is to make sure no one important is left out.

Stakeholder Analysis :

Once stakeholders are identified, it’s essential to understand what each

group or individual wants from the project and how much power they
have. Some stakeholders will be more influential or need more attention,
while others may be affected only indirectly. Knowing this helps in
prioritizing efforts and managing resources. For example, a client might
want specific features, while an investor is more focused on profitability.

Stakeholder Engagement :

Stakeholder engagement means keeping them connected to the project.

This could be through regular updates, status meetings, or gathering
their feedback at important stages. When stakeholders feel involved and
heard, they’re more likely to support the project and be satisfied with its
outcomes.

Communication Management :

Communication management involves creating a tailored plan for

keeping each stakeholder informed. This plan should specify how often
to reach out, through which channels (email, meetings, reports), and
what information to provide. For example, the project team may need
detailed technical updates, while high-level reports might suffice for
upper management.

Expectation Management :

This is about setting realistic goals and making sure stakeholders know
what the project can and can’t achieve. By aligning their expectations
with the project’s capabilities and timelines, you reduce the risk of
disappointment and conflict. This might involve negotiating with
stakeholders to adjust their expectations if needed, especially when
resources are limited or if project scope changes.

Conflict Resolution :

Inevitably, there may be conflicts or concerns that arise during the

project. Maybe two stakeholders want different things, or a client
requests a new feature that’s challenging to implement. Conflict
resolution means finding a balance and addressing issues early to avoid
derailing the project. Good problem-solving often involves open
dialogue, compromise, and transparency.

Q] What is leadership ? Explain different types of leadership

What is Leadership in Projects?

Leadership is about guiding a team to achieve the project's goals.
Good leaders motivate their team, make decisions, and solve challenges
effectively.

Types of Leadership Styles:

1. Servant Leadership :
 Focus on team growth and success.
 Encourages teamwork and values everyone’s ideas.
 Supports the team

2. Transformational Leadership :
 Motivates the team with clear goals.
 Encourages creativity and new ideas.
 Focuses on improving both the team and individual members.
3. Democratic Leadership :
 Decisions are made with team input.
 Promotes teamwork and open communication.
 Builds trust and gives the team a sense of responsibility.

4. Autocratic Leadership :
 Decisions are made by the leader without team input.
 Very direct and authoritative.
 Little to no collaboration with the team.

5. Situational Leadership :
 Flexible and adapts to the situation.
 Understands the team’s strengths and weaknesses.
 Matches the leadership style to the task or team capability.

6. Laissez-Faire Leadership :
 Leader gives freedom and trusts the team.
 Team members are fully responsible for decisions and results.
 Minimal guidance is provided by the leader.
 Best for skilled, experienced, and self-motivated teams.
Module 2

Q] Explain waterfall model.

The Waterfall Model is one of the oldest and most traditional ways to
develop software.
It works in a linear and step-by-step process, meaning one phase must
finish completely before moving to the next.

Key Features:
 Sequential Process
 Fixed Requirements
Q] Explain Incremental Model.

The Incremental Model is a type of software development process in

which the software is built and delivered in small, manageable parts
called "increments." Each increment adds some functionality to the
software until the entire system is complete. It’s an approach that allows
the development team to gradually build the software, testing and
refining each part as it’s developed.

Key Features of the Incremental Model :

 Step-by-Step Development: The system is developed in small

sections, or increments, each of which adds a specific set of
functions. Instead of building the entire system all at once, it’s
broken down into smaller pieces that can be built and tested
individually.
 User Feedback: After each increment is completed, it’s released for
testing or use. This allows users to give feedback early and often,
which can help guide further development and make sure the
project meets their needs.
 Flexibility: Developers can adapt and make changes to the software
in later increments based on user feedback from earlier increments.
This flexibility is especially useful for projects where requirements
may change or evolve.

How the Incremental Model Works :

 Requirements Gathering and Analysis :

At the beginning of the project, the team identifies all requirements for
the software. This might not be as detailed as in some other models,
since requirements can be refined and adjusted with each increment.

 Design Phase :
The overall design of the system is created, and then a more detailed
design is developed for the first increment.

 Implementation (Coding) and Testing :

The first increment is developed based on the initial set of requirements.
After coding, the increment is tested to make sure it meets
requirements and works as expected.
Any bugs or issues found during testing are fixed.

After passing testing, the increment is delivered for use or further

evaluation.

 Integration and Delivery:

Each subsequent increment is integrated with the previous increments.
Each new increment builds on the functionality of the last, gradually
adding new features and capabilities.
Repeat Steps for Each Increment: Steps 2-4 are repeated for each
increment until all parts of the system are complete.

Advantages of the Incremental Model :

 Early Partial Working Software:

Users can start using some parts of the software before the entire
system is completed. This allows for quicker feedback and early
detection of any potential issues.

 Flexibility for Changes:

Changes can be made after an increment is released, making it easier to
adapt to new requirements or improvements as the project progresses.

 Easier Testing and Debugging:

Each increment is a manageable part of the overall system, which makes
testing and debugging simpler since only a small portion is tested at each
stage.

 Risk Management:
High-risk elements can be handled early in the project. If a certain
feature is complex or uncertain, it can be prioritized in early increments,
allowing the team to assess feasibility sooner.
Disadvantages of the Incremental Model :

 Requires Good Planning:

Since each increment builds on the previous one, the overall design
needs to be well thought out from the beginning.

 Higher Initial Costs:

Compared to simpler models like the Waterfall Model, the Incremental
Model may have higher initial costs because it requires careful planning
and regular testing at each increment.

 Resource Intensive:
Incremental development can require more resources for regular testing,
feedback handling, and integration.

Q] Explain prototype model.

This model is used when a customer has a general idea of what they
want but can’t provide detailed requirements.
Developers build a quick prototype (a rough version of the software) to
show how it might work.
It helps customers visualize the software and give feedback before
finalizing the product.

Key Features:
User Involvement: Customers are heavily involved in providing feedback.
Multiple Iterations: The prototype is modified and improved in cycles
until it meets the customer’s needs.
Flexible: Changes are easily made based on feedback.

Phases in Prototype model :

Requirement Gathering and Analysis:

Developers talk to the customer to understand general goals and broad
needs.
Quick Design:
A simple and rough design of the system is created, focusing on
important parts the customer wants to see.

Build Prototype:
Using the quick design, a basic and incomplete version of the software is
developed.

User Evaluation:
The prototype is shared with the customer, and they provide feedback
about its functionality and design.

Refinement of Prototype:
Based on customer feedback, the prototype is improved or modified.
This cycle of feedback and improvement continues until the prototype
meets expectations.

Final Product Development:

When the prototype is perfect, the final product is build based on the
final prototype.

Q] How would you apply the Spiral Model to a project with

high risks and evolving requirements? Describe how each
phase would address the risks and uncertainties.
OR
Q] Explain Spiral Model.

The Spiral Model is ideal for high-risk projects with evolving

requirements because it combines iterative development with
systematic risk assessment at every phase. In each spiral, the model
addresses uncertainties and risks, allowing the project team to make
informed decisions as they progress.
Phases of Spiral Model :

1. Identify Objectives and Requirements :

 In the first step of each cycle, the team works closely with
stakeholders (like clients or users) to understand and list the goals
and requirements for that part of the project.
 Because requirements may change, the team focuses on what’s most
important and up-to-date right now.
 They also take a first look at any possible risks, like technical issues or
unexpected costs, and plan ways to manage them in this cycle.
 Key result: A clear list of prioritized goals and requirements for the
current cycle.

2. Risk Analysis and Prototyping :

 Next, the team takes a closer look at potential risks and comes up
with ways to reduce them.
 For example, if they’re using a new technology, they might create a
small prototype or a test version to see if it works.
 If requirements are unclear, they can also build a simple prototype to
get feedback from stakeholders and make sure they’re on the right
track.
 Prototypes and test versions are very useful here because they help
the team explore ideas, find issues early, and gather insights without
a big commitment.
 Key result: A document listing risks, any updates to requirements,
and sometimes a prototype for testing ideas.

3. Development and Testing :

 Now, the team builds and tests the features or parts of the project
that were prioritized for this cycle. The goal is to focus on the core
functionality or the minimum viable product (MVP) for this stage.
 Testing is included throughout development to make sure everything
works as expected and meets the quality standards.
 By developing in small pieces, the team can quickly spot any issues
and keep improving the project little by little.
 Key result: A working version of part of the system, with some tested
features and components.
4. Customer Evaluation and Planning for the Next Spiral :

 At the end of each cycle, stakeholders review what’s been done, give
feedback, and share any new needs or changes.
 This feedback is crucial because it helps the team update their
understanding of the project’s direction and goals.
 Based on this feedback, the team plans the next cycle with any new
requirements or adjusted goals.

Q] What is Agile development ?

Agile development is a flexible and collaborative way to create software.

It focuses on delivering small, usable parts of the product quickly,
instead of waiting to complete everything all at once. Teams work
closely with customers and adapt to changes as the project evolves.
Key Features of Agile Development:

Iterative and Incremental:

Work is done in small pieces called "iterations" or "sprints" (usually 1–4
weeks long).
Each iteration delivers a working part of the product.

Customer Collaboration:
Customers or users are involved throughout the project, providing
feedback regularly.

Flexibility to Change:
Changes in requirements are welcomed, even late in the process, to
ensure the product matches customer needs.

Continuous Improvement:
After each iteration, the team reviews what went well and what didn’t
to improve for the next sprint.

Teamwork and Communication:

Teams work closely together and hold daily meetings (called stand-ups)
to discuss progress and challenges.

Focus on Value:
The priority is to deliver features that are most valuable to the customer
first.
Q] Explain Extreme programming

-XP is the type of agile developement.

-XP approach is used where the changing rate of requirement is high

XP values :

1] Communication and feedback:

-There must be active communication with the client
-It is important to get Client's feedback on what you have built to check
whatever you have built is meeting the clients requirements or not.

2] Simplicity:
-Make the design simple for less complexity

3] Responsibility:
-Developers are the one who are responsible for the quality of the
software

4] Courage:
-If something unexpected happen then the programmer must have
courage to start from the beginning with new and different ideas.

XP practices :

1] Planning process
-Planning process means deciding how you are going to build the project
with your team

2] Small releases
-Means instead of waiting a long time to show the client what you have
build, you share smaller working parts of it more often.
-So that if the new requirements are there then it becomes easy to add
those as early as possible

3] Metaphor
-User can't understand the language of programmer so to explain them
the concept of project, Using simple statements and giving real life
examples so that the user can relate it quickly
4] Simple Design
-Making design of the project simple so that it will not cause any
complexity in the project

5] Testing
-It's like checking your work to make sure that it is right.

6] Refactoring
-It means cleaning and organizing your code to make it neater to work
with, without changing how it functions.

7] Pair programming
-Pair programming is like having a code buddy
-Two programmers work together with one person typing and the other
person is watching and suggesting ideas.
-This way it becomes easy to catch errors and share knowledge and
come up with better solutions together.

8] Collective owenership
-It means having mindset of 'Every team member is responsible for the
code and not a single person'.

9] Continuous Integration
-In XP we build modules saperately and check if it is working or not.
-But there might be dependancies in the modules and will be unable to
find it out if the moduless are working together correctly or not.
-For this, Continuous integration is essential.

10] 40-Hour week

-it means the developement team works regular which is typically 40
hours per week.
-This practice ensures that the team members have healthy work-life
and don't overwork themselves.
-This is for maintaining the mental health of the team members.

11] On site customer

-It is important to have a person in company who is continuously in
touch with the user and the programmer so that he can give the updates
to the user.
12] Coding standard
-Setting rules and standards that everyone on the developement team
must follow when writting the code.

Q] Demonstrate working of SCRUM development model with

respect to roles involved in it, events and artifacts.

-Scrum is one of the agile development models.

-In Scrum model, a project is divided into small modules.
-Each modules are incrementally developed and delivered over time
boxes that are called sprints.
-Each sprint is typically 2 to 4 weeks long.
-At the end of each sprint, the stakeholders and the team members
arranges a meeting where they discuss about the development of the
software.
-The stakeholders may suggest any changes and improvements to the
developed software.
-The software therefore gets developed over a series sprints.
-After completion of a sprint, it is deployed at the client site and the
client feedback is obtained after each sprints.

Key Roles :

 Product owner :
-The product owner represents customers perspective and guides the
team towards building the right software.
-In various meetings the product owner portray the customers view in
front of the developement team.

 Scrum master :
-Scrume master acts as a project manager for the project.
-The responsibilities of the scrum master includes guiding team towards
the succesfull project implimentation.
-Scrum master ensures that the developement team is fully productive

 Team member
-A scrum team is consist of different kinds of team members.
-It is necessary to have peoples with different mindset in a team.
-So that the new ideas gets inovate constantly.
Artifacts
-There are three important artifacts is scrum methodology:

1] Product backlog :
-The document list where all the project requirements, features are
noted together.
-In this document the features or requirements are written in the form
of user stories.
-As time passes new features got added as well as some features get
removed.
-This document is therefore dynamic document.
-For sprint, features from this backlog are chosen for developement.

2] Sprint backlog :
-During sprint planning meating, the team selects one or more features
from product backlog and decides to work on that perticulat module.
-Now these selected features gets removed from the product backlog
and gets added to sprint backlog.

3] Sprint burndown chart :

-A sprint burndown chart helps the team to track their progress in
completing tasks during sprint.
-It is a visualisation tool to show if you're getting closer to your
destination on sheduled time or not.

Scrum Events

1] Sprint planning :
-While sprint planning the whole team comes together.
-They decide what they want to achieve.
-They figure out how to reach thoes goals.
-They got assigned with the task they can finish and the whole team
start working on a project.

2] Daily scrum :
-Daily scrum is reffered to as a 'Stand up meeting'.
-Team members attend this meeting while standing hence called as
stand up meeting.
-Team discuss what they had done yestarday and what is their todays
goal and what are the obstacles they might face while working.
-This meeting is held for just 10-15 minutes.

3] Sprint review meeting :

-At the end of each sprint, a sprint review meeting is conducted.
-In this meeting, the team demonstrate the functionality of the
completed module in front of all the stakeholders.
-Feedback is collected from the stakeholders in this meeting and then
working of next sprint starts.
Module 3

Q] Explain requirement engineering process

Requirements engineering is the process of understanding, defining, and

documenting what a software system should do. It is the first and most
important step in creating high-quality software. If the requirements are
not clear, the developers won't know what to build, and customers
won't know what to expect.

Steps in Requirements Engineering:

Requirements Elicitation (Gathering Information):
This step is about collecting requirements from the customer and other
stakeholders.

Requirements Analysis (Refining Information):

Once the requirements are gathered, they are analyzed to:
Find and fix any errors, conflicts, or missing details.
Make sure all requirements are clear and not contradictory.

Requirements Documentation (Writing it Down):

After gathering and analyzing, the requirements are written down in a
formal document called the Software Requirements Specification (SRS).

Requirements Review (Checking for Accuracy):

Once the SRS is ready, it is reviewed and verified to make sure:
It accurately reflects what the customer wants.
It doesn’t have any mistakes or missing details.

Q] Explain Functional and Non- Functional Requirements

In Software Project Management (SPM), functional and non-functional

requirements describe different aspects of what the software should do
and how it should perform. Both types are crucial to ensuring the project
meets the needs of users and stakeholders.
Functional Requirements :

These describe what the software should do—the specific functions,

tasks, or behaviors it must perform to achieve its purpose. They are
typically features or services that the software should provide to meet
the user’s needs.

Examples of functional requirements include:

 User Authentication:
The system should allow users to log in with a username and password.

 Order Processing:
The software should enable users to add items to a shopping cart,
checkout, and process payments.

 Data Entry and Storage:

The application should allow users to enter and save personal
information.

 Report Generation:
The system should generate monthly sales reports and display them in a
dashboard.

Non-Functional Requirements :

These describe how the software should perform rather than what it
should do. Non-functional requirements specify quality attributes,
performance criteria, and constraints that define the system’s operation
and usability. They’re essential for ensuring the software meets the
required standards and can operate in the intended environment.

Examples of non-functional requirements include:

 Performance:
The system should respond to user actions within 2 seconds.

 Scalability:
The software should handle up to 1,000 simultaneous users without
performance degradation.
 Security:
User data should be encrypted, and the system should be protected
against unauthorized access.

 Usability:
The application should be intuitive for new users and provide help
documentation.

 Reliability:
The software should have an uptime of 99.9% and recover from crashes
within 5 minutes.

 Maintainability:
The codebase should be modular, making it easy for developers to fix
bugs or add new features.

Q] Explain Requirement Elicitation Technique: Interview.

Requirement elicitation is the process of gathering requirements from

stakeholders to understand what they need from a software system.
One of the most commonly used techniques for requirement elicitation
is Interviews. Interviews involve direct communication with stakeholders
to uncover detailed information about their needs, goals, and
expectations for the system.

Overview of the Interview Technique :

 In an interview, the requirements analyst (or business analyst) asks

stakeholders a series of questions to gather information. This is often
done one-on-one but can also involve small groups.

 Interviews can vary in structure:

Structured Interviews :
Follow a predefined set of questions, often in a specific order. They’re
more formal and can be useful when you need consistent data across
multiple stakeholders.
Unstructured Interviews :
More flexible and conversational. These interviews do not follow a set
list of questions, allowing the interviewer to explore topics based on the
stakeholder's responses.

Semi-Structured Interviews :
Combine elements of both structured and unstructured interviews,
allowing the interviewer to follow a set of questions but with flexibility
to explore new areas of interest as they arise.

Types of Questions Used in Interviews :

 Open-Ended Questions:
These encourage detailed responses and are useful for gathering broad
information. For example, "Can you describe how you currently perform
this task?"

 Closed-Ended Questions:
These require short, specific answers and are useful for gathering factual
information. For example, "How many users are involved in this
process?"

Advantages of Using Interviews :

 In-Depth Information:
Interviews allow for detailed discussions, which can uncover complex or
nuanced requirements.

 Personal Interaction:
Face-to-face or live interviews build rapport and can make stakeholders
feel more comfortable, leading to more open sharing of information.

 Clarification Opportunity:
The interviewer can immediately clarify any ambiguous responses,
ensuring more accurate understanding.
 Flexibility:
Interviews can adapt to each stakeholder’s knowledge level and area of
expertise, allowing the interviewer to focus on relevant areas.

Disadvantages of Using Interviews :

 Time-Consuming:
Conducting and analyzing interviews takes significant time, especially if
there are many stakeholders involved.

 Potential Bias:
Interviewers may unconsciously influence responses, and interviewees
may focus on personal concerns rather than overall system needs.

 Limited Reach:
Interviews typically involve fewer participants than surveys or
questionnaires, so some requirements may be missed if the right
stakeholders are not interviewed.

 Dependence on Communication Skills:

Effective interviews rely heavily on the interviewer’s skills in questioning
and listening, as well as the interviewee’s ability to articulate their needs.

Q] Explain Requirement Elicitation Technique: Brainstorming.

Brainstorming is a group activity used to gather ideas during the

planning phase of a project. The goal is to come up with as many ideas
as possible, no matter how silly they may seem. This process helps the
team start with a lot of ideas to work from, rather than having nothing
at all.

Brainstorming helps create a list of ideas or requirements that can help

in finding a solution. Having many ideas gives a stronger starting point
than starting from scratch. After generating the ideas, the team can
review and sort them to find the most useful ones for the project.
How Does Brainstorming Work?

 It encourages creativity and idea-sharing.

 It’s a way for everyone to express their thoughts and any concerns
they may have.
 People are told to share whatever ideas come to mind, even if they
seem irrelevant or unusual.
 No one is criticized for their ideas, even if they seem silly.

How to Do Brainstorming:

 Share All Ideas: No idea is too weird. Even strange ideas can lead to
useful ones.
 Avoid Criticism: Everyone should feel safe to share their thoughts
without fear of judgment.
 Build on Each Other’s Ideas: Sometimes one idea leads to a better
idea when combined with someone else’s input.

Q] Write short note on Software Requirement Specification

 Requirements Documentation is a critical step after gathering and

analyzing the requirements for a project. It involves writing down all
the requirements in a clear and organized way.
 The document used for this is called the Software Requirements
Specification (SRS). The SRS is a detailed document that describes
what the software needs to do and how it should behave.

What is an SRS?

The SRS is a detailed description of the software that includes:

Functional Requirements: What the software should do.
Non-Functional Requirements: How the software should perform (like
speed, security, etc.).

Purpose of Requirement Documentation:

For Customers: It defines the needs and expectations of the users.
For Developers: It acts as a contract between the customer and the
developer, making sure everyone understands what the system should
do. This helps prevent misunderstandings and ensures the final product
meets the customer's expectations.

Q] Write a short note on business case

 A business case is essential for justifying the need for a particular

project.
 It identifies different aspects and argues why the project would be
beneficial and the risks and costs involved.
 Business case is a document or presentation that tells the people in
charge why its good idea to start that perticular project.
 It presents a current business problems and suggests ways to solve it.
 Feasibility study can also acts as a business case.
 It provides justification for startig a project.
 Business case includes the total cost,investment,time required to
develope a project as well as the return of investment.
 The main purpose is to convience stakeholders that the project is
worth the investment.

Components of business case :

Executive summary :
-Gives quick idea of your project to the stakeholders.

Project Defination :
-Provides general information about your project such as planning.

Project Schedule :
-Making shedule to complete each module of the project.

Project Budget :
-Required investment to complete the project in specified time.
Q] Consider a project with the following functional units:
Number of user inputs = 50
Number of user outputs = 40
Number of user enquiries = 35
Number of user files = 06
Number of external interfaces = 04

Assume all complexity adjustment factors and weighting factors are

average.
Compute the function points for the project.
Some Important formulas :

Q] Write a short note on work breakdown structure

A Work Breakdown Structure (WBS) is a way to break down a big project

into smaller, manageable tasks.

Purpose: WBS helps in organizing the work required to finish a project by

dividing it into smaller tasks and activities. It makes the project clearer
and easier to manage.

Representation: It is usually shown as a tree structure :

 The root of the tree is the main project or problem.
 The branches represent bigger tasks.
 The leaf nodes are the smallest tasks, usually taking no more than
two weeks to finish.
 Each task should ideally take about 1-2 weeks to complete.

Q] Consider the following activity, duration and dependencies:

Calculate 1] Critical path

2] ES and EF
3] LS and LF
4] Slack Time (ST)
Q] Write a short note on project procurement management

Procurement management is the process of getting the things you need

for a project or business by purchasing them from outside suppliers. This
includes buying products, services, or resources from vendors.

Here are the main steps involved:

Planning: Figuring out what you need to buy and when.

Choosing Suppliers: Finding and selecting the right people or companies
to buy from, based on things like price, quality, and reliability.

Making Agreements: Setting up contracts with suppliers to agree on

things like price, delivery time, and quality.

Managing Purchases: Making sure that what you ordered is delivered on

time, at the right price, and meets the requirements.

Finalizing: Wrapping up the purchase process, making final payments,

and making sure everything is complete.

Q] Write a short note on ISO 9000.

ISO 9001 is a set of guidelines created by the International Organization

for Standardization (ISO), which helps companies maintain high quality
in their products and services. These guidelines focus on how companies
should manage their operations, not just the products they make.

What is ISO 9000?

ISO 9000 is a group of standards created to ensure companies follow a
good process to make quality products. The goal is to help businesses
maintain consistent quality in their work.

Types of ISO 9000 Standards:

ISO 9001: This is for companies that design, develop, produce, and
maintain products. Software companies usually follow this standard.
ISO 9002: This applies to companies that only manufacture products, not
design them, like factories making things from someone else's designs.

ISO 9003: This is for companies that just install and test products,
without making or designing them.

Why Should Software Companies Get ISO 9000 Certification?

Customer Trust: ISO 9000 shows customers (especially in other countries)

that the company follows good quality practices. Some contracts require
ISO certification to ensure quality.

Better Quality: By following ISO 9000, companies ensure their software

is made with a clear process, leading to higher quality and consistency.

Efficiency: It helps companies work faster and cheaper by reducing

waste and improving their development process.

Q] Write short note on SEI capability maturity model

The SEI Capability Maturity Model (CMM) helps companies improve how
they create software. It shows them how to improve their work
processes, so they can make better software in a faster and cheaper way.

SEI CMM’s Five Levels:

Level 1: Initial (Chaotic) :

What it means: There are no set rules or processes for making software.
Each person does things their own way, and it's all very messy.
Problems:
The quality of the software is bad because people rush and make
shortcuts.
When key people leave, the work gets disrupted.
Level 2: Repeatable :

What it means: The company starts using basic rules to track things like
costs and time.
Benefits:
The company gets better at doing things the same way on similar
projects.

Level 3: Defined :

What it means: The company now has written rules and guidelines that
everyone follows.
Problems: There's no focus on checking how good the work or product is.
Similar to: This level is close to the ISO 9000 standard.

Level 4: Managed :

What it means: The company uses numbers and data to see how good
their software is and how well the process is going.
Benefits:
You can set goals for quality and meet them using data.
Data helps track progress, but the company still isn’t improving things
yet.

Level 5: Optimizing :

What it means: The company keeps improving by using the data they
collect. They find ways to get better and share ideas with everyone.
Benefits:
Processes become faster and more adaptable to changes.
The company uses what they’ve learned to keep improving.
Q] Write short note on project risk management

Project Risk Management is all about finding potential problems or

chances that could affect the project's success. It helps teams plan for
risks, so the project can meet its goals.

What is a Project Risk?

A project risk is anything uncertain that could either help or hurt the
project.

There are two main parts to risks:

 Uncertainty: We don’t always know if a risk will happen.
 Loss: If the risk happens, it could cause problems like delays or extra
costs.

Types of Risks in Projects:

 Project Risks: These affect how the project is planned and can cause
delays or cost increases.
Example: A project with unclear goals might lead to missed deadlines or
higher costs.

 Technical Risks: These are risks that happen when the software being
built has technical problems, like issues with design or testing.
Example: Using a new technology might cause unexpected problems.

 Business Risks: These affect how well the project fits into the
company's goals.
Example: A product might fail if it doesn't meet customer needs.

 Positive Risks (Opportunities):

Sometimes risks can lead to good results, like finding new opportunities.
It's important to balance both risks and rewards.

Risk Appetite and Risk Tolerance:

 Risk Appetite: How much risk a company is willing to take to get a
reward.
Example: A company might take risks with new technology to get an
advantage in the market.
 Risk Tolerance: The amount of risk the company is willing to accept.
Example: A company might accept minor quality issues to launch a
product earlier.

Six Steps for Managing Project Risk:

 Create a Risk Plan: Decide how to deal with risks and make sure
everyone supports the plan.
 Identify Risks: Look for possible risks by brainstorming, asking
experts, or using checklists.
 Analyze Risks: Figure out how likely the risks are and how much they
could affect the project. Prioritize them.
 Develop Risk Strategies: Plan ways to reduce, avoid, or take
advantage of the risks.
 Monitor and Control Risks: Keep track of the risks throughout the
project to make sure they’re being managed.
 Respond and Evaluate Risk: When risks happen, act quickly and
check how well your plans worked.