- 1. Problem Identification & Justification
- 2. Problem Definition (Project Proposal)
- 3. Project Planning & Sequencing
- 4. Project Organization (Staffing)
- 5. Resource Allocation & Scheduling
- 6. Tracking, Reporting & Controlling
- 7. Project Termination & Release
"If You Fail to Plan, You Plan to Fail"
- Defined deliverables & scope boundaries
- Infrastructure & environment setup
- Seek consensus with the team on metrics
- Create a reasonable, agreed approach
- Operate in a methodical timeframe
- Scope Planning: Document assumptions, constraints, user needs & exclusions.
- Scope Verification: Quality-assuring acceptance of deliverables.
- Infrastructure: Hardware, networks, tools, governance & team structure.
- MTA (Milestone Trend Analysis): Tracks planned vs. actual milestone dates over time.
Work Breakdown Structure (WBS)
Best built collaboratively in a Joint Project Planning (JPP) session using either Top-Down decomposition (goal → work packages) or Bottom-Up aggregation (team brainstorm → grouped hierarchy).
Each work package must have clear: 1) Status/Completion measurability, 2) Start & End event, 3) Deliverable output, 4) Time/Cost estimateability, 5) Acceptable duration limits, and 6) Independent task assignment.
Process Models: Thick vs. Thin
- Waterfall Model: Sequential phases (Reqs → Design → Code → Test). Best when requirements are stable and well understood.
- V-Process Model: Maps every dev phase directly to a corresponding testing level (Unit, Integration, System, Acceptance).
- Spiral Model (Boehm): Risk-driven iterative cycles (Objective → Risk Analysis → Engineering → Evaluation).
- Prototyping & Incremental Delivery: Rapid user feedback for unclear UI/needs; delivers working increments early.
- Thick (Heavyweight) Methodologies: Heavy documentation, formal roles, strict sign-offs —
RUP,SSADM,PRINCE2. - Thin (Agile/Lightweight) Methodologies: Adaptive, iterative, people-focused —
XP(Planning Game),Scrum,Crystal Clear. - Agile Planning Trade-off: When time/budget are fixed, XP adjusts scope (fewer stories in the increment) rather than delaying delivery.
- Small/Student Projects (Unit 14): Keep planning lightweight, but never skip WBS, schedule, or version control!
Upper/Lower CASE & Specifications
Upper CASE Tools (Planning & Design)
Used for documentation, collaboration, requirements modeling & tracking: Git, Slack, Figma, OMG/UML modeling tools.
Lower CASE Tools (Code & Implementation)
Used directly for coding, compiling, debugging & simulation: VS Code, CodeBlocks, PyCharm, Gazebo.
Object-Oriented (OMG UML)
Use Case Diagram & Description Table, Class, Sequence, Collaboration, State, Package & Deployment Diagrams.
Structured Approach
Context Diagram, DFD Level 0 / 1 / 2, Flowcharts, and Jackson Structured Programming (JSP) Diagrams.
Key Exam Takeaways
- If a deliverable isn't in the WBS, it isn't in the project.
- Prevents unpriced gold-plating and feeds directly into Effort Estimation and CPM.
- Written in Initiation by the PM/Sponsor to authorize work.
- Project Plan comes in Planning (how, when, how much).
- Hardware & tech double rapidly; projects taking years risk launching obsolete tech.
- Deliver incrementally when requirements shift.
Completed Concept 3: Planning, WBS & Process Models
Next up: Effort Estimation with Albrecht Function Point Analysis (FPA) & COCOMO.