Major Project-II (EX-805) - Unit 2 Short Notes

2.1 Implementation Strategies & Methodologies

• Core Execution Models:

  • Waterfall: Sequential phases (Design → Build → Test). Best for well-defined, stable requirements. High risk of late-stage failures if requirements change.

  • Agile/Iterative (Scrum/Kanban): Work in short cycles (Sprints). Delivers incremental value, adapts to change. Requires high customer involvement.

  • Hybrid: Combine upfront planning (Waterfall) with iterative development (Agile) for complex projects.

• Translating Plan to Action:

  • Work Breakdown Structure (WBS): Hierarchical decomposition of total scope into manageable work packages. Deliverable-oriented.

  • Gantt Chart: Visual timeline showing task durations, dependencies, and milestones. Used for schedule baseline.

  • Critical Path Method (CPM): Identifies longest sequence of dependent tasks (critical path). Any delay here delays the project.

  [!TIP] Exam Focus: Be able to contrast Waterfall vs. Agile for a given project scenario. Define WBS and explain its role in task assignment.

2.2 Monitoring, Tracking, & Control

• Performance Measurement Baselines: Compare actual progress against the approved schedule (time) and budget (cost) baselines.

• Key Performance Indicators (KPIs):

  • Schedule Variance (SV): SV = EV - PV

  • Cost Variance (CV): CV = EV - AC

  • Schedule Performance Index (SPI): SPI = EV / PV (>1 = ahead)

  • Cost Performance Index (CPI): CPI = EV / AC (>1 = under budget)

  • Scope Creep: Uncontrolled changes to project scope. Major threat to baseline.

• Earned Value Management (EVM) Core Formulas:

  • Planned Value (PV): Budgeted cost for work scheduled.

  • Earned Value (EV): Budgeted cost for work actually performed.

  • Actual Cost (AC): Total cost incurred for work performed.

  • Estimate at Completion (EAC): EAC = BAC / CPI (if current cost performance continues).

  • Variance at Completion (VAC): VAC = BAC - EAC.

  \boxed{CPI = \frac{EV}{AC} \quad , \quad SPI = \frac{EV}{PV} \quad , \quad EAC = \frac{BAC}{CPI}}

• Change Control Process: Formal procedure for modifying scope, schedule, or budget.

  1. Request: Stakeholder submits change request.

  2. Analyze: Impact on time, cost, quality, resources assessed.

  3. Approve/Reject: Change Control Board (CCB) decides.

  4. Communicate & Update: Inform team, update baselines if approved.

  [!TIP] Common Pitfall: Confusing AC (actual money spent) with EV (value of work done). EV is the key to all EVM metrics.

2.3 Tools, Technologies, & Technical Execution

• Development & Collaboration Tools:

  • Version Control: Git (with GitHub/GitLab/Bitbucket) for code/documentation history, branching, merging.

  • Project Management: Jira (Agile), Trello (Kanban), MS Project (Waterfall), Asana.

  • Communication: MS Teams, Slack (channels, file sharing, meetings).

• Technical Execution Setup:

  • Lab/Workshop Safety: Pre-use safety checklist, Personal Protective Equipment (PPE), emergency procedures, risk assessment for experiments.

  • Data Collection: Instrument calibration certificates, standardized logging sheets/procedures, data backup protocol (3-2-1 rule: 3 copies, 2 media types, 1 offsite).

  [!TIP] Exam Tip: Always link tool choice to project need (e.g., "For a software project with multiple developers, Git is essential for version control and collaboration").

2.4 Risk & Issue Management During Execution

• Active Risk Management Cycle:

  1. Review Risk Register: Weekly/bi-weekly review of identified risks and mitigation status.

  2. Identify New Risks: From daily stand-ups, testing results, external changes.

  3. Log Issues: Distinguish Risk (future uncertainty) from Issue (present problem). Log both in a register.

  4. Assign Owner & Action: Each risk/issue has a clear owner and mitigation/action plan.

• Escalation Procedure: Define clear thresholds (e.g., cost overrun >10%, critical path delay >3 days) and escalation matrix (who to inform: Team Lead → Supervisor → Project Champion).

