Call for research · October and November 2026
Value in engineering teams
Engineering teams spend a large share of every company's budget, yet hours, story points and velocity measure effort, not value. We invite studies that show where value is created, lost or shifted in software and hardware engineering.
Questions we would like to see answered
- How do you measure the value a team delivers, not only its output?
- Where does anti-value appear: rework, incidents, technical debt, burnout, lost knowledge?
- How do priorities, estimates and roadmaps change when value is the unit?
- What happens to value at hand-offs between product, design, development, testing and support?
- How do AI tools change the value a team creates, and who receives it?
- Which practices reliably raise realized value, and which only raise activity?
What counts as research
- Case studies from your own team or company. Data can be anonymized.
- Comparisons of metrics or practices with a clear method.
- Experiments and pilots, including the ones that failed.
- Reviews of published studies with your own analysis.
Practitioners are welcome. No degree or affiliation is required. Works on other value topics are welcome at any time.
For an example of the format, read Measuring Value Flows in Software Delivery with the Value System Schema.
How it works
- Submit your work through the form. It takes two short steps.
- An independent expert reviews it and may ask for changes. Experts never review their own work.
- After publication, readers evaluate the work, and you see the value it gave them.
- The work is translated into 20 languages, and you receive an ÆVRI Researcher badge for your website or profiles.
The theme is open until 30 Nov 2026. Works received later are still reviewed.