Project Management Cheatsheet Cheatsheet

📋

Project Management Fundamentals

The Foundation of Delivery

Project management is the discipline of planning, organizing, executing, and controlling resources to achieve specific goals within defined constraints (time, cost, scope, quality). Whether you are managing a software project, marketing campaign, or product launch, these fundamentals apply universally.

The Project Management Triangle (Iron Triangle)

Constraint	Description	How It Affects Others	Example
Scope	What needs to be delivered — features, deliverables, requirements	Increasing scope increases time and cost; decreasing scope reduces time and cost	Client adds 5 new features mid-project: timeline extends by 3 weeks, budget increases by 20%
Time	The schedule and deadlines for project completion	Shortening time increases cost (overtime, more resources) or reduces scope	Boss wants delivery 2 weeks earlier: either hire more developers (cost+) or cut 2 features (scope-)
Cost	The budget available for the project including resources, tools, and materials	Reducing budget increases time or reduces scope/quality	Budget cut by 30%: either extend timeline by 2 months or deliver fewer features with same team
Quality	The standard of deliverables — often considered the center of the triangle	Trade-offs among scope, time, and cost directly impact quality	Rushed project (time-) with reduced budget (cost-) results in buggy software (quality-)

Project Management Methodologies Comparison

Methodology	Approach	Flexibility	Best For	Key Characteristics
Waterfall	Linear, sequential phases	Low — changes are costly	Construction, manufacturing, regulated industries	6 phases: Initiation, Planning, Execution, Monitoring, Testing, Deployment; documentation-heavy
Agile	Iterative, incremental delivery	High — adapt to change	Software, product development, creative projects	Sprints (1-4 weeks), daily standups, sprint reviews, continuous feedback and improvement
Scrum	Agile framework with defined roles and ceremonies	High	Software development, product teams	Product Owner, Scrum Master, Developers; Sprints, Backlog, Daily Scrum, Sprint Review, Retrospective
Kanban	Visual workflow, continuous flow	Very High	Support teams, ops, continuous delivery	Kanban board (To Do, In Progress, Done), WIP limits, pull system, continuous delivery
Hybrid	Combines Waterfall planning with Agile execution	Medium	Large organizations, enterprise projects	Waterfall for planning/budgeting, Agile for development/execution; best of both worlds
PRINCE2	Process-based, structured methodology	Low-Medium	Government projects, large enterprises in UK/Europe/India	7 principles, 7 themes, 7 processes; emphasis on business justification and defined roles
Lean	Minimize waste, maximize value delivery	High	Manufacturing, startup MVPs, process optimization	Eliminate Muda (waste): overproduction, waiting, defects, overprocessing, inventory, motion, transport

Project Lifecycle Phases

5 Phases of Every Project

Phase 1: InitiationDefine project purpose, objectives, scope, stakeholders, and feasibility. Output: Project Charter, Stakeholder Register. Key question: Should we do this project?

Phase 2: PlanningCreate detailed project plan: scope, schedule, budget, resources, risks, quality, communication. Output: Project Management Plan, WBS, Gantt Chart. Key question: How will we do it?

Phase 3: ExecutionDo the work — develop product, manage team, coordinate resources, communicate with stakeholders. Output: Deliverables, Work Performance Data. Key question: Are we doing the work right?

Phase 4: Monitoring & ControlTrack progress against plan, manage changes, control scope, monitor risks, report status. Output: Change Requests, Status Reports, KPIs. Key question: Are we on track?

Phase 5: ClosureFinal deliverables, get formal acceptance, release resources, document lessons learned, archive project files. Output: Final Product, Lessons Learned, Project Closure Report. Key question: Did we deliver what was promised?

💡

PMBOK Knowledge Areas: The PMI PMBOK Guide defines 10 knowledge areas every project manager should master: Integration, Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurement, and Stakeholder Management. Together with the 5 process groups, these form the foundation of professional project management.

🔄

Agile Methodology

Adapt and Deliver

Agile is a mindset and set of principles for software development under which requirements and solutions evolve through collaborative effort of self-organizing teams. It promotes adaptive planning, evolutionary development, early delivery, and continual improvement.

The 4 Agile Values (Agile Manifesto)

