HKSM

Training is a tool and technique used in Scrum to build the skills and knowledge needed to deliver product backlog items and work effectively within the framework. It includes targeted workshops, coaching, pairing, and just-in-time learning driven by upcoming work and improvement needs. The result is reduced skill gaps, higher quality, and more sustainable throughput.

Key Points

• Targeted learning that addresses capability gaps impacting delivery and quality.
• Common triggers include retrospectives, onboarding, new technologies, process changes, or compliance needs.
• Formats include workshops, on-the-job coaching, pairing, spikes, communities of practice, and e-learning.
• Timeboxed and aligned with sprint goals; capacity is adjusted to accommodate learning.
• Facilitated by the Scrum Master; priorities are informed by the Product Owner and the team based on the product backlog.
• Produces improved competencies, refined working agreements, and better adherence to the Definition of Done.

Purpose of Analysis

The purpose is to analyze current and upcoming work to identify the specific skills the team and stakeholders need. By understanding gaps early, the team can plan focused learning that reduces defects, rework, and delays.

This analysis also ensures training investments are tied to product goals and measurable outcomes such as improved velocity, lower cycle time, and fewer escaped defects.

Method Steps

1. Identify gaps: Use retrospective insights, impediment logs, incident trends, and upcoming backlog items to spot capability gaps.
2. Prioritize needs: Rank learning topics based on risk, urgency, and value impact on near-term backlog items.
3. Select format: Choose workshops, pairing, coaching, spikes, or external courses to fit the topic and time constraints.
4. Plan and timebox: Schedule sessions around sprints and adjust team capacity; avoid jeopardizing the sprint goal.
5. Deliver and practice: Conduct training with hands-on exercises, pairing, and immediate application on real backlog work.
6. Capture learnings: Update checklists, working agreements, Definition of Done, and knowledge base entries.
7. Evaluate outcomes: Track skill adoption and product metrics over several sprints and refine the training plan.

Inputs Needed

• Product backlog, upcoming releases, and dependencies.
• Definition of Done, acceptance criteria patterns, and quality standards.
• Retrospective findings, impediment log, and risk register.
• Team skills matrix or competency assessment.
• Performance data such as velocity, defects, and cycle time trends.
• Available trainers, internal SMEs, and training catalog options.

Outputs Produced

• Training plan and schedule integrated with sprint capacity.
• Updated skills matrix and training records or badges.
• Refined Definition of Done, checklists, or standards based on new practices.
• Knowledge assets such as job aids, code templates, and playbooks.
• Improved delivery indicators observed over subsequent sprints.

Interpretation Tips

Evaluate training impact using both learning evidence and delivery outcomes. Look for sustained improvements across multiple sprints, not just immediate gains.

Favor practical, just-in-time learning tied to near-term backlog items. If capability gaps are structural or urgent, consider combining training with expert support or staffing changes.

Example

A team is about to deliver features requiring a new authentication protocol. In the previous sprint, defects were found during integration because the team lacked protocol expertise.

The Scrum Master arranges a half-day workshop with an internal SME, plans a technical spike in the next sprint, and pairs an experienced developer with a learner. The team updates its Definition of Done to include new security checks and sees fewer integration defects afterward.

Pitfalls

• Generic courses that do not align with the product backlog.
• Scheduling training without adjusting sprint capacity, risking missed sprint goals.
• One-and-done sessions with no hands-on application or follow-up.
• Chasing certificates instead of measurable delivery outcomes.
• Ignoring stakeholder or Product Owner training needs on new processes or tools.
• Using training as a substitute for critical expertise when immediate delivery is at risk.

PMP/SCRUM Example Question

During Sprint Planning, the team identifies a capability gap for an API integration scheduled in the next two sprints. What should the Scrum Master recommend to address the risk while protecting the sprint goal?

1. Extend the sprint length so the team can learn and deliver without changing scope.
2. Ask a senior engineer to complete the work alone to avoid slowing others.
3. Schedule targeted training and a timeboxed spike, adjust capacity, and keep scope realistic.
4. Request the Product Owner drop the integration from the release plan.

Correct Answer: C — Schedule targeted training and a timeboxed spike, adjust capacity, and keep scope realistic.

Explanation: Focused, just-in-time training with a spike enables learning and de-risks upcoming work while preserving the sprint goal through capacity and scope adjustments. Extending sprints, isolating work to one person, or removing scope without analysis are less effective or contrary to Scrum principles.