Overview
Scrum is straightforward conceptually but challenging to implement effectively. This FAQ addresses common questions from ScrumMaster and Scrum Product Owner training courses.
Frequently Asked Questions
How can Agile/Scrum be applied to Hardware or Solution projects?
Scrum development has limited application in pure hardware creation, though agile philosophy applies everywhere. Hardware modeling and planning can proceed iteratively, as can simulation software development. However, most hardware development follows a task flow. Scrum remains useful for teams creating hardware—they can maintain a Product Backlog, commit to sprint work, and conduct daily synchronization meetings.
Does Scrum conform to PMI standards?
Scrum and PMI serve different purposes. PMI represents project management methodology while Scrum is a framework for managing people and workflow—they are fundamentally different tools.
What is a typical implementation of change from waterfall to Scrum?
- Understand organizational culture
- Create transition team with vision and milestones
- Select pilot project
- Train relevant personnel
- Run multiple sprints with adjustments
- Evaluate results and refine approach
- Scale to additional teams
How do we handle people working across multiple projects?
The parallel project challenge exists regardless of methodology. The better approach seeks to complete work sequentially more efficiently rather than sustaining concurrent projects.
How many Scrum teams can one ScrumMaster manage?
This depends on the ScrumMaster's experience, team maturity, and product complexity. "Experienced ScrumMasters can work with more teams efficiently" but three teams represents a practical maximum in most cases.
Can Scrum handle complex solutions effectively?
Complex problems resist detailed upfront resolution due to numerous variables and assumptions. Agile Development addresses complexity by examining problems at high level, then solving components iteratively—potentially making some mistakes during development but spending less time on flawed initial designs.
Role of wikis or collaboration tools in Scrum
Collaboration tools support geographically distributed teams but cannot replace face-to-face communication.
Where does Scrum track risks and impediments?
Impediments appear on team impediment lists. Project risks use risk trackers or documents. Backlog-related risks integrate into item notes and story point estimates.
Must teams use User Stories or are Use Cases acceptable?
Scrum makes no specification regarding Product Backlog item format—tasks, features, scenarios, or defects all work.
How to handle high priority fires during a Sprint
High-priority defects enter the sprint directly; teams address them and adjust their commitment. High-priority opportunities either wait for the next sprint or trigger sprint replanning. Teams often swap lower-priority items for urgent new ones.
When do you plan for the next Sprint?
Backlog grooming workshops (60-90 minutes, once or twice weekly) prepare upcoming work without constantly interrupting the current sprint. This preparation enables efficient sprint planning sessions.
What metrics assess a ScrumMaster's performance?
Evaluation should consider multiple roles: ScrumMaster (team functionality), team member (sprint contribution), technical practitioner (skill development), individual (career goals), and employee (organizational alignment).
How to project final product when requirements change?
"If the requirements keep changing, the final product picture will change as well." Base projections on current knowledge and update as requirements evolve.
If a team runs smoothly, does the ScrumMaster run out of work?
No. Even high-performing teams leave room for improvement. The organizational impediment list and team performance optimization provide ongoing focus areas.
Author: Peter Category: Agile FAQs for SMs and POs Tags: csm, cspo, faq, frequently asked questions, product owner, scrummaster, training