• Problem-Solving Framework: PDCA (Plan-Do-Check-Act) or Root Cause Analysis (5 Whys) for technical blockades.

2.5 Quality Assurance & Testing/Validation

• Quality Assurance (QA) vs. Quality Control (QC):

  • QA: Process-oriented. Prevents defects (e.g., following coding standards, design reviews).

  • QC: Product-oriented. Identifies defects (e.g., testing, inspection).

• Testing/Validation Hierarchy:

  • Unit Testing: Test individual components/modules.

  • Integration Testing: Test interfaces between modules.

  • System Testing: Test complete integrated system against requirements.

  • User Acceptance Testing (UAT): End-user validates solution meets needs.

• Verification & Validation (V&V):

  • Verification: "Are we building the product right?" (Conforms to specs).

  • Validation: "Are we building the right product?" (Meets user needs).

• Statistical Validation: For experimental data, use measures like Mean, Standard Deviation, Confidence Intervals. Replication (n≥3) is key for reliability.

2.6 Intermediate Documentation & Record Keeping

• Primary Source Documents:

  • Lab Notebook/Engineering Journal: Bound, paginated, dated entries. Records hypotheses, procedures, raw data, observations, calculations in real-time. Legal document for IP/patents.

  • Daily/Weekly Logs: Brief entries on tasks done, issues, next steps.

• Living Project Documents (updated continuously):

  • Design Documents, Data Logs (raw & processed), Test Reports, Code Repository (with READMEs), Meeting Minutes.

• Drafting Final Report Chapters: Write Methodology and Implementation sections as you work. Do not wait until the end.

2.7 Adaptation, Iteration, & Feedback Incorporation

• Interim Analysis: Compare preliminary results against success criteria and hypotheses defined in the proposal.

• Pivoting vs. Iterating:

  • Iteration: Refining the current approach (e.g., tweaking algorithm parameters).

  • Pivot: Fundamental change in direction (e.g., switching technology stack, changing target user group). Requires formal change request.

• Feedback Loops: Actively seek and document feedback from:

  • Supervisor: During scheduled reviews.

  • Peers: Informal code/design reviews.

  • Stakeholders/End-users: Through demos or prototypes.

• Managing Re-work: Track re-work as a cost and schedule impact. Analyze root cause to prevent recurrence.

2.8 Professional, Ethical, & Safety Considerations

• Ethical Conduct:

  • Data Integrity: No fabrication, falsification, or selective reporting. Keep raw data.

  • Authorship & IP: Clear agreements on contribution and ownership (institutional policies apply).

  • Confidentiality: Protect sensitive stakeholder data (NDAs).

• Safety & Sustainability:

  • Continuous Risk Assessment: Before each new experiment/phase.

  • Environmental Impact: Dispose of waste properly, consider energy use of systems, life-cycle analysis where applicable.

• Professional Communication: Clear, respectful, and documented (email for decisions). Timely escalation of blockers.

2.9 Preparation for Final Deliverables & Presentation

• Final Report/Thesis Structure (Key Chapters):

  1. Introduction

  2. Literature Review

  3. Methodology (from 2.6)

  4. Implementation & Results (from 2.6, 2.5)

  5. Analysis & Discussion (from 2.7)

  6. Conclusion & Future Work

• Effective Visualizations:

  • Choose the right chart (line for trends, bar for comparison, scatter for relationships).

  • All figures/tables must have clear titles, labeled axes, and legends.

  • Include prototype images, system architecture diagrams, screenshots.

• Presentation & Viva:

  • Storytelling Arc: Problem → Your Solution → How You Built It → What You Found → Why It Matters.

  • Slide Design: 1 idea per slide, minimal text, high-impact visuals.

  • Anticipate Questions: Prepare for "What was the biggest challenge?", "How is your work different from X?", "What are the limitations?", "Future work?".

  [!TIP] Final Checklist: Ensure all figures are cited in text, bibliography is complete, abstract is standalone, and you can explain any code/equation/data point in your appendix.