Value	Over	What It Means in Practice
Individuals and Interactions	Processes and Tools	Trust and empower your team; face-to-face communication over documentation; people over rigid processes
Working Software	Comprehensive Documentation	Deliver a working product every sprint; working software is the primary measure of progress; documentation supports, not replaces, working code
Customer Collaboration	Contract Negotiation	Involve customers throughout the project; get feedback every sprint; adapt to changing requirements instead of following a fixed contract rigidly
Responding to Change	Following a Plan	Embrace change as a competitive advantage; re-prioritize backlog every sprint; the plan is a guide, not a contract

12 Agile Principles (Condensed)

Agile Principles Every Team Should Follow

1. Satisfy CustomerOur highest priority is to satisfy the customer through early and continuous delivery of valuable software

2. Welcome ChangeWelcome changing requirements, even late in development. Agile processes harness change for competitive advantage

3. Deliver FrequentlyDeliver working software frequently (weeks, not months), with preference for shorter timescales

4. Work TogetherBusiness people and developers must work together daily throughout the project

5. Trust & SupportBuild projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done

6. Face-to-FaceThe most efficient method of conveying information is face-to-face conversation (or video call for remote teams)

7. Working SoftwareWorking software is the primary measure of progress — not lines of code, documentation, or plans

8. Sustainable PaceAgile processes promote sustainable development. Sponsors, developers, and users should maintain a constant pace indefinitely

9. Technical ExcellenceContinuous attention to technical excellence and good design enhances agility

10. SimplicityMaximize the amount of work not done — simplicity is essential

11. Self-OrganizeThe best architectures, requirements, and designs emerge from self-organizing teams

12. Reflect & AdjustAt regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

Agile vs Waterfall: Waterfall is like building a house — you plan everything upfront and build sequentially. Agile is like painting a picture — you start with a vision, adjust as you go, and deliver something valuable at every step. In India, most tech companies (TCS, Infosys, Wipro, and all startups) use Agile or hybrid approaches. Waterfall is still used in government projects, construction, and heavily regulated industries.

🏈

Scrum Framework

The Most Popular Agile Framework

Scrum is a lightweight Agile framework for developing, delivering, and sustaining complex products. It is the most widely adopted Agile framework globally, used by 66% of software teams. Scrum provides just enough structure to be effective while remaining flexible enough to handle complexity.

Scrum Roles

Role	Responsibilities	Common Anti-Patterns	India Market Context
Product Owner	Owns the product backlog, defines priorities, ensures business value, accepts/rejects work, represents stakeholders	Being a order taker instead of decision maker, not available for questions, overcommitting the team	Often played by business analyst or product manager; salary: 15-35 LPA in India
Scrum Master	Facilitates Scrum events, removes impediments, coaches the team on Agile, shields team from external distractions	Acting as a project manager (bossing team), micro-managing developers, ignoring team dynamics	Average salary: 12-25 LPA; high demand in Indian IT sector; certification: PSM I from Scrum.org
Development Team	Self-organizing, cross-functional team of 3-9 people who do the actual work of delivering the product increment	Waiting for instructions instead of self-organizing, not collaborating, gold-plating features	Typically includes: frontend dev, backend dev, QA, UI/UX designer; team size 5-8 is optimal

Scrum Events (Ceremonies)

Event	Frequency	Duration	Purpose	Who Attends
Sprint Planning	Start of every sprint	2 hours (2-week sprint)	Define sprint goal, select backlog items for the sprint, create sprint backlog with tasks	PO, SM, Dev Team (entire Scrum Team)
Daily Scrum / Standup	Every day	15 minutes max	Answer 3 questions: What did I do yesterday? What will I do today? Any impediments?	Dev Team (SM facilitates but does not answer)
Sprint Review	End of sprint	2 hours (2-week sprint)	Demo completed work to stakeholders, collect feedback, update product backlog based on feedback	Scrum Team + Stakeholders
Sprint Retrospective	After Sprint Review	1.5 hours (2-week sprint)	Reflect on the sprint: what went well, what to improve, actionable items for next sprint	Scrum Team only (no managers/stakeholders)
Backlog Refinement	1-2 times per sprint	1-2 hours	Clarify, estimate, and prioritize backlog items; break large items into smaller ones	PO + Dev Team (SM optional)

