SAFe Measure and Grow helps organizations evaluate business agility, choose improvement priorities, and check whether changes produce better outcomes. Current assessments follow the five SAFe Disciplines. An older seven-Core-Competency checklist should not be presented as the current assessment structure.
The current five-Discipline view
| Discipline | Questions it helps explore |
|---|---|
| Leadership and Culture | Are leaders, culture, learning, and change enabling adaptability? |
| Team and Technical Agility | Can teams build quality solutions and improve their way of working? |
| Product Development Flow | Does customer and product work move from idea to validated value? |
| Large Solution Integration and Delivery | Can multiple ARTs and suppliers create integrated solution evidence? |
| Lean Portfolio Management | Do strategy, funding, governance, and portfolio flow reinforce outcomes? |
Competencies address specific business problems
Competencies now sit within the Disciplines and provide a learning journey for a particular problem, such as accelerating product flow, organizing teams and ARTs around value, coordinating large-solution delivery, or managing portfolio investment. An organization should select relevant competencies instead of treating every capability as an identical maturity checklist.
Combine assessment with outcome and flow evidence
- Business and customer outcomes show whether value changed.
- Flow measures reveal delay, WIP, throughput, and predictability.
- Quality and reliability signals expose delivery-system health.
- Employee and customer feedback provides context behind scores.
- Competency evidence shows whether a targeted capability is improving.
A score is a conversation starter
Assessment numbers are vulnerable to optimism, fear, inconsistent interpretation, and target gaming. Facilitate discussion around evidence, disagreement, and examples. Preserve minority observations when they reveal a risk hidden by an average.
Run one improvement loop
- Choose the assessment scope and explain the decision it should support.
- Collect individual perspectives before group discussion where possible.
- Review evidence and select one or two material constraints.
- Define an improvement hypothesis, owner, measure, and review date.
- Run the change and inspect outcome, flow, quality, and human effects.
- Repeat the assessment only when enough time and evidence exist to learn.
Scaled Agile's current framework update history explains the move to Disciplines and competency-based business-problem guidance. Leaders can use AI-Empowered Leading SAFe training to build shared framework context before designing an improvement cycle.
Assess to choose improvement, not to produce a score
Measure and Grow assessments should create a shared view of strengths, constraints and next experiments. Scores are sensitive to participant selection, interpretation and psychological safety. Comparing business units as a league table encourages optimistic answers and hides context.
A responsible assessment cycle
- Define the decision the assessment will support.
- Include people from different roles and levels.
- Discuss evidence behind ratings.
- Select one or two bounded improvements.
- Review outcome, flow and qualitative evidence later.
Use the current discipline or competency assessment supplied by Scaled Agile, since names and groupings evolve. Record the version and date when reporting results.
Facilitate the conversation ethically
Explain the purpose, audience and use of results before collecting responses. Participants should know whether comments are anonymous, who can see raw data and how findings will influence decisions. Never use maturity ratings to evaluate individual performance or punish a group for reporting problems honestly.
During discussion, ask for observable examples and note where roles interpret a statement differently. The disagreement may reveal a more useful improvement opportunity than the average score. Separate facts, perceptions and hypotheses, then select experiments small enough to review.
Reassess with context
Record the assessment version, participants, date and important organizational conditions. When reassessing, compare both quantitative movement and qualitative evidence such as flow, quality, customer feedback or decision speed. A higher score without better outcomes may reflect familiarity with the questions rather than meaningful change. Conversely, a lower score can indicate greater candor. Treat the assessment as a learning instrument, preserve psychological safety and use current official guidance for the competency being examined.
