MANAV RACHNA UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE AND TECHNOLOGY

Software Project Management

Theory Assignment

B.Tech CSE AIML A

Semester: 7

SUBMITTED TO: SUBMITTED BY:

Prof. Agha Imran Shivangi Sharma
2K21CSUN04026
Q.1 Explain the key differences between a Software Project and other types of projects.
How does management control differ in software projects compared to construction
projects? Provide real-world examples to illustrate your answer.

Ans : Key differences between a Software Project and other types of projects are as
follows:

1. Deliverable Nature: Software projects yield non-physical outputs, such as

applications or software systems. In contrast, projects like construction produce
tangible results, such as buildings or infrastructure.
2. Adaptability and Change: Software projects are more adaptable, allowing
requirements to evolve over time. Construction projects are generally inflexible, with
limited room for changes once the work is underway. For example, implementing a
new feature in software is easier compared to altering the design of a building under
construction.
3. Risk Factors: Software development is susceptible to risks like technology becoming
outdated or integration challenges. Construction projects, however, are often
concerned with physical safety and environmental factors.

Project Management and Control:

 Software Projects: Use flexible, iterative methods, emphasizing constant updates,

adaptability, and efficient code management. For instance, managing an app
development project involves regular testing and user-driven iterations.
 Construction Projects: Rely on structured, sequential processes with a focus on
resource management, safety, and adherence to detailed blueprints. For example,
constructing a bridge requires meticulous planning and strict compliance with
engineering standards.

Overall, managing software projects emphasizes flexibility and responsiveness, while

construction projects focus on strict execution and adherence to pre-set plans.

Q2. You are tasked with developing a new e-commerce platform for a retail client. Based
on the stepwise project planning process, outline the steps you would take from selecting
the project to allocating resources. Identify at least two potential risks and how you
would mitigate them.

Ans, Here is Stepwise Project Planning for an E-commerce Platform:

1. Project Selection: Define the project scope and objectives, aligning with the
client’s business needs, such as a user-friendly interface and secure payment
system.
2. Requirement Analysis: Gather and document functional and non-functional
requirements, considering features like product catalogs, user authentication, and
order management.
3. Design and Prototyping: Create wireframes and a system architecture to
visualize user experience and back-end processes.
 4. Technology Selection: Choose the tech stack, such as the MERN stack, for
efficient development and scalability.
5. Development Planning: Break the project into sprints, assigning tasks to the
development team for front-end, back-end, and database integration.
6. Testing Strategy: Plan for unit testing, integration testing, and user acceptance
testing (UAT) to ensure quality.
7. Resource Allocation: Assign developers, designers, and QA specialists based on
project requirements and timelines.
8. Deployment and Maintenance: Establish a deployment plan, ensuring
continuous monitoring and regular updates.

Potential Risks and Mitigation

1. Scope Creep: Requirements may expand beyond the initial agreement. To mitigate,
implement strict change management and prioritize features with the client.
2. Security Vulnerabilities: Data breaches could impact customer trust. Use secure
coding practices, regular security audits, and data encryption to minimize risks.

Q.3 Consider a project to develop a mobile banking application. Identify three major
risks associated with the project and explain how you would apply qualitative risk
analysis (using tools like probability-impact matrices) to prioritize and address these
risks.

Ans, Here are the Major Risks in Mobile Banking Application Development:

1. Data Security Breach: A potential cyberattack or data leak could compromise

user information.
2. System Downtime: Unexpected outages or performance issues could hinder user
transactions.
3. Regulatory Compliance: Non-adherence to banking regulations could result in
fines and project delays.

Applying Qualitative Risk Analysis

1. Identify Risks: Document each risk and its potential impact on the project.
2. Probability-Impact Matrix: Evaluate the likelihood and impact of each risk on a
scale (e.g., high, medium, low). For instance, a data security breach may have a
high probability and high impact, making it a top priority.
3. Prioritization: Rank risks based on their severity to allocate resources effectively.
Address high-priority risks first with specific mitigation strategies, like
implementing advanced encryption for security or setting up load balancers for
system uptime.

Q.4 You are managing a software development team working on a new feature for a
large healthcare platform. One of your key developers is demotivated and missing
deadlines. As a project manager, how would you apply motivational theories and
leadership principles to improve team performance and meet project deadlines?

Ans: To address the developer’s demotivation, I would use motivational theories like
Maslow’s Hierarchy of Needs and Herzberg’s Two-Factor Theory. First, I would ensure
the developer’s basic needs, such as a balanced workload and supportive environment, are
met. Next, I would focus on intrinsic motivators like recognition, opportunities for skill
development, and meaningful work aligned with the healthcare platform’s impact on patient
care.

From a leadership perspective, I’d employ transformational leadership by communicating

the project’s vision and how the new feature contributes to improving lives. Additionally, I’d
practice active listening to understand any personal or work-related challenges and offer
support, like adjusting tasks or providing mentorship. By fostering a positive, purpose-driven
atmosphere, I’d aim to re-engage the developer and improve overall team performance to
meet deadlines.

Q.5 Discuss how Six Sigma and CMM (Capability Maturity Model) can be used to
enhance the quality of a software project. Compare the two methodologies in terms of
their approach to managing software quality.

Ans: Six Sigma and the Capability Maturity Model (CMM) are both used to improve
software quality but differ in their approaches. Six Sigma focuses on process improvement
by reducing defects and variability through data-driven techniques like DMAIC (Define,
Measure, Analyse, Improve, Control). It emphasizes continuous process refinement to
enhance performance and efficiency.

In contrast, CMM provides a framework for process maturity. It defines five maturity
levels: Initial, Repeatable, Defined, Managed, and Optimizing. CMM helps organizations
improve quality by standardizing and refining software development processes as they
advance through these levels, ensuring consistency and predictability.

While Six Sigma is results-oriented and quantitative, focusing on defect reduction, CMM
is process-oriented, emphasizing process evolution and maturity. Combining both can lead
to comprehensive quality management, where Six Sigma enhances efficiency and CMM
ensures process stability.

Q.6 A software development company has been delivering products with frequent
defects. As the project manager, propose a quality assurance plan to improve product
quality using tools like Pareto Analysis and ISO 9126. Explain how you would measure
success.

Ans: Here is Quality Assurance Plan to Improve Product Quality,

 1. Implement ISO 9126 Standards: Focus on key quality attributes like
functionality, reliability, usability, efficiency, maintainability, and portability.
Define specific metrics for each attribute to evaluate product quality.
2. Use Pareto Analysis: Identify and prioritize the most common causes of defects.
Focus on the top 20% of defect causes that contribute to 80% of the issues,
allowing targeted and effective quality improvements.
3. Continuous Testing and Review: Integrate regular code reviews, automated
testing, and user feedback loops into the development process to detect and fix
issues early.

Measuring Success

1. Reduction in Defects: Track the defect rate over time and aim for a significant
decrease in reported issues.
2. Customer Satisfaction: Collect user feedback and monitor satisfaction scores for
improvements.
3. Quality Metrics Compliance: Assess adherence to ISO 9126 standards, ensuring
the product meets defined quality benchmarks.

Q.7 A software project has an initial investment of INR150,000. The expected cash
inflows for the next three years are INR60,000, INR80,000, and INR100,000,
respectively. Using a discount rate of 10%, calculate the Net Present Value (NPV).
Should the project be accepted based on the NPV?

Ans: