Deriving and Validating Requirements Engineering Principles for Large-Scale Agile Development: An Industrial Longitudinal Study
This five-year longitudinal industrial study derives and validates six key requirements engineering principles for large-scale agile development through extensive qualitative research at Grundfos AB and cross-company expert evaluation with multinational organizations.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to organize a massive, city-wide music festival. You have hundreds of different teams: one group is setting up the stages, another is managing the food trucks, another is handling the security, and another is booking the bands.
Now, imagine if every team had their own idea of what "success" looks like. The food truck team thinks the festival is about gourmet tacos, while the security team thinks it’s a high-security lockdown, and the band team thinks it’s a wild rave. Without a shared set of "ground rules," the festival will turn into a chaotic mess where the stages don't fit the power supply, and the food trucks arrive on the wrong day.
This research paper is essentially a "Survival Guide" for large-scale companies trying to build complex things (like smart water pumps or massive software systems) using "Agile" methods.
The Problem: The "Agile" Chaos
"Agile" is a way of working where teams move fast, change direction quickly, and don't spend months writing giant instruction manuals. It works great for a small group of five people. But when you have thousands of people working on one giant product, "moving fast" can lead to everyone running in different directions.
In big companies, the "Requirements" (the list of what the product must actually do) often get lost in translation between the people building the hardware, the people writing the software, and the people talking to the customers.
The Solution: The Six North Stars
Instead of giving these massive companies a rigid, boring rulebook (which people usually ignore), the researchers spent five years studying a company called Grundfos. They discovered that instead of "Rules," these companies need "Principles"—think of them like North Stars. A rule tells you exactly which path to walk; a North Star just tells you which direction to head so you don't get lost.
Here are the six "North Stars" they found:
- Know the Map (Architectural Context): You can't just build a cool engine if you don't know if it's going into a car, a boat, or a plane. Every requirement must respect the "big picture" of how the whole system fits together.
- Don't Make it a Solo Act (Democratize RE): Requirements shouldn't be the job of one "Requirement Guru" sitting in a dark room. Everyone—the builders, the testers, the designers—needs to have a say and a responsibility. It’s a team sport.
- Pack Light (Minimum Viable Documentation): Don't write a 500-page manual that no one reads. Write just enough so that people don't get lost, but not so much that you spend all your time writing instead of building. It’s like a GPS: you need the directions, but you don't need a printed map of the entire continent.
- Progress Over Perfection (No Perfect Requirement): In a fast-moving world, trying to write the "perfect" instruction is like trying to catch a cloud with your hands. It’s better to write a "good enough" instruction and fix it as you learn more.
- Keep Polishing (Refine When Needed): As you build, you learn things. If you realize a requirement is wrong, change it! Don't be a slave to a plan that you already know is broken.
- Understand the "Why" and the "How" (Know the Why and How): Don't just build a button because someone asked for it. Know why the customer needs it (to solve a problem) and how it connects to the machine (the technical reality).
Why does this matter?
The researchers didn't just come up with these ideas in a classroom; they tested them in the "real world" with giant companies like Volvo, Ericsson, and Bosch.
The takeaway is simple: When you are building something massive, you don't need more bureaucracy; you need better guidance. By following these six principles, big companies can move as fast as a small startup without crashing into each other like bumper cars.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.