Scholars have studied for many years the challenges of integrating requirements traceability in Agile environments. The developed tools, frameworks, and models in the literature take a rather technical perspective on the problem. The scholars focus primarily on mechanisms that provide accurate and relevant information retrieval from the requirements database or analyze various techniques for creating valid links between requirements. Although the technical approach provides solutions to several scoped challenges, the scholars did not take into account the business goals, stakeholders’ needs, and business processes. In practice, the company resources, the development approach, and knowledge workers’ interests play a critical role in requirements traceability. As a result, multiple tradeoffs are required to develop a balanced and stable environment. In particular, the approaches are not in sync with agile development approaches, whereas the first requires documentation, the latter is focused on working software. Therefore, taking a business and management perspective on requirements traceability integration in Agile methodologies could bring new meaningful insights into solving existing challenges.

Management requires to make trade-offs between what is desirable and feasible given limited resources and the need to stay agile. As a result, a framework for making these trade-offs is developed. In addition, a model capturing the main elements needed for traceability is designed, which can be modified/customized by other companies to realize RT given the limitations (or no limitations) brought by resources and business goals/strategy.

This thesis presents the research on developing a suitable dashboard for Project ENHANCE following the design guidelines from Few and Eckerson, and the recommendations that follow from this process for dashboard design in a non-business context. Two mock-up dashboards were developed in Python, using the Dash library. this case study shows that the guidelines from Few and Eckerson for designing different dashboard types could only be partly applied to the non-business context of Project ENHANCE. This is due to the fact that Project ENHANCE largely aims for a different purpose of their dashboard than recognized by Few and Eckerson, as was discovered during the user requirements interviews. Furthermore, Few and Eckerson make no distinction between dashboards for internal audiences or external audiences, whereas comments in the evaluation survey demonstrated that this distinction can greatly influence dashboard design.A new type of dashboard is proposed based on the conducted research: the Communication & Learning dashboard.