Scrum Artifacts

Three Scrum Artifacts

Product BacklogOrdered list of everything needed in the product; owned and managed by the Product Owner; items are called PBIs (Product Backlog Items) or User Stories; continuously refined and re-prioritized

Sprint BacklogSet of PBIs selected for the current sprint plus the plan for delivering them; owned by the Development Team; sprint goal provides guidance on why items were selected

IncrementThe sum of all completed PBIs at the end of a sprint + value of all previous increments; must be in usable condition (working, tested, potentially shippable)

Scrum Master Interview Tip: The most common Scrum Master interview question is: "A stakeholder wants to add a feature mid-sprint. What do you do?" Answer: "I would remind the stakeholder that the sprint is a time-boxed commitment. The new feature can be added to the product backlog and prioritized for the next sprint. If it is truly critical, we can discuss with the Product Owner about cancelling the current sprint and re-planning. The team's commitment to the sprint goal must be respected."

📌

Kanban System

Visual Workflow Management

Kanban is a visual method for managing workflow with emphasis on continuous delivery without overloading the team. Originating from Toyota's manufacturing system, Kanban focuses on visualizing work, limiting work in progress, and optimizing flow.

Kanban Core Practices

Practice	Description	How to Implement	Benefits
Visualize Workflow	Make all work visible on a Kanban board with columns for each stage	Create columns: Backlog, To Do, In Progress, Review, Done; use physical board or digital (Trello, Jira)	Everyone sees the status of all work at a glance
Limit Work in Progress (WIP)	Set maximum number of items allowed in each column at any time	Set WIP limits per column: To Do (5), In Progress (3), Review (2); do not pull new work until capacity is available	Prevents multitasking and overloading; improves focus and quality
Manage Flow	Monitor, measure, and optimize the flow of work through the system	Track cycle time (start to finish), lead time (request to delivery), throughput (items per week)	Identify bottlenecks and optimize process continuously
Make Policies Explicit	Define clear rules for how work moves through the system	Define: Definition of Done, pull criteria per column, escalation process, priority rules	Reduces confusion, improves consistency and quality
Implement Feedback Loops	Regular reviews of the Kanban system and its effectiveness	Weekly Kanban review meeting, monthly metrics review, continuous improvement suggestions	Ensures the system evolves with the team and project needs
Improve Collaboratively	Use data-driven experiments to make incremental improvements	Identify the biggest bottleneck, propose a change, measure the impact, iterate	Continuous improvement culture; measurable gains over time

Kanban Metrics

Key Kanban Metrics to Track

Lead TimeTotal time from when a request is made to when it is delivered (request to done); includes wait time; target varies by team

Cycle TimeTime from when work actually starts to when it is completed (start to done); excludes wait time in backlog; more actionable than lead time

ThroughputNumber of work items completed per time period (per day, week, or sprint); measure average over 4-6 weeks for stability

WIP (Work in Progress)Number of items currently being worked on; lower WIP = faster flow; set explicit WIP limits per column

Cumulative Flow DiagramVisualizes work items in each status over time; bands show backlog, in-progress, done; ideal bands grow steadily from left to right

Bottleneck DetectionColumn where work items pile up (widest band in CFD); indicates insufficient capacity or upstream issues; address immediately

⚠️

Scrum vs Kanban: Scrum is time-boxed (fixed sprints), prescriptive (defined roles and ceremonies), and commits to delivering a set of items per sprint. Kanban is continuous flow, flexible (no fixed iterations), and focuses on limiting WIP and optimizing flow. Many Indian IT teams use Scrumban — a hybrid that uses Scrum ceremonies with Kanban visual management.

🛠️

Project Management Tools

Jira, Trello, Asana & More

Modern project management relies heavily on digital tools for planning, collaboration, tracking, and reporting. Below is a comprehensive comparison of the most popular PM tools used in India and globally.

PM Tools Comparison

