How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Scrum Team Selection Criteria

A structured technique used in SBOK to define and apply objective, product-focused criteria for assembling a cross-functional, self-organizing Scrum Team. It balances skills, availability, and collaboration qualities to ensure the team can deliver value each sprint.

Key Points

  • Used during team formation and refresh to guide who joins the Scrum Team.
  • Prioritizes cross-functional, T-shaped skills and the ability to collaborate.
  • Targets a small, stable team size to maximize communication and focus.
  • Emphasizes dedicated availability over part-time allocation.
  • Includes soft skills, agile mindset, and readiness to be self-organizing.
  • Considers domain, technology, compliance, and time-zone constraints.

Purpose of Analysis

This technique ensures the selected team can deliver the product vision and meet sprint goals without relying on heavy handoffs. It helps align staffing decisions with backlog needs, Definition of Done coverage, and real capacity rather than titles or seniority. It is most useful in Initiate or when scaling or re-forming teams between releases.

Method Steps

  1. Clarify product vision and high-level epics to understand capability needs.
  2. Define must-have vs nice-to-have criteria: skills, experience, certifications, and soft skills.
  3. Assess cross-functionality by mapping backlog work types to required competencies.
  4. Check candidate availability and dedication to avoid over-allocation and context switching.
  5. Balance the team for size, diversity, and T-shaped skill coverage; confirm DoD and compliance needs are covered.
  6. Validate collaboration fit: communication habits, openness, and willingness to self-organize.
  7. Confirm logistics: co-location or plan for distributed practices, tools, and time-zone overlaps.
  8. Document the selection rationale, onboarding plan, and any training or coaching gaps.
  9. Review with Product Owner and Scrum Master; invite team input and adjust as needed.

Inputs Needed

  • Project vision statement and high-level product roadmap.
  • Epic-level product backlog and anticipated work types.
  • Skills inventory and resource pool profiles.
  • Availability calendars and allocation constraints.
  • Quality, security, and regulatory requirements that influence team skills.
  • Organizational policies on location, budget, and tooling.

Outputs Produced

  • Scrum Team roster with confirmed roles: Product Owner, Scrum Master, Developers.
  • Skills coverage matrix showing cross-functional capability and gaps.
  • Initial team capacity baseline and availability notes.
  • Onboarding and enablement plan, including training or coaching needs.
  • Logistics setup: workspace or remote collaboration plan and tool access.

Interpretation Tips

  • Optimize for team effectiveness, not individual brilliance or job titles.
  • Prefer dedicated members over a larger number of part-time contributors.
  • Focus on T-shaped profiles to reduce handoffs and increase flow.
  • Include diverse perspectives to improve innovation and risk detection.
  • Expect to iterate on composition as the backlog and context evolve.

Example

An organization plans a new product with epics in payments, reporting, and user management. The Product Owner and Scrum Master apply criteria: small team size, cross-functionality across backend, frontend, testing, and DevOps, and at least one member experienced in PCI compliance. Candidates are screened for availability to dedicate full-time, collaborative behavior, and willingness to pair. A 7-person team is formed, a skills matrix reveals a test automation gap, and a 2-week onboarding plan with coaching is scheduled.

Pitfalls

  • Picking members by title or seniority instead of capability and collaboration.
  • Forming an oversized team to chase speed, which often reduces throughput.
  • Assigning members to multiple teams, causing context switching and delays.
  • Ignoring soft skills and agile mindset, leading to handoffs and silos.
  • Overfitting to the first release and neglecting adaptability for future work.
  • Underestimating distributed-team needs for time-zone overlap and tooling.

PMP/SCRUM Example Question

During Initiate, a Scrum Master and Product Owner are assembling a new Scrum Team. Which criterion best reflects effective use of Scrum Team Selection Criteria?

  1. Select the highest-rated individual performers regardless of collaboration history.
  2. Choose a cross-functional group with full-time availability that covers Definition of Done needs.
  3. Fill roles strictly by job titles to ensure clear handoffs between functions.
  4. Maximize headcount to increase velocity in the first sprint.

Correct Answer: B — Choose a cross-functional group with full-time availability that covers Definition of Done needs.

Explanation: The technique emphasizes cross-functionality, dedication, and quality coverage. Titles, individual ratings, and oversized teams do not ensure effective delivery.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Take Control of Project Performance!

HK School of Management helps you go beyond status reports and gut feelings. In this advanced course, you will learn Earned Value Management (EVM) to measure progress, forecast outcomes, and take corrective action. Learn how WBS quality drives performance, how control accounts work, and how to use EAC, TCPI, and variance analysis. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More