Implement and document MVP KPIs

[janniclas]

Description
In this ticket we track and update, which KPIs, metrics, and data models we already have implemented and which ones we need to add.

How To

1. If you want to contribute a KPI implementation choose a ticket from the list below, assign it to yourself, and move it into the In progress column.
2. In general, we follow gitflow, so create a feature/[KPI NAME] branch based on the dev branch.
3. Check the linked documentation and make sure it is complete and sufficient. If not extend the documentation and submit these changes for review.
4. Check for dependent data and link it in the ticket (see Technical Debt #44 for an example).
5. Add your implementation
6. Submit a pull request, which links to the corresponding ticket (see Feature/developer focus #15 for an example).

Tickets

• Branch Uniqueness #21
• Build Failure Rate #22
• Coupling Of Components #23
• Developer #24
• Development Focus #25
• Fault Correction Capability #26
• Fault Correction Efficiency #27
• Fault Correction Rate #29
• Feature Completion Capability #28
• Feature Completion Efficiency #30
• Feature Completion Rate #31
• Issue #32
• Mean Fault Correction Efficiency #33
• Mean Feature Completion Efficiency #34
• Meant Time To Resolution #35
• Modification Correctness #36
• Modification Efficiency #37
• Organization #38
• Project #39
• Pull Request Complexity #40
• Pull Requests #41
• Release #42
• Release Cycle #43
• Technical Debt #44
• Test Coverage #45
• Time Idea To Market #46
• Time to Resolution #47