Tool	Best For	Pricing	Key Features	Learning Curve
Jira	Software development, Scrum teams	Free (up to 10 users), $8.15/user/mo	Sprint planning, backlog management, sprint boards, reports, automation, integrations	Medium — powerful but complex
Trello	Visual project management, small teams	Free, $5/user/mo (Standard)	Kanban boards, cards, lists, Power-Ups, automation (Butler), calendar view	Low — easiest to learn
Asana	Cross-functional project management	Free (10 users), $10.99/user/mo	Tasks, projects, timelines, portfolios, workflows, automation, reporting	Low-Medium — intuitive interface
Monday.com	Work management, no-code workflows	Free, $9/seat/mo	Customizable boards, automations, dashboards, integrations, Gantt charts	Low — visual and user-friendly
Notion	All-in-one workspace (docs + PM)	Free, $8/user/mo	Databases, docs, wikis, Kanban boards, templates, collaboration, API	Low-Medium — flexible and powerful
ClickUp	All-in-one PM (docs, goals, time)	Free (100MB), $7/user/mo	Docs, tasks, goals, whiteboards, time tracking, dashboards, automations	Medium — feature-rich but can be overwhelming
Linear	Modern software teams	Free (10 users), $8/user/mo	Issue tracking, sprints, cycles, roadmap, GitHub/GitLab integration, keyboard-first	Low — minimalist and fast
Microsoft Project	Enterprise, traditional PM	$10/user/mo	Gantt charts, resource management, portfolio management, reporting, integration with MS ecosystem	High — enterprise-grade complexity

Tool Selection Tip: For Indian startups and small teams: use Notion or ClickUp as your all-in-one tool. For software development teams: Jira is the industry standard (especially in Indian IT services). For visual/creative teams: Trello or Monday.com. For enterprise/large organizations: Jira, Microsoft Project, or ServiceNow. Choose based on team size, workflow, and budget — not just features.

⚠️

Project Risk Management

Prevent Problems Before They Happen

Risk management is the process of identifying, analyzing, and responding to risks throughout the project lifecycle. A well-managed risk can become an opportunity; an unmanaged risk can become a project failure. Proactive risk management separates great PMs from average ones.

Risk Management Process

Step	Activity	Output	Example
1. Identify Risks	Brainstorm with team, review past projects, use risk checklists, stakeholder interviews	Risk Register with 15-30 identified risks	"Key developer may leave the project during sprint 4"
2. Assess Probability	Rate each risk likelihood: Low (1-3), Medium (4-6), High (7-10)	Probability score for each risk	"Developer leaving" = Medium (5/10) — happened once before in the org
3. Assess Impact	Rate impact severity: Low (1-3), Medium (4-6), High (7-10)	Impact score for each risk	"Developer leaving" = High (8/10) — no backup, critical knowledge
4. Prioritize	Risk Score = Probability x Impact; sort by score descending	Prioritized risk list	"Developer leaving" Risk Score = 5 x 8 = 40 (High Priority)
5. Plan Response	For each risk: Avoid, Mitigate, Transfer, or Accept	Risk response plans	Mitigate: Cross-train team members, document all code, pair programming
6. Monitor & Review	Track risks weekly, update probability/impact as project progresses	Updated risk register, weekly risk review	Track risk trigger indicators: dissatisfaction signals, job postings

Risk Response Strategies

4 Risk Response Strategies

AvoidEliminate the threat by changing the project plan. Example: Remove a risky technology component and use a proven alternative instead

MitigateReduce the probability or impact of the risk. Example: Add buffer time, cross-train team, implement automated testing, use fallback vendors

TransferShift the risk to a third party. Example: Buy insurance, outsource risky work, use fixed-price contracts, get SLA guarantees from vendors

AcceptAcknowledge the risk but take no action (for low-probability, low-impact risks). Example: Minor UI bug risk — accept and fix later if it occurs

Risk Management Golden Rule: Spend 5-10% of project management time on risk management. Review your risk register weekly in team meetings. The #1 mistake PMs make is not identifying risks early enough. Create a culture where team members feel safe to raise risks without blame. Address risks proactively — a risk discussed in planning is a problem solved; a risk discovered during execution is a project crisis.

🎯

Project Management Interview

Common Q&A

Preparing for a project management interview? Below are the most commonly asked questions with frameworks for impressive answers.

Top 15 PM Interview Questions

