Home

Welcome to the quality-time wiki! Configuring Metrics

What is Quality-time ?

Most application dashboards and monitoring tools are meant to be used when the application is in operation or production. Quality-time is unique because it monitors the quality and quality care of software in development. It combines all sources in and around a build pipeline, repository and workflow board.

Why Quality-time ?

For both software development teams and their surrounding organisation, it can be a demanding task to keep delivery high quality software that meets the respective quality requirements. Installing and configuring tools in the pipeline to scan the built software is one thing, but combining all the data and acting on the issues accordingly is another thing. Quality-time saves time by guiding the focus of the software development team to what should be dealt with now and later.

Why this wiki?

While the official documentation describes thoroughly how to deploy, develop and configure Quality-time, it can still be overwhelming to start from scratch. The official documentation does not provide guidance on where to start and how to apply and configure team agreements, the way of working and the targets of non-functional requirements in your quality report.

While this wiki is mainly developed by employees of the Dutch government organisation ICTU, this wiki aims to be neutral as does Quality-time itself, so it can be used for all organisations that develop bespoke software.

How to use this wiki?

When starting with an empty report refer to the getting-started guide. When already having a report and wanting to make it more effective, refer to Using-missing-metrics or the Configuring Metrics guide.