Project Management ও Team Collaboration

Estimation Techniques ⭐

• Story Points (Fibonacci 1,2,3,5,8,13)
• T-shirt size (XS, S, M, L, XL)
• Planning Poker — team consensus
• PERT — (optimistic + 4×likely + pessimistic) / 6
• Bucket System — quick bulk estimate

কেন Story Points vs Hours?

• Hours = absolute, misleading
• Story points = relative complexity (effort+risk+uncertainty)
• Team velocity = avg points/sprint → forecast

Scrum Roles Recap

• Product Owner — vision, backlog, priority
• Scrum Master — facilitate, remove blocker
• Dev Team — 3-9 people, self-organizing

Sprint Ceremonies

• Planning — goal + backlog commitment
• Daily Standup (15m) — yesterday/today/blocker
• Refinement — groom backlog ahead
• Review — demo to stakeholders
• Retrospective — what went well/wrong/change

Jira Workflow

Backlog → To Do → In Progress → Code Review →
  QA → Done

Epic → Story → Sub-task / Bug
Labels, components, fix version
Dashboard, roadmap, burndown

Definition of Ready (DoR)

Story sprint-এ নেয়ার আগে:

• Clear description + acceptance criteria
• Estimated
• Dependencies identified
• Designs ready (if UI)
• Small enough (1 sprint)

Definition of Done (DoD)

• Code written + reviewed
• Unit tests passing
• Documentation updated
• QA approved
• Deployed to staging
• Product Owner signed off

Velocity Tracking

Sprint 1: 25 points
Sprint 2: 30 points
Sprint 3: 28 points
Avg velocity = 27.6

Forecast: 100 points backlog → 100/27.6 ≈ 4 sprints

Retrospective Formats

• Start/Stop/Continue — simple
• Mad/Sad/Glad — emotional
• 4 L's — Liked, Learned, Lacked, Longed-for
• Sailboat — wind (helps), anchor (slows), rocks (risks)

Retro Best Practices

• Blameless, safe environment
• Actionable outcomes (with owner)
• Follow-up next retro
• Rotate facilitator

Stakeholder Communication

RACI Matrix

Task	PM	Dev	PO	QA
Design	C	R	A	I
Build	I	R	A	C
Test	I	C	A	R

R=Responsible, A=Accountable, C=Consulted, I=Informed।

Status Reporting

• Executive: 1-page summary (RAG — Red/Amber/Green)
• Team: detailed burndown
• Client: demo + next milestones

Risk Management

Risk Register:
  ID | Description | Probability | Impact | Mitigation | Owner

Example:
  R1 | Third-party API change | Medium | High |
      | Implement adapter pattern | Karim

Critical Path Method

Longest chain of dependent tasks = project duration। Focus-এ রাখুন।

Conflict Resolution

1. Listen both sides
2. Separate people from problem
3. Focus on interests not positions
4. Brainstorm options
5. Decide on objective criteria

Remote/Distributed Team

• Overlap hours (async + sync)
• Written culture (docs)
• Record important meetings
• Tools: Slack, Notion, Loom, Miro
• Over-communicate
• Virtual coffee, team building

OKR (Objectives & Key Results)

Objective: Improve customer satisfaction
  KR1: NPS score 40 → 60
  KR2: Support ticket response < 2h
  KR3: 95% bug-free release

Quarterly, ambitious (70% achievement = success)