Question	Key Points to Cover
What is the difference between Agile and Waterfall?	Waterfall: linear, sequential, heavy documentation, resistant to change. Agile: iterative, incremental, welcomes change, working software over documentation, continuous feedback. Use examples from your experience.
How do you handle a project that is behind schedule?	1) Identify the root cause (scope creep, resource issues, technical debt). 2) Communicate transparently with stakeholders. 3) Re-prioritize: what can be cut or deferred? 4) Add resources if possible. 5) Crash or fast-track the schedule. 6) Update the plan and communicate new timeline.
How do you handle scope creep?	Document all change requests formally. Evaluate impact on time, cost, and quality. Present options to stakeholders with trade-offs. If approved, update the project plan. If not, defer to next phase. Always maintain a change log.
What is your approach to stakeholder management?	Identify all stakeholders using a power-interest matrix. Map: high power + high interest (manage closely), high power + low interest (keep satisfied), low power + high interest (keep informed), low power + low interest (monitor). Communicate proactively.
Describe a project that failed. What did you learn?	Use STAR method. Be honest about the failure but focus on learnings and what you would do differently. PMs who cannot admit failure are red flags. Show growth mindset and resilience.
What tools and techniques do you use for estimation?	Analogous (compare to similar past projects), Parametric (mathematical models), Bottom-up (estimate each task individually), Three-point (optimistic, pessimistic, most likely), Planning Poker (team consensus). Always add buffer (10-20%).
How do you motivate a team?	Understand individual motivations (not everyone is motivated by money). Provide clear goals and autonomy. Recognize achievements publicly. Remove impediments. Create a safe environment for experimentation. Lead by example. Build team rituals and culture.

PM Certification Guide (India): PMP (Project Management Professional) from PMI: most recognized globally, requires 36 hours of training + 4,500 hours PM experience + pass 180-question exam. Cost: $555 (₹46,000). CSM (Certified ScrumMaster) from Scrum Alliance: 2-day training + pass exam. Cost: $1,000-1,500 (₹80,000-1,20,000). SAFe Agilist: for scaled Agile in enterprise. Cost: $995. All are valuable for Indian PM roles — PMP is most versatile.

⏳

Loading cheatsheet...

Constraint

Description

How It Affects Others

Example

Scope

What needs to be delivered — features, deliverables, requirements

Increasing scope increases time and cost; decreasing scope reduces time and cost

Client adds 5 new features mid-project: timeline extends by 3 weeks, budget increases by 20%

Time

The schedule and deadlines for project completion

Shortening time increases cost (overtime, more resources) or reduces scope

Boss wants delivery 2 weeks earlier: either hire more developers (cost+) or cut 2 features (scope-)

Cost

The budget available for the project including resources, tools, and materials

Reducing budget increases time or reduces scope/quality

Budget cut by 30%: either extend timeline by 2 months or deliver fewer features with same team

Quality

The standard of deliverables — often considered the center of the triangle

Trade-offs among scope, time, and cost directly impact quality

Rushed project (time-) with reduced budget (cost-) results in buggy software (quality-)

Methodology

Approach

Flexibility

Best For

Key Characteristics

Waterfall

Linear, sequential phases

Low — changes are costly

Construction, manufacturing, regulated industries

6 phases: Initiation, Planning, Execution, Monitoring, Testing, Deployment; documentation-heavy

Agile

Iterative, incremental delivery

High — adapt to change

Software, product development, creative projects

Sprints (1-4 weeks), daily standups, sprint reviews, continuous feedback and improvement

Scrum

Agile framework with defined roles and ceremonies

High

Software development, product teams

Product Owner, Scrum Master, Developers; Sprints, Backlog, Daily Scrum, Sprint Review, Retrospective

Kanban

Visual workflow, continuous flow

Very High

Support teams, ops, continuous delivery

Kanban board (To Do, In Progress, Done), WIP limits, pull system, continuous delivery

Hybrid

Combines Waterfall planning with Agile execution

Medium

Large organizations, enterprise projects

Waterfall for planning/budgeting, Agile for development/execution; best of both worlds

PRINCE2

Process-based, structured methodology

Low-Medium

Government projects, large enterprises in UK/Europe/India

