Creating and practicing alignment on Team Guiding Principles across Scrum Teams

**Team Guiding Principles:**
-
**Simplicity is Essential**
* Use common components unless it can be justified
* Build “Like for Like” first
* Consider costs of features

**Satisfy Customers Through Early & Continuous Delivery**
* Get feedback and complete UX research
* Conduct co-design UX sessions

**Welcome Changing Requirements Even Late in the Build**
* Embrace uncertainty and acknowledge that even a late change can still bear a lot of value to the end customer

**Delivery frequently**
* Move goals to test and into market per sprint
* Working software

**Empowered and expect to communicate**
* Ask for help
* Self organization of teams

**Maintain a sustainable pace of work**
* Keep sprints small related to velocity and goals
* Keep Story’s to 2-3 days
* Keep Tasks to 1-2 days

The issue lists Team Guiding Principles but names no files, tests, or entry points. Start by clarifying whether the goal is to document these principles, create a shared practice, or both, and where the result should live. Done should be defined by an agreed artifact and a clear approach for alignment across Scrum teams.

Written by the indexing model from the issue text.