The CTO - my good product friend - Erik Bjernulf and I spent one week in Karlskrona. We visited the World Conference for Requirement Engineering. Both Erik and I were to share some findings on how to work with product requirements. The conference gathered over 300 researchers in the field.

We listened to researchers from Brazil in how to handle requirements in partnerships. We were intrigued by Dutch professors in how to handle requirements on platforms, by Indian doctors to automate the work, and by Intel in dealing with landing zones. It was an intense week by design, a nerdy week for requirements geeks; we loved it.

As we drove home in Erik's extremely uncomfortable Porsche, we discussed the week. What do we bring with us? We ended up with 10 principles on how to evaluate how Requirement ways of working. It is almost like a checklist when designing a process or evaluating your way of working with requirements.

In addition, we should also look at the teams involved in doing the work. We have used the 10 principles both to evaluate requirement management work and to design it. It has proven helpful, and it has identified major problems and to fix them.

Attached is the tool and a very brief article on it where the 10 principles are grouped into 5 areas.