PM Fundamentals

Project Management FAQ: 50 Questions From New PMs

By Vact Published

Project Management FAQ: 50 Questions From New PMs

Starting a project management role means confronting a wall of terminology, frameworks, and expectations. This FAQ covers the 50 questions new PMs ask most frequently, organized by topic for quick reference.

Fundamentals (Questions 1-10)

1. What does a project manager actually do?

A PM defines project goals, creates timelines, allocates resources, manages risks, communicates with stakeholders, and ensures delivery meets expectations. The role sits at the intersection of planning, execution, and communication [1].

2. What is the project lifecycle?

Five phases: Initiation, Planning, Execution, Monitoring and Control, and Closure. Every project, regardless of methodology, moves through these stages. For a comprehensive walkthrough, see our project management guide.

3. What is a project charter?

A document that formally authorizes the project, defines its objectives, identifies key stakeholders, and establishes the PM’s authority. It is created during the Initiation phase and serves as the project’s founding document.

4. What is a stakeholder?

Anyone who is affected by or can influence the project: sponsors, end users, team members, executives, vendors, and regulators. Managing stakeholders is a core PM skill. Our stakeholder management guide covers this in depth.

5. How do I estimate how long a project will take?

Start with a work breakdown structure to decompose deliverables into tasks. Then estimate each task using techniques like analogous estimation (based on similar past work), three-point estimation (optimistic, pessimistic, most likely), or bottom-up estimation (sum of individual task estimates). Add 10-20% buffer for unknowns [2].

6. What is scope creep?

Uncontrolled expansion of project scope without corresponding adjustments to timeline, budget, or resources. It is the most common reason projects miss deadlines. Our scope management guide addresses prevention strategies.

7. What is a deliverable?

A tangible or intangible output produced by the project. Deliverables can be documents, software features, hardware components, or training materials. They are defined during planning and tracked during execution.

8. What is a milestone?

A significant point in the project timeline marking the completion of a major deliverable or phase. Milestones have zero duration and serve as progress checkpoints. See our milestone planning guide.

9. What is the difference between a program and a project?

A project has a defined start and end date with specific deliverables. A program is a collection of related projects managed together to achieve strategic benefits that would not be realized if managed individually.

10. Do I need a PMP certification to be a PM?

No. Many successful PMs have no formal certification. However, a PMP (Project Management Professional) credential from PMI demonstrates knowledge of PM principles and can strengthen your resume, especially for enterprise and government roles.

Methodologies (Questions 11-20)

11. What is Agile?

An iterative approach that delivers work in short cycles (sprints) and adapts plans based on feedback. See our Agile guide for a full introduction.

12. What is Scrum?

A specific agile framework that uses time-boxed sprints (1-4 weeks), defined roles (Product Owner, Scrum Master, Development Team), and ceremonies (planning, standup, review, retrospective). Our Scrum guide covers the full framework.

13. What is Kanban?

A visual workflow management method that uses boards, cards, and work-in-progress limits to manage tasks as they flow through stages. Read our Kanban guide.

14. When should I use Agile vs Waterfall?

Use Agile when requirements may change and stakeholders are available for regular feedback. Use Waterfall when requirements are fixed and regulatory compliance requires formal phase gates. See our Agile vs Waterfall comparison for a complete decision framework.

15. What is a sprint?

A fixed time period (typically 1-4 weeks) during which the team commits to completing a set of work items. Sprints are the basic unit of work in Scrum. Our sprint guide explains the full process.

16. What is a retrospective?

A meeting held at the end of each sprint where the team reflects on what went well, what went poorly, and what to improve in the next sprint. It is the primary mechanism for continuous improvement. See our retrospective guide.

17. What is the Definition of Done?

A shared understanding of what “done” means for a work item. It typically includes criteria like code complete, tested, documented, and reviewed. Our Definition of Done guide explains how to create one.

18. What is a product backlog?

A prioritized list of everything the product needs. The Product Owner maintains it, adding, removing, and reordering items based on business value and stakeholder feedback. See our backlog management guide.

19. What is velocity?

The amount of work a team completes in a sprint, measured in story points or task count. Velocity helps predict how much work the team can take on in future sprints. Our agile metrics guide covers this and other key measures.

20. What is SAFe?

The Scaled Agile Framework. It coordinates multiple agile teams working on large programs through Program Increments (8-12 weeks), PI Planning events, and portfolio-level alignment. See our scaling frameworks comparison.

Tools (Questions 21-30)

21. What PM tool should I use?

It depends on your team and workflow. Jira excels for software teams. Asana provides clean general-purpose PM. Monday.com offers ease of use for mixed teams. See our PM tools comparison for a detailed breakdown.

22. Can I manage a project in a spreadsheet?

Yes, for small projects with few dependencies. But as complexity grows, dedicated PM tools provide automation, collaboration, and reporting that spreadsheets cannot match.

23. What is a Gantt chart?

A horizontal bar chart showing tasks on the vertical axis and time on the horizontal axis. Bars represent task duration and arrows show dependencies. Our Gantt chart guide covers creation and best practices.

24. How much does PM software cost?

Free to ~$55+/user/month. Most tools offer free tiers for small teams. Entry-level paid plans range from $5-12/user/month. Enterprise plans are custom-priced. See our PM tool cost guide for current pricing.

25. Do I need a time tracking tool?

If you bill clients by the hour, manage contractors, or need to measure where time goes, yes. If your team’s work is measured by output rather than hours, time tracking adds overhead without much value.

26. What is a RACI matrix?

A chart that defines who is Responsible, Accountable, Consulted, and Informed for each task or decision. It eliminates ambiguity about roles and decision-making authority.

