Evidence from scientific research, business failures, politics, military history and sports has proven over and over that a disciplined, systematic approach to achieving a goal has a greater chance of success than undisciplined processes. Full Stack Scrum™ initially enforces a system proven successful in multiple companies, and yet maximizes team empowerment over time relative to other systems.
Here are the key differences in FuSS™ from the way Agile is often practiced:
- The Agile Performance Standards.
- The part-time nature of the Product Owner and Scrum Master roles (under “Guidance Roles”).
- Extreme transparency through open meetings (“Scrum Ceremonies“) and accessible work trackers (“Choose a Tracker“).
- Backlog and user story grooming by the entire team working together (“Groom Stories“).
- Creation of task lists prior to the sprint start (“Take Them to Task“).
- No story points required: FuSS relies on labor-hour estimation at the task level for story sizing, and story or epic counts for longer-term prediction (see “Why use task hours instead of story points?“).
Note: Organizations already using points and able to meet the Agile Performance Standards are welcome to keep points.
- “Just enough, just in time” architecture documentation.
- Strict discipline around:
- Freedom of teams to revise or abandon most of the system once, and as long as, the Standards are met.