Course (Part 776)

Course: Project Management Crash Course: Project Management 101

The field of project management organizes people, time, and resources to transform objectives into tangible outcomes within defined constraints. This introduction outlines the fundamental components of the discipline, including the project life cycle, scope, time, cost, quality, risk, and stakeholder management. Understanding the life cycle—initiation, planning, execution, monitoring and controlling, and closure—helps managers allocate attention and governance at each phase. Clear scope definition reduces the likelihood of scope creep and preserves timelines and budgets. Time management techniques such as Gantt charts and the Critical Path Method make schedules explicit and measurable, while cost controls and regular financial reviews maintain fiscal health. Quality assurance and control processes guard deliverables against failure and align products with acceptance criteria. Risk management requires proactive identification, assessment, and mitigation of uncertainties that threaten objectives. Stakeholder engagement and transparent communication are indispensable: they build support and reduce friction across the project ecosystem. Agile and Scrum are presented as complementary approaches for dynamic environments, emphasizing iteration, customer feedback, and cross-functional teams. Scrum’s roles, events, and artifacts (Product Owner, Scrum Master, Development Team; sprints; backlogs; increments) provide a practical framework for implementing Agile values. Best practices—clear communication, frequent check‑ins, documentation, empowerment, and flexibility—translate theory into repeatable habits that improve delivery outcomes. Finally, the text acknowledges that university courses often omit tacit skills such as political navigation, stakeholder psychology, and adaptive leadership, which are learned in practice but are essential to success.

Lesson

Topic: Introduction to Project Management — Agile, Scrum, Timelines & Stakeholders

Learning Outcomes

• Explain the project life cycle and its five phases.
• Distinguish core knowledge areas: scope, time, cost, quality, risk, and stakeholder management.
• Compare Agile and Scrum and identify appropriate contexts for their use.
• Apply best practices for timeline control and stakeholder engagement.

Conceptual Explanation

Project management is a structured discipline for delivering change: it aligns scope, schedule, budget, quality, and people to achieve defined outcomes. The project life cycle provides governance checkpoints across initiation, planning, execution, monitoring & controlling, and closure. Scope management defines boundaries and prevents scope creep; time management decomposes work into tasks, sequences them, and identifies critical paths; cost management estimates and controls expenditures; quality management ensures acceptance criteria are met; risk management anticipates threats and opportunities; stakeholder management secures alignment and support. Agile is an iterative mindset that values individuals, working deliverables, customer collaboration, and responsiveness to change; Scrum provides a concrete framework (roles, events, artifacts) to operationalize Agile in short, inspectable sprints. Practical tools include Gantt charts, Kanban boards, CPM analyses, and backlog grooming techniques. Best practices focus on communication, frequent reviews, documentation, empowerment of teams, and built-in flexibility to adapt to evolving information.

Answer

Use the project life cycle as your primary planning scaffold, map stakeholders early, prioritize scope items using MoSCoW or Value-based methods, timebox work into sprints when complexity or change is high, and review cost/quality metrics at each milestone.

Bilingual (EN → বাংলা)

Key Terms and Translations

English	বাংলা (Bangla)
Project Life Cycle	প্রকল্প জীবনচক্র
Scope Management	পরিধি ব্যবস্থাপনা
Time Management	সময় ব্যবস্থাপনা
Cost Management	খরচ ব্যবস্থাপনা
Quality Management	মান ব্যবস্থাপনা
Risk Management	ঝুঁকি ব্যবস্থাপনা
Stakeholder	স্টেকহোল্ডার / অংশীদার
Agile	অ্যাজাইল (দ্রুত অভিযোজ্য পদ্ধতি)
Scrum	স্ক্রাম (অ্যাজাইল ফ্রেমওয়ার্ক)

Answer

Use these translations when communicating core concepts with Bangla‑speaking stakeholders; simpler terms often improve clarity in cross‑cultural teams.

Important Notes

• Scope clarity and change control are primary defenses against delays and budget overruns.
• Agile/Scrum fit environments with uncertainty, frequent feedback needs, or evolving requirements.
• Document decisions and assumptions to preserve institutional memory and enable audits.
• Soft skills—communication, negotiation, and stakeholder empathy—are as critical as technical tools.

Exercises → True / False / Fill in the Blanks / MCQ / Matching / Descriptive / Creative

Activities, Vocabulary, Homework, Practice Task

True / False

1. The project life cycle always follows the same sequence of activities regardless of project type.
Answer

False — The life cycle phases are common, but activities and emphasis vary by project type and methodology.

2. Scope creep occurs when uncontrolled changes to project scope are implemented.
Answer