27. Should I use Slack for project management?

Slack is a communication tool, not a PM tool. Use it for quick discussions and notifications, but track tasks, deadlines, and project status in a dedicated PM platform. Read our Slack for PM guide.

28. What integrations matter most?

Calendar syncing, version control (for engineering teams), document storage (Google Drive, SharePoint), and communication tools (Slack, Teams). Our integration strategies guide covers this topic.

29. How do I get my team to actually use the PM tool?

Keep the tool configuration simple, make it the single source of truth (not one of many), lead by example, and remove competing systems. If the tool adds friction without obvious value, adoption will fail.

30. When should I switch PM tools?

When the current tool consistently blocks your workflow, when your team size outgrows the tool’s capacity, or when a critical feature gap cannot be solved by integrations. See our migration guide.

Planning and Execution (Questions 31-40)

31. How do I run a kickoff meeting?

Cover the project’s goals, scope, roles, timeline, communication plan, and risks. Share materials in advance. Leave time for questions. Our kickoff meeting guide provides a complete checklist.

32. What is a work breakdown structure (WBS)?

A hierarchical decomposition of the project into smaller, manageable pieces. The WBS is the foundation for scheduling, budgeting, and resource allocation. See our WBS guide.

33. How do I manage project risks?

Identify risks early, assess their probability and impact, create mitigation plans for high-priority risks, and monitor them throughout the project. Our risk management guide provides frameworks and templates.

34. How do I handle scope changes mid-project?

Use a formal change request process: document the change, assess its impact on timeline and budget, get stakeholder approval, and update the plan. Never absorb scope changes silently. See our scope change guide.

35. How often should I report project status?

Weekly for most projects. Daily for high-urgency or launch-phase work. Monthly for long-running programs with stable velocity. Match frequency to stakeholder needs and project risk. Our status reporting guide covers formats and cadences.

36. What do I do when a project falls behind schedule?

Diagnose the cause (scope creep, resource shortages, estimation errors, blockers). Then choose a response: reduce scope, add resources, extend the timeline, or improve efficiency. Communicate the situation to stakeholders immediately.

37. How do I prioritize competing projects?

Use a prioritization framework like RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must, Should, Could, Won’t), or weighted scoring. Our prioritization frameworks guide compares the major approaches.

38. How much buffer should I add to estimates?

10-20% for well-understood work with experienced teams. 20-30% for new technology, new team compositions, or ambiguous requirements. Never present buffer as padding; frame it as risk mitigation [3].

39. How do I close a project properly?

Deliver final outputs, get stakeholder sign-off, conduct a post-mortem, document lessons learned, archive project artifacts, and release team members. Our project closure guide provides a checklist.

40. What is the critical path?

The longest sequence of dependent tasks that determines the shortest possible project duration. Delays on the critical path directly delay the project. Our critical path guide explains how to calculate and manage it.

Team and Communication (Questions 41-50)

41. How do I run effective standups?

Keep them under 15 minutes. Each person answers three questions: What did I complete? What am I working on today? What is blocking me? Our standup guide covers formats and anti-patterns.

42. How do I manage a remote team?

Default to async communication, schedule focused synchronous time for decisions and collaboration, document everything in a shared wiki, and invest in team bonding rituals that work across time zones.

43. How do I handle conflict on my team?

Address it early and directly. Listen to both sides, focus on the work problem rather than personal dynamics, find common ground, and agree on next steps. Unresolved conflict poisons team velocity. See our team decision-making frameworks guide.

44. What is a communication plan?

A document defining who receives what information, how often, through which channels, and from whom. It prevents information gaps and reduces ad-hoc requests. See our communication plan guide.

45. How do I keep meetings productive?

Set a clear agenda, invite only necessary participants, assign a facilitator, start and end on time, and send written notes with action items after. Our effective meetings guide provides detailed techniques.

46. How do I onboard new team members mid-project?

Prepare a project brief, assign a buddy, schedule a walkthrough of the project board and documentation, and give them a small, well-defined first task. See our team onboarding guide.

47. How do I manage stakeholders who keep changing requirements?

Establish a change request process, show the impact of each change on timeline and budget, and get written approval before acting. If changes are constant, consider switching to an agile methodology where change is expected.

48. Should I use email or chat for project communication?

Chat for quick, time-sensitive exchanges. Email for formal communications, external stakeholders, and decisions that need a clear record. Neither replaces a PM tool for task tracking. Our email management guide covers best practices.

49. How do I measure team productivity?

Track output metrics (velocity, throughput, cycle time) rather than activity metrics (hours worked, tasks started). Our team productivity guide covers the measures that matter.

50. How do I prevent team burnout?

Monitor workload balance, protect focus time from meeting overload, recognize accomplishments, and create psychological safety for raising concerns. Sustainable velocity beats peak output every time. See our burnout prevention guide.

Key Takeaways

  • Every project follows five phases: Initiation, Planning, Execution, Monitoring, Closure
  • Choose your methodology based on requirement stability and stakeholder availability
  • PM tools should reduce friction, not add it; start with free tiers and upgrade as needed
  • Communication and stakeholder management consume more PM time than planning
  • Buffer is not padding; it is risk mitigation

Next Steps

Sources

[1] Wrike, “Project Management Frequently Asked Questions,” wrike.com/project-management-guide/faq

[2] PMI, “Project Planning: Frequently Asked Questions,” pmi.org

[3] Productive.io, “Top 6 Project Estimation Techniques in 2026,” productive.io/blog

Project management is a broad discipline. This FAQ covers fundamentals; consult the linked guides for detailed treatment of each topic.

Sources

  1. Project Management Institute — accessed March 2026
  2. Agile Alliance — accessed March 2026