Course (Part 778)

Course: Project Management Crash Course: Project Management 101

Chapter: Introduction to Project Management — Composition Project management is the structured discipline of planning, executing, and controlling resources to achieve defined objectives within time and budget constraints. This chapter introduces the core elements of project management, emphasizing why a disciplined approach improves the likelihood of successful outcomes. Readers will learn the five major project phases—initiation, planning, execution, monitoring and controlling, and closure—and how each phase contributes to predictable delivery. Scope management is highlighted as essential for defining boundaries and preventing scope creep that can undermine schedules and budgets. Time management techniques such as task breakdowns, milestones, Gantt charts, and Critical Path Method help teams create realistic schedules. Cost management involves estimating, budgeting, and monitoring expenditures so that projects remain financially viable. Quality management ensures deliverables meet standards through both assurance and control activities. Risk management processes identify potential threats and create mitigation plans before problems become crises. Stakeholder management underscores the importance of early identification, transparent communication, and expectation management to build support. The chapter also surveys methodologies, contrasting plan-driven approaches with iterative ones like Agile. Within Agile, Scrum is presented as a lightweight framework that uses sprints, roles, and ceremonies to maintain focus and responsiveness. Best practices such as clear communication, frequent check-ins, thorough documentation, team empowerment, and flexibility are recommended to translate methodology into effective practice.

Lesson

Topic: Introduction to Project Management

Learning Outcomes

• Define project management and list its primary objectives.
• Explain the project life cycle phases and their purposes.
• Describe key knowledge areas: scope, time, cost, quality, risk, and stakeholder management.
• Compare Agile and Scrum with traditional plan-driven approaches.
• Apply best practices for timelines, stakeholder engagement, and team empowerment.

Conceptual Explanation

Project management is the application of processes, methods, skills, and experience to achieve specific project objectives. The project life cycle—initiation, planning, execution, monitoring & controlling, and closure—provides a predictable structure for delivery. Scope management defines project boundaries and deliverables to avoid uncontrolled changes (scope creep). Time management converts scope into a sequenced schedule using techniques such as Work Breakdown Structure (WBS), Gantt charts, and Critical Path Method (CPM). Cost management estimates and controls budgeted resources; periodic financial reviews detect overruns early. Quality management combines assurance (processes) and control (inspection, testing) to meet acceptance criteria. Risk management entails identifying, analyzing, and mitigating threats and opportunities throughout the lifecycle. Stakeholder management focuses on mapping interests, communication planning, expectation setting, and participation. Agile offers iterative delivery and customer collaboration, while Scrum provides roles (Product Owner, Scrum Master, Development Team), time-boxed sprints, and ceremonies that promote transparency and rapid feedback. Best practices include explicit communication channels, frequent check-ins, thorough documentation, empowerment of team members, and built-in flexibility to adapt plans.

Bilingual (EN → বাংলা)

Key Terms — English and Bengali

English	বাংলা (Bangla)
Project	প্রকল্প (Prokolpo)
Scope	পরিসর / কাজের সীমা (Porishor / Kajer Seema)
Stakeholder	প্রাসঙ্গিক ব্যক্তি/গোষ্ঠী (Prasangik Byakti/Goshti)
Risk	ঝুঁকি (Jhuki)
Sprint	স্প্রিন্ট (Sprint) — সময়সীমাবদ্ধ কাজ (Samoysīmābaddho Kaj)

Important Notes

• Document assumptions and decisions; documentation is the project's memory.
• Build realistic schedules with buffers for uncertainty; avoid overcommitment.
• Engage stakeholders early and often to align expectations and secure support.
• Empower teams to own tasks; authority without accountability undermines delivery.
• Use the right methodology for context—Agile is not a universal panacea.

Exercises

Types: True / False / Fill in the Blanks / MCQ / Matching / Descriptive / Creative

Exercise Set — Questions and Answers

Type	Question / Prompt	Answer
True / False	1. The project life cycle ends at the execution phase. 2. Scope creep occurs when uncontrolled changes expand the project deliverables.	Answer 1. False — The life cycle continues through monitoring & controlling and closure. 2. True — Scope creep is uncontrolled expansion of scope without time/budget adjustments.
Fill in the Blanks	1. A ________ breaks a project into smaller tasks for scheduling. 2. In Scrum, the role responsible for maximizing product value is the ________.	Answer 1. Work Breakdown Structure (WBS). 2. Product Owner.
MCQ	Which technique identifies the longest sequence of dependent tasks that determines project duration? A. Gantt chart   B. Critical Path Method (CPM)   C. Kanban   D. MoSCoW	Answer Correct: B. Critical Path Method (CPM) — it finds the longest path of dependent activities determining minimum project duration.
Matching	Match column A (term) with column B (definition): A1. Risk Management A2. Sprint Backlog A3. Stakeholder A4. Quality Control	Answer Matches: A1 → Identification and mitigation of potential issues affecting objectives. A2 → Set of tasks the Scrum team commits to for the current sprint. A3 → Any person or group affected by or influencing the project. A4 → Activities that verify deliverables meet defined standards (inspection, testing).
Descriptive	Explain in 150–200 words how stakeholder management influences project success. Include two concrete techniques.	Answer Sample points to include: Early stakeholder mapping clarifies who influences scope and priorities; a communication plan with frequency and channels mitigates surprises; active involvement (workshops, demos) secures buy-in and uncovers requirements; expectation management via transparent status reporting reduces conflict; escalation paths and documented decisions preserve relationships. Two techniques: stakeholder power-interest grid to tailor engagement; regular sprint reviews or demo sessions to collect feedback and validate direction.
Creative	Design a one-page "project kickoff" checklist for a small software project (max 10 items).	Answer Suggested checklist items: 1. Confirm project objectives and success criteria. 2. Identify and list stakeholders with contact roles. 3. Define high-level scope and explicit out-of-scope items. 4. Appoint Product Owner and Scrum Master (or PM). 5. Establish initial backlog or feature list. 6. Agree sprint length and cadence for meetings. 7. Set up collaboration tools (repo, issue tracker, CI/CD, chat). 8. Agree definition of done and quality criteria. 9. Identify top 5 risks and mitigation owners. 10. Schedule first sprint planning and stakeholder review.

Activities, Vocabulary, Homework, Practice Task

Activities

1. In groups, create a four-phase timeline for a hypothetical website project and present task dependencies.
2. Run a 30-minute mini-sprint: plan, work on a tiny backlog item, review, and retrospective.

Vocabulary

• WBS (Work Breakdown Structure)
• CPM (Critical Path Method)
• Scope Creep
• Product Backlog
• Time-boxing

Homework

1. Write a one-page plan that defines scope, three milestones, and a risk register for a small project of your choice.
2. Read an article on Agile vs Waterfall and summarize three trade-offs in 300 words.

Practice Task

Create a simple Gantt chart (paper or digital) for your homework project, showing dependencies and at least one buffer period; submit as PDF or screenshot.