Requirements management is an essential part of software development. This work emphasizes product management’s role in a software development environment. Product management represents customer to product development. By turning development projects towards an agile requirements management through communication and training, the project was a success, delivered on time but with challenges, namely resistance to change.

In this case study, by utilizing the action research strategy, qualitative data was gathered using a comprehensive questionnaire. Altogether 36 professionals took part in interviews, results were analyzed and an internal development project roadmap was developed. One of the target projects played an important pilot role during the internal development project. In this particular pilot project, changes were implemented into practice with a help of a project manager, leading architect and with a product manager who was also the mentor of this thesis work.

Continuous development of practices improves quality and at the same time operates as a reminder for maintaining existing good practices. The study indicated that better process quality can be received with relatively small changes in practices. By utilizing and implementing requirements hierarchy and a structured way of handling even large amount of requirements has been shown to improve management work. This also helps other stakeholders get a better understanding of products content. Consistent and harmonious stack of requirements are easier to manage. Collaboration and continuous communication reduces ambiguity.

A key finding of this study is that requirement’s continuous, systematic and collaborative management improves requirements quality. Better requirements quality with improved project practices are key factors in successful software development projects.