Project Mgmt & Quality: Plans, Metrics, Risks & Standards

TAKEAWAYS:

• Project management uses frameworks like Waterfall (sequential) and Agile (iterative) to plan, execute, and deliver software projects efficiently.
• Quality management relies on standards (ISO 25010) and models (CMMI) to ensure software meets functional and non-functional requirements.
• Risk management identifies, analyzes, and mitigates risks (technical, schedule, budget) using techniques like SWOT and risk matrices.
• Cost and schedule estimation uses methods like COCOMO and PERT to predict project timelines and budgets accurately.
• Quality assurance (QA) involves reviews, testing, and metrics (defect density, cyclomatic complexity) to maintain software reliability.
• Tools and techniques (e.g., Gantt charts, Kanban boards, defect tracking) help track progress and ensure quality in real-world projects.

1. Software Project Management

Software project management (SPM) is the application of knowledge, skills, tools, and techniques to plan, execute, and deliver software projects within constraints like time, cost, and quality. It ensures projects are completed successfully while meeting stakeholder expectations.

1.1 Project Management Frameworks

Different frameworks guide how projects are structured and executed. The two most common are:

1.2 Work Breakdown Structure (WBS)

A WBS breaks down a project into smaller, manageable tasks. It helps in:

• Estimating time and cost.
• Assigning responsibilities.
• Tracking progress.

Example (Nepali Context): Suppose Nepal Electricity Authority (NEA) is developing a new billing system. The WBS might look like this:

1.3 Gantt Charts and Critical Path Method (CPM)

• Gantt Charts: Visualize project timelines, dependencies, and progress.
• CPM: Identifies the longest path of tasks (critical path) to determine project duration.

Example (Pathao Driver App): Pathao’s app development might have dependencies like:

1. User authentication → 2. Ride booking → 3. Payment integration → 4. Driver matching. If payment integration is delayed, the entire project timeline shifts.

gantt
    title Pathao App Development Timeline
    dateFormat  YYYY-MM
    section Planning
    Requirements Gathering :a1, 2023-01-01, 2023-01-15
    section Design
    UI/UX Design :design, after a1, 30d
    Database Schema :db, after a1, 20d
    section Development
    Frontend :frontend, after design, 45d
    Backend :backend, after db, 60d
    API Integration :api, after frontend, 20d
    section Testing
    QA Testing :qa, after api, 30d
    section Deployment
    Launch :launch, after qa, 10d

2. Software Quality Management

Quality management ensures software meets functional (what it does) and non-functional (performance, security, usability) requirements.

2.1 Quality Models

Example (Khalti Payment System): Khalti must ensure:

• Functional Quality: Correct transaction processing.
• Non-Functional Quality: Fast response time (<2s), 99.9% uptime, secure encryption (PCI-DSS compliance).

2.2 Quality Assurance (QA) Techniques

Example (Daraz Order Fulfillment System):

• Static Testing: Check if the order processing logic handles edge cases (e.g., out-of-stock items).
• Dynamic Testing: Simulate 10,000 concurrent users to test scalability.

2.3 Quality Metrics

Example (Ncell App): If the Ncell app has 50 defects in 10,000 lines of code, the defect density is: $$\text{Defect Density}=\frac{50}{10,000}=0.005\text{ defects/LOC}$$ (Acceptable range: <0.01 defects/LOC).

3. Risk Management in Software Projects

Risk management identifies potential issues and plans responses to minimize their impact.

3.1 Risk Identification and Analysis

3.2 Risk Matrix

A risk matrix prioritizes risks based on probability and impact.

Example (eSewa Project):

• Risk: Cyberattack on payment gateway (High probability, High impact) → Mitigation: Implement DDoS protection and regular audits.

3.3 SWOT Analysis for Projects

4. Cost and Schedule Estimation

Accurate estimation ensures projects stay on budget and timeline.

4.1 Estimation Techniques

Example (Bank Loan Processing System): Using COCOMO: $$\text{Effort (person-months)}=3.2\times (\text{KLOC}{)}^{1.05}$$ For 5 KLOC: $$3.2\times 5^{1.05}\approx 18\text{ person-months}$$ (Assuming 3 developers: 18/3 = 6 months.)

4.2 PERT Example (Ncell App Update)

5. Tools for Project and Quality Management

In the Real World

1. Khalti (Digital Payments)

   • Quality Management: Uses ISO 25010 for security (encryption, PCI-DSS compliance) and CMMI Level 3 for process maturity.
   • Risk Management: Mitigates fraud risks via two-factor authentication (2FA) and real-time transaction monitoring.
   • Project Management: Hybrid model (Agile for app development, Waterfall for compliance documentation).

2. Pathao (Ride-Hailing App)

   • Cost Estimation: Used COCOMO to estimate the backend system (15 KLOC → ~25 person-months).
   • Quality Assurance: Static testing (SonarQube) to reduce defects before release.
   • Risk Management: SWOT analysis identified "driver shortages" as a threat → solution: referral bonuses.

3. Nepal Electricity Authority (NEA) Billing System

   • Project Management: Waterfall model (due to strict regulatory requirements).
   • Schedule Estimation: PERT used to account for delays in government approvals.
   • Quality Metrics: Defect density tracked to ensure <0.01 defects/LOC.

Exam Tip

1. Project Management (30% weight)

   • Know the differences between Waterfall, Agile, and Hybrid (when to use each).
   • Be able to draw a Gantt chart and identify the critical path.
   • Worked Example: Given a scenario (e.g., "Ncell wants to update its app"), explain which framework to use and why.

2. Quality Management (25% weight)

   • ISO 25010 vs. CMMI: Define key terms (e.g., "reliability," "process maturity").
   • Quality Metrics: Calculate defect density and cyclomatic complexity.
   • QA Techniques: Differentiate between static and dynamic testing.

3. Risk and Cost Estimation (20% weight)

   • Risk Matrix: Given a scenario, classify risks and suggest mitigations.
   • COCOMO/PERT: Solve numerical problems (e.g., "Estimate effort for a 10 KLOC project").
   • SWOT Analysis: Apply to a real Nepali project (e.g., eSewa, Daraz).

4. Tools and Standards (15% weight)

   • Name 2 tools for each category (project management, QA, defect tracking).
   • Explain how ISO 25010 applies to a given system (e.g., Khalti’s security).

5. Case Study (10% weight)

   • Expect a real-world scenario (e.g., "NTC is deploying fiber in Kathmandu"). Answer should include:
     • Framework choice (Agile/Waterfall/Hybrid).
     • Risk analysis (top 3 risks + mitigations).
     • Quality metrics (e.g., uptime goals).
     • Estimation (COCOMO or PERT).

Pro Tip: Always relate answers to Nepali examples (Ncell, Khalti, NEA, Daraz). Examiners love context!