7 principles, 7 themes, 7 processes; emphasis on business justification and defined roles

Lean

Minimize waste, maximize value delivery

High

Manufacturing, startup MVPs, process optimization

Eliminate Muda (waste): overproduction, waiting, defects, overprocessing, inventory, motion, transport

Value

Over

What It Means in Practice

Individuals and Interactions

Processes and Tools

Trust and empower your team; face-to-face communication over documentation; people over rigid processes

Working Software

Comprehensive Documentation

Deliver a working product every sprint; working software is the primary measure of progress; documentation supports, not replaces, working code

Customer Collaboration

Contract Negotiation

Involve customers throughout the project; get feedback every sprint; adapt to changing requirements instead of following a fixed contract rigidly

Responding to Change

Following a Plan

Embrace change as a competitive advantage; re-prioritize backlog every sprint; the plan is a guide, not a contract

Role

Responsibilities

Common Anti-Patterns

India Market Context

Product Owner

Owns the product backlog, defines priorities, ensures business value, accepts/rejects work, represents stakeholders

Being a order taker instead of decision maker, not available for questions, overcommitting the team

Often played by business analyst or product manager; salary: 15-35 LPA in India

Scrum Master

Facilitates Scrum events, removes impediments, coaches the team on Agile, shields team from external distractions

Acting as a project manager (bossing team), micro-managing developers, ignoring team dynamics

Average salary: 12-25 LPA; high demand in Indian IT sector; certification: PSM I from Scrum.org

Development Team

Self-organizing, cross-functional team of 3-9 people who do the actual work of delivering the product increment

Waiting for instructions instead of self-organizing, not collaborating, gold-plating features

Typically includes: frontend dev, backend dev, QA, UI/UX designer; team size 5-8 is optimal

Event

Frequency

Duration

Purpose

Who Attends

Sprint Planning

Start of every sprint

2 hours (2-week sprint)

Define sprint goal, select backlog items for the sprint, create sprint backlog with tasks

PO, SM, Dev Team (entire Scrum Team)

Daily Scrum / Standup

Every day

15 minutes max

Answer 3 questions: What did I do yesterday? What will I do today? Any impediments?

Dev Team (SM facilitates but does not answer)

Sprint Review

End of sprint

2 hours (2-week sprint)

Demo completed work to stakeholders, collect feedback, update product backlog based on feedback

Scrum Team + Stakeholders

Sprint Retrospective

After Sprint Review

1.5 hours (2-week sprint)

Reflect on the sprint: what went well, what to improve, actionable items for next sprint

Scrum Team only (no managers/stakeholders)

Backlog Refinement

1-2 times per sprint

1-2 hours

Clarify, estimate, and prioritize backlog items; break large items into smaller ones

PO + Dev Team (SM optional)

Practice

Description

How to Implement

Benefits

Visualize Workflow

Make all work visible on a Kanban board with columns for each stage

Create columns: Backlog, To Do, In Progress, Review, Done; use physical board or digital (Trello, Jira)

Everyone sees the status of all work at a glance

Limit Work in Progress (WIP)

Set maximum number of items allowed in each column at any time

Set WIP limits per column: To Do (5), In Progress (3), Review (2); do not pull new work until capacity is available

Prevents multitasking and overloading; improves focus and quality

Manage Flow

Monitor, measure, and optimize the flow of work through the system

Track cycle time (start to finish), lead time (request to delivery), throughput (items per week)

Identify bottlenecks and optimize process continuously

Make Policies Explicit

Define clear rules for how work moves through the system

Define: Definition of Done, pull criteria per column, escalation process, priority rules

Reduces confusion, improves consistency and quality

Implement Feedback Loops

Regular reviews of the Kanban system and its effectiveness

Weekly Kanban review meeting, monthly metrics review, continuous improvement suggestions

Ensures the system evolves with the team and project needs

Improve Collaboratively

Use data-driven experiments to make incremental improvements

Identify the biggest bottleneck, propose a change, measure the impact, iterate

Continuous improvement culture; measurable gains over time

Tool

Best For

Pricing

Key Features

Learning Curve

Jira

Software development, Scrum teams

Free (up to 10 users), $8.15/user/mo

