Getting Real About Your Values – The Values Retrospective

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Bringing values down to earth

Values and principles can often seem lofty and intangible so many agile practitioners prefer to focus on tools and practices. That’s understandable but unfortunate. Because values and principles have the potential to provide us with clarity and guidance that transcends what practices and frameworks can achieve.  Ideally – part of your empiric inspection and adaptation process should explore whether you are living according to your values/principles. To achieve that you can try a value-based retrospective.

 

Values-based Retrospective – The TL;DR (Too long; Didn’t Read) version:

Create a matrix of your values as rows, and some classic retro categories such as plus/delta as columns. Then run a “generate insights” activity in which you try to see what you’re doing that upholds a value or flies in the face of it and could be improved. Afterward continue the retrospective as usual by deciding what to focus on, getting to the root cause, coming up with experiments, and committing to some change.

The Value of a Values-based Retrospective

This can help in a couple of ways:

  • Refresh the team’s recollection and understanding of the values/principles and their importance
  • Help you identify espoused values that you need to work on a bit (or a lot…)
  • Celebrate some values that are coherent with your actual behavior.
  • Identify impediments that are in your way to actually behave in a way that’s aligned with your espoused values.

Choosing Values to Focus On

One question you should probably be asking is “What values should I use?”

  • Your organizational/team values (assuming those are ones you feel are real and relevant – not just posters on the wall…)
  • Values of the agile approach you’re using – e.g. Scrum ValuesSAFe Values, values from the Manifesto for Agile Software Development
  • Values from a management approach you like – e.g. Daniel Pink’s Intrinsic Motivation– in this case, your values will be Autonomy, Mastery, and Purpose.
  • Decision filters like the Lean Decision Filter– in this case, your values will be Value, Flow, Eliminate Waste or the Agile Decision Filter – in which the values would be “making progress with imperfect information”, “treating WIP as a liability”, “encouraging a high-trust culture”

Regardless of what set of values you choose – make sure you understand the value of each value. E.g. how does the Scrum value “Courage” benefit you as a team? Why is it required in order to achieve high-performance? This can be a warm-up activity of the retrospective – each person trying to lay out his perspective on this and then sharing notes.

Improve Collaboratively Using Models

You could also use this retrospective style to bring in sets of values as models to look at while trying to improve. What I mean by that is you could run a retrospective using a certain set of values even if they’re not formally your values. For example, Even if you’re not doing Scrum, running a retrospective using the Scrum Values would be educational, would probably inspire some interesting discussions, and drive some useful experiments. In summary – running a values-based retrospective can be a great way to run a different style of a retrospective – one that is one hand focusing on the roots of what we’re trying to do and on the other hand grounded in our actual behaviors and what to do about them.

Subscribe for Email Updates:

Categories:

Tags:

Nexus and Kanban
Retrospectives
lean agile change management
SA
ScrumMaster Tales
Reading List
Agility
Agile
Effective Agile Retrospectives
Implementing SAFe
Scrum Guide
Acceptance Test-Driven Development
Portfolio for Jira
Video
Sprint Planning
Introduction to ATDD
Risk Management in Kanban
Lean Risk Management
IT Operations
Operational Value Stream
Program Increment
Agile Games
Nexus Integration Team
The Kanban Method
Implementation of Lean and Agile
Scaled Agile Framework
Nexus
Agile Israel Events
ALM Tools
Lean-Agile Software Development
Jira Plans
Sprint Retrospectives
Lean Agile Basics
RTE Role
Software Development Estimation
Agile Project
Story Slicing
SAFe
Games and Exercises
Advanced Roadmaps
Agile Community
Agile Product Ownership
Slides
Kanban Game
Rapid RTC
Agile Development
Scrum Primer
Tools
Self-organization
Perfection Game
Agile Techniques
Achieve Business Agility
Certification
AI
Scrum With Kanban
Product Management
Atlassian
Agile Testing Practices
Value Streams
Agile Product Development
Nexus and SAFe
Entrepreneurial Operating System®
SAFe Release Planning
Pomodoro Technique
ATDD vs. BDD
ROI
agileisrael
Legacy Enterprise
Lean-Agile Budgeting
Scrum and XP
Spotify
Lean and Agile Techniques
LAB
Agile Games and Exercises
Agile Outsourcing
PI Planning
Professional Scrum Master
Kanban
chatgpt
Agile Release Management
Release Train Engineer
Agile Israel
Code
Coaching Agile Teams
Change Management
PI Objectives
Agile Delivery
Sprint Iteration
Agile India
Amdocs
speed at scale
Quality Assurance
ART Success
Test Driven Development
An Appreciative Retrospective
LPM
Scrum Master
Kanban Kickstart Example
SPC
Risk-aware Product Development
Iterative Incremental Development
System Team
AgileSparks
Lean Agile Organization
RSA
Jira Cloud
Business Agility
speed @ scale
Lean and Agile Principles and Practices
Introduction to Test Driven Development
NIT
Continuous Delivery
BDD
Presentation
Principles of Lean-Agile Leadership
Scrum.org
Agile for Embedded Systems
Daily Scrum
Accelerate Value Delivery At Scale
Development Value Streams
transformation
Webinar
Engineering Practices
Releases Using Lean
System Archetypes
Agile Mindset
Managing Projects
Agile Release Planning
Atlaassian
Jira
Confluence
Tips
Built-In Quality
Large Scale Scrum
Software Development
Rovo
Agile in the Enterprise
ATDD
Keith Sawyer
WIP
Professional Scrum Product Owner
POPM
Lean Startup
Limiting Work in Progress
Agile Contracts Best Practices
Systems Thinking
Lean Agile
Lean Budgeting
Scrum Master Role
Agile Marketing
Manage Budget Creation
Applying Agile Methodology
A Kanban System for Software Engineering
What Is Kanban
Team Flow
System Integration Environments
Lean Agile Management
AI Artificial Intelligence
Enterprise DevOps
EOS®
Covid19
Frameworks
Scrum
The Agile Coach
Continuous Improvement
Managing Risk on Agile Projects
Scrum Values
Professional Scrum with Kanban
Nexus vs SAFe
Hybrid Work
DevOps
Process Improvement
Agile Risk Management
Product Ownership
Lean Software Development
predictability
Kanban Basics
SAFe DevOps
Planning
Legacy Code
Continuous Integration
Continuous Planning
Jira admin
ARTs
Certified SAFe
Artificial Intelligence
Elastic Leadership
Agile Program
RTE
Continuous Deployment
Kaizen Workshop
Agile Basics
Agile and DevOps Journey
Risk Management on Agile Projects
LeSS
User stories
Lean Agile Leadership
Kanban 101
GanttBan
Kaizen
Agile Project Management
Agile Assembly Architecture
TDD
QA
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart