HKSM

A trial project is a short, low-risk initiative selected to pilot Scrum in an organization, validate practices, and gather evidence for wider adoption. It is chosen early by sponsors or the Scrum Guidance Body and then used as input to initiate and run Scrum processes. Outputs from the trial include lessons learned, refined working agreements, and adoption recommendations.

Key Points

• Selected as a low-risk pilot to apply Scrum and learn before scaling across the organization.
• Acts as an input to Initiate processes such as Create Project Vision, Identify Scrum Master and Stakeholder(s), and Form Scrum Team.
• Approved by a sponsor or Scrum Guidance Body, with clear timebox, scope boundaries, and success criteria.
• Runs through normal Scrum events and artifacts to produce real increments and measurable outcomes.
• Outputs include lessons learned, updated Definition of Done, process tailoring, and recommendations for broader rollout.
• Ties into Retrospect Sprint and Retrospect Project for institutional learning and updates to organizational guidelines.

Purpose

The trial project demonstrates the feasibility and value of Scrum in a controlled environment. It reduces organizational risk by limiting scope and duration while generating real delivery and actionable learning.

It builds stakeholder confidence, tests team structure and tooling, and informs decisions on scaling Scrum to other projects or programs.

Key Terms & Clauses

• Timebox: Fixed duration for the pilot (for example, 2-3 sprints of 2 weeks each).
• Scope Boundaries: Clear, minimal scope that can deliver one or more potentially shippable increments.
• Success Criteria: Measures such as predictability of velocity, product quality, stakeholder satisfaction, and team stability.
• Governance: Sponsor and Scrum Guidance Body oversight, with check-in points and a go/scale/stop decision at the end.
• Learning Objectives: Specific adoption hypotheses to test (for example, estimation approach, Definition of Done, tooling).
• Constraints: Limits on budget, team size, dependencies, and technology to keep risk manageable.

How to Develop/Evaluate

Select the trial by applying criteria: moderate complexity, low external dependencies, supportive Product Owner and stakeholders, and ability to deliver incremental value. Confirm organizational readiness through a lightweight checklist covering roles, tooling, and access to users.

Define a short charter capturing objective, timebox, high-level scope, success metrics, and governance. Evaluate during and after the pilot using sprint metrics, defect trends, stakeholder feedback, and retrospective insights to determine whether to scale, adjust, or halt adoption.

How to Use

Use the approved trial project as an input to start Initiate processes: create the Product Vision, identify the Scrum Master and key stakeholders, form the Scrum Team, develop epics and user stories, and build the Prioritized Product Backlog. Conduct Release Planning for the pilot timebox and agree on the initial Definition of Done and team working agreements.

During execution, run normal Scrum events and track empirical metrics. After completion, feed outputs into Retrospect Project, update Scrum Guidance Body guidelines, refine organizational Definition of Done, and provide a recommendation for scaling Scrum.

Example Snippet

Sample trial project charter elements:

• Objective: Validate Scrum for customer portal enhancements and establish a baseline velocity.
• Timebox: 3 sprints, 2 weeks each; team of 6 cross-functional members.
• Scope: 1 epic split into 8-12 user stories; at least two increments delivered to internal users.
• Success Criteria: Stable velocity by Sprint 3, < 5 escaped defects, stakeholder satisfaction score ≥ 4/5.
• Governance: Sponsor reviews at end of each sprint; final scale/go/stop decision after Sprint 3.

Risks & Tips

• Risk: Choosing a mission-critical effort for the pilot. Tip: Select a low-risk, value-bearing scope instead.
• Risk: Vague success criteria. Tip: Define measurable targets for predictability, quality, and satisfaction.
• Risk: Skipping Scrum events to rush delivery. Tip: Run the full Scrum cadence to get valid learning.
• Risk: No path to scale decisions. Tip: Establish go/scale/stop criteria and capture lessons in Retrospect Project.
• Risk: Over-customizing Scrum too early. Tip: Start with core Scrum practices, then tailor based on evidence.

PMP/SCRUM Example Question

A sponsor approves a trial project to pilot Scrum. What is the most appropriate next step for the Scrum Master to initiate the work?

1. Create a detailed WBS and baseline scope for the full year.
2. Facilitate the Create Project Vision session and help form the Scrum Team.
3. Negotiate fixed-date commitments for all epics before starting the first sprint.
4. Delay initiation until all dependencies are removed by other teams.

Correct Answer: B — Facilitate the Create Project Vision session and help form the Scrum Team.

Explanation: After the trial project is approved, it becomes an input to Initiate processes in SBOK. The Scrum Master should facilitate creating the Product Vision and forming the team rather than building a WBS or fixing dates upfront.