Sprint planning, backlog management, sprint boards, reports, automation, integrations

Medium — powerful but complex

Trello

Visual project management, small teams

Free, $5/user/mo (Standard)

Kanban boards, cards, lists, Power-Ups, automation (Butler), calendar view

Low — easiest to learn

Asana

Cross-functional project management

Free (10 users), $10.99/user/mo

Tasks, projects, timelines, portfolios, workflows, automation, reporting

Low-Medium — intuitive interface

Monday.com

Work management, no-code workflows

Free, $9/seat/mo

Customizable boards, automations, dashboards, integrations, Gantt charts

Low — visual and user-friendly

Notion

All-in-one workspace (docs + PM)

Free, $8/user/mo

Databases, docs, wikis, Kanban boards, templates, collaboration, API

Low-Medium — flexible and powerful

ClickUp

All-in-one PM (docs, goals, time)

Free (100MB), $7/user/mo

Docs, tasks, goals, whiteboards, time tracking, dashboards, automations

Medium — feature-rich but can be overwhelming

Linear

Modern software teams

Free (10 users), $8/user/mo

Issue tracking, sprints, cycles, roadmap, GitHub/GitLab integration, keyboard-first

Low — minimalist and fast

Microsoft Project

Enterprise, traditional PM

$10/user/mo

Gantt charts, resource management, portfolio management, reporting, integration with MS ecosystem

High — enterprise-grade complexity

Step

Activity

Output

Example

1. Identify Risks

Brainstorm with team, review past projects, use risk checklists, stakeholder interviews

Risk Register with 15-30 identified risks

"Key developer may leave the project during sprint 4"

2. Assess Probability

Rate each risk likelihood: Low (1-3), Medium (4-6), High (7-10)

Probability score for each risk

"Developer leaving" = Medium (5/10) — happened once before in the org

3. Assess Impact

Rate impact severity: Low (1-3), Medium (4-6), High (7-10)

Impact score for each risk

"Developer leaving" = High (8/10) — no backup, critical knowledge

4. Prioritize

Risk Score = Probability x Impact; sort by score descending

Prioritized risk list

"Developer leaving" Risk Score = 5 x 8 = 40 (High Priority)

5. Plan Response

For each risk: Avoid, Mitigate, Transfer, or Accept

Risk response plans

Mitigate: Cross-train team members, document all code, pair programming

6. Monitor & Review

Track risks weekly, update probability/impact as project progresses

Updated risk register, weekly risk review

Track risk trigger indicators: dissatisfaction signals, job postings

Question

Key Points to Cover

What is the difference between Agile and Waterfall?

Waterfall: linear, sequential, heavy documentation, resistant to change. Agile: iterative, incremental, welcomes change, working software over documentation, continuous feedback. Use examples from your experience.

How do you handle a project that is behind schedule?

1) Identify the root cause (scope creep, resource issues, technical debt). 2) Communicate transparently with stakeholders. 3) Re-prioritize: what can be cut or deferred? 4) Add resources if possible. 5) Crash or fast-track the schedule. 6) Update the plan and communicate new timeline.

How do you handle scope creep?

Document all change requests formally. Evaluate impact on time, cost, and quality. Present options to stakeholders with trade-offs. If approved, update the project plan. If not, defer to next phase. Always maintain a change log.

What is your approach to stakeholder management?

Identify all stakeholders using a power-interest matrix. Map: high power + high interest (manage closely), high power + low interest (keep satisfied), low power + high interest (keep informed), low power + low interest (monitor). Communicate proactively.

Describe a project that failed. What did you learn?

Use STAR method. Be honest about the failure but focus on learnings and what you would do differently. PMs who cannot admit failure are red flags. Show growth mindset and resilience.

What tools and techniques do you use for estimation?

Analogous (compare to similar past projects), Parametric (mathematical models), Bottom-up (estimate each task individually), Three-point (optimistic, pessimistic, most likely), Planning Poker (team consensus). Always add buffer (10-20%).

How do you motivate a team?

Understand individual motivations (not everyone is motivated by money). Provide clear goals and autonomy. Recognize achievements publicly. Remove impediments. Create a safe environment for experimentation. Lead by example. Build team rituals and culture.