Week 1: Project Management Study Notes
Agenda
Introduction
Projects, Tasks, and Programs
Methodologies
Waterfall and Agile
Key Concepts: Scope, Schedule, Budget, Resources, Risks,
Communication
Introduction
This course provides a comprehensive overview of project management,
covering both traditional and Agile methodologies.
Students will use practical tools like JIRA and engage with real-world
scenarios to apply concepts effectively.
An introduction to Agile principles and the Scaled Agile Framework (SAFe)
equips learners to manage complex projects and enhance collaboration.
Hands-on learning through assignments, quizzes, and a group project
develops skills needed for dynamic project environments.
Projects, Tasks, and Programs
What Is a Project?
A temporary endeavor with a defined beginning and end, aimed at
creating a unique product, service, or result.
Distinguished from business operations by specific scope, resources,
timeframe, and objectives.
Project Examples
Simple Projects
Planting a garden: choose flowers, prepare soil, plant seeds, water
(duration: weeks)
Writing a short story: brainstorm, outline, write, edit, submit (duration:
days–weeks)
Complex Projects
Launching a new product line: market research, formulation, branding,
manufacturing, packaging, stocking (duration: months–1 year)
What Is a Task?
A specific, actionable unit of work with a defined outcome, usually
completed in minutes or hours.
Examples: writing an email, scheduling a meeting, fixing a faucet
Differences Between Tasks and Projects
Feature Task Project
Scope Small, well-defined, Large, complex
atomic
Duration Short-term (minutes– Long-term (weeks–
days) years)
Resources Minimal Varied, multiple
resources
Dependenc Independent or few Interdependent, ordered
ies
Outcome Specific, measurable Broad goal achieved via
result tasks
Programs
A program is a group of related projects managed in a coordinated manner to
achieve benefits not available when managed separately.
Purpose
Align multiple projects with organizational goals
Ensure projects deliver cumulative benefits that support strategy
Example
A digital transformation program comprising system upgrades, process
automation, and employee training to improve efficiency
Methodologies
Project management methodologies offer structured frameworks for
planning, executing, monitoring, and closing projects.
Major Methodologies
Waterfall
Spiral
Agile
Big Bang
Core Components
Methodology: collection of techniques for completing project activities
Tools: software applications (e.g., IDEs, Visio, CASE tools, MS Project)
Techniques: guidelines for analysts (e.g., use case modeling,
interviewing)
Models: virtual representations to simplify and communicate complex
systems
Waterfall Model
Characteristics
Linear progression through sequential phases: requirements → design
→ development → testing → deployment
Emphasis on extensive upfront planning and documentation
Clear roles, predictable timelines, and budgets
Low adaptability to change; costly rework if requirements evolve
Example
Construction projects leverage Waterfall due to stringent safety regulations
and the need for sequential approvals.
Challenges
Rigid structure struggles with changing requirements
Late feedback can lead to expensive rework
Discourages experimentation and iterative improvement
Spiral Model
Characteristics
Risk-driven, iterative model combining Waterfall and prototyping
Focus on early risk identification and mitigation
Adapts to changing requirements through repeated cycles
Example
NASA’s Space Shuttle program used Spiral to iteratively address risks and
improve safety over successive mission cycles.
Big Bang Model
Characteristics
Minimal planning, no formal phases or documentation
Highly code-centric; rapid development with on-the-fly integration
Best for small teams or ambiguous requirements
Fast and flexible but prone to errors and rework
Example
Hackathons exemplify Big Bang by requiring teams to prototype quickly
under time pressure.
Agile Model
Characteristics
Iterative and incremental delivery in short sprints
Cross-functional teams for rapid problem-solving and collaboration
Prioritizes working software over extensive documentation
Emphasizes continuous learning, feedback loops, and adaptability
Example
Netflix uses Agile to deliver new features in sprints, leveraging user feedback
and data to iterate quickly.
Waterfall vs. Agile Comparison
Aspect Waterfall Agile
Adaptability Low; rigid sequential High; iterative and
phases responsive
Feedback Late-stage feedback Continuous feedback and
Loop improvement
Time to Value Longer due to sequential Faster through incremental
completion delivery
Team Phase-based, specialized Cross-functional, empowered
Structure roles teams
Documentati Heavy upfront Lightweight, just-in-time
on
Risk Traditional, phase-based Ongoing risk mitigation each
Management iteration
Course Focus on Agile
Agile is the dominant methodology in software and beyond, fostering
problem-solving mindsets in marketing, healthcare, and more.
Benefits for Students
Enhances employability with sought-after skills
Encourages entrepreneurial thinking and experimentation
Empowers graduates to drive innovation and adapt strategies
Key Concepts
Scope
Definition: All work needed to deliver the project
Example: Design, develop, test, and launch a responsive website
Schedule
Definition: Planned start and finish dates for activities
Example: January 10 to October 31, with milestones at design,
development, testing, and launch
Budget
Definition: Expected costs for project components
Example: Personnel $250K; Hardware $90K; Software $40K; Marketing
$100K; Miscellaneous $20K
Resources
Definition: Allocation of human, technical, and financial assets
Example: Project Manager, development team, AWS cloud
infrastructure
Risk
Definition: Uncertain events impacting objectives
Example: Delayed design approval—mitigation via early stakeholder
engagement and regular check-ins
Communication
Essential for stakeholder alignment, progress reporting, and issue
resolution
Involves creating and following a tailored communication plan
Fundamental Advantages of Formal Project Management
Better control of financial, physical, and human resources
Improved customer relations
Shorter development times and lower costs
Higher quality, reliability, and profit margins
Enhanced coordination, morale, and strategic goal alignment
Triple Constraint
Project success balances three constraints:
Scope: What work will be done
Time: When it will be completed
Cost: Budget required
Project managers apply knowledge, tools, and techniques to meet these
constraints and stakeholder expectations.
PMI Framework
Knowledge Areas
1. Integration Management
2. Scope Management
3. Schedule Management
4. Cost Management
5. Quality Management
6. Resource Management
7. Communications Management
8. Risk Management
9. Procurement Management
10. Stakeholder Management
Process Groups
1. Initiating
2. Planning
3. Executing
4. Monitoring & Controlling
5. Closing
Agile shares many areas—scope, schedule, cost, resource, and risk
management—within its iterative framework.
Case Study: Cyberguard Dynamics
Context: Financial services provider implementing an AI-driven
cybersecurity system.
Project Goals:
Real-time threat detection and automated response
Enhanced data protection and regulatory compliance
Increased efficiency through machine learning
Key Features:
Continuous network monitoring
Anomaly detection and predictive analytics
Automated threat response and compliance reporting
Weekly Analysis Tasks
1. Overview Cyberguard Dynamics and its AI-driven cybersecurity
objectives
2. Compare Traditional vs. Agile methodologies
3. Analyze how each methodology impacts project outcomes
4. Recommend the optimal methodology with pros and cons for each
Further Reading
Mokhtar, R., & Khayyat, M. (2022). A Comparative Case Study of
Waterfall and Agile Management. SAR Journal, 5(1), 52–62.
INSIGHT Staff. (2018). Lessons Learned: Aligning System Development
Models. APPEL Knowledge Services.
Schmitz, M. Agile vs. Waterfall Methodology: Which One Should You
Use?
Hoory, L., & Bottorff, C. (2023). Agile vs. Waterfall. Forbes.
Schwaber, K. (2011). Applying Agile to Nonsoftware Enterprise Projects.
Project Management Institute.