Blog / News


Last autumn, I wrote an article on how the words we use play a significant role in defining IT systems. Ambiguous sentences, slang and abbreviations, excessive storytelling, and the language barrier often cause comprehension difficulties. Texts need to be revised and edited a lot to make them clear and understandable to different stakeholders.

Traditionally, testing has been the last step in the development of the system before completion. In principle, therefore, it could not have been very agile because comprehensive testing requires a functional version of the entire system.

Defining requirements is basically a simple task. Listen to what the customer wants and write the requirements in a suitable format so that the developers can implement them. However, the task involves many challenges and potential pitfalls.

In this article, I gather my thoughts on defining requirements in hybrid projects that apply traditional project management combined with agile development methods. Today, such a model is a very common way of implementing software in, for example, large Finnish companies.