True — Unmanaged changes to scope that are not controlled by formal change requests cause scope creep.

3. Scrum prescribes a fixed schedule of three‑month sprints.
Answer

False — Scrum recommends short time‑boxed sprints, typically 2–4 weeks, not three months.

Fill in the Blanks

1. Breaking a project into short cycles and frequent reviews is central to the __________ methodology.
Answer

Agile

2. The person responsible for prioritizing the product backlog in Scrum is the __________.
Answer

Product Owner

3. A visual timeline that shows tasks, durations, and dependencies is called a __________ chart.
Answer

Gantt

Multiple Choice Questions (MCQ)

1. Which technique identifies the sequence of tasks that determine the shortest project duration?
   1. Kanban
   2. Critical Path Method
   3. MoSCoW
   4. PERT (but not CPM)
   Answer

   b) Critical Path Method

2. Who facilitates Scrum events and removes impediments?
   1. Product Owner
   2. Project Sponsor
   3. Scrum Master
   4. Business Analyst
   Answer

   c) Scrum Master

Matching

Match the term (1–4) with the definition (A–D):

Number	Term	Letter	Definition
1	Scope	A	Set of features, functions, and deliverables agreed for the project.
2	Risk Register	B	Documented list of identified risks, impacts, and responses.
3	Sprint	C	Time‑boxed iteration in Scrum, often 2–4 weeks.
4	Stakeholder	D	Individual or group affected by or able to affect the project.

Answer

1–A, 2–B, 3–C, 4–D

Descriptive

1. Explain in 3–4 sentences how you would integrate risk management into sprint planning.
Answer

During sprint planning, review the sprint backlog for tasks with identified risks and estimate their probability and impact. Prioritize risk responses—mitigation, avoidance, transfer, or acceptance—and include contingency tasks or buffers. Assign risk owners and acceptance criteria, and ensure the Definition of Done reflects risk‑related quality checks. Document any residual risks in the risk register and schedule a mid‑sprint check if necessary.

2. Describe a stakeholder communication plan for a small product development project (bullet points).
Answer
• Identify stakeholders and map influence/interest.
• Define communication cadence: weekly team updates, biweekly stakeholder demos, monthly executive summaries.
• Choose channels: email for formal deliverables, chat for quick clarifications, demo sessions for feedback.
• Set escalation paths and decision rights.
• Record and distribute meeting notes and action items.

Creative

Design a one‑page visual (describe layout) that combines a Gantt snapshot, risk heatmap, and stakeholder RACI for a two‑month project sprint plan.

Answer

Top third: compact Gantt showing weeks 1–8 with color‑coded task bars and critical path highlighted. Middle third: a 3×3 risk heatmap (probability × impact) listing top 6 risks with mitigation tags. Bottom third: a RACI table for key deliverables listing Responsible, Accountable, Consulted, and Informed columns for each stakeholder. Include legend and date of last update in the footer.

Activities

1. Workshop: Create a mini project plan (one page) for a hypothetical mobile app (60 minutes).
Answer

Deliverable: one‑page plan with objectives, scope boundary, 8‑week timeline, three milestones, top 5 risks, and stakeholder map.

2. Roleplay: Stakeholder negotiation exercise (30 minutes).
Answer

Objective: practice clarifying requirements, setting expectations, and documenting agreed changes through a short change request form.

Vocabulary

• Backlog
• Timebox
• Critical Path
• Scope Creep
• Retrospective

Answer

Review the glossary definitions given in the Conceptual Explanation section and the bilingual table for translations.

Homework

1. Write a one‑page reflection: choose a past team project you experienced and map it to the five life cycle phases. Identify one thing you would have changed.
Answer

Expected: clear mapping to phases, identification of a missing control (e.g., no risk register), and a practical change (e.g., introduce sprint retrospectives or formal change control).

2. Create a prioritized product backlog of 8 items for a simple feature set (use MoSCoW).
Answer

Expected: backlog with at least 2 Must‑haves, 3 Should/Could, and 1 Won’t have; include short acceptance criteria for each.

Practice Task

Using any tool (paper, Excel, or PM software), produce a two‑week sprint plan with tasks, estimates, and daily standup agenda; submit a screenshot or exported file.

Answer

Rubric: task decomposition, realistic estimates, clear ownership, and a concise standup template (yesterday/today/blockers). Bonus for including a risk item and test/QA step.

Wrap Up / Suggested Readings

• "A Guide to the Project Management Body of Knowledge (PMBOK Guide)" — for foundational standards.
• "Scrum Guide" by Schwaber & Sutherland — concise Scrum reference.
• Articles on Agile transformations and stakeholder engagement (recommended links provided in course LMS).