Scrum Adherence Score Calculator for Cultural Institutions

A comprehensive tool designed to calculate an overall Scrum adherence score for different groups within a cultural institution. Built upon the principles of the Scrum methodology and the Taiga platform, this calculator ensures that each group's commitment and performance with respect to Scrum are quantified.

Table of Contents

• Background
• Parameters
• Formula Evolution
• Repository Contents
• Usage
• Contribute

Background

The Scrum Adherence Score Calculator emerged from the need to quantify the adherence of various groups within a cultural institution to the Scrum methodology. With the parameters and formula continually refined, this tool serves as a reliable metric of Scrum commitment.

Parameters

1. Sprint Planning (Factor A):

   • Function: fetch_a_value(pid)
   • Description: Evaluates the team's commitment for a sprint.
   • Formula: ratio of the story points of current sprint to the total number of hours committed by the team

2. Progress (Factor B):

   • Function: fetch_b_value(pid, tpid)
   • Description: Gauges the task completion rate within a sprint.
   • Formula: ratio of the done task points to the story points of the current sprint

3. Scrum Meetings (Factor C):

   • Function: fetch_c_value(pid)
   • Description: Assesses the quality and consistency of daily Scrum meetings.
   • Formula: average score of daily scrum meetings

4. Release (Factor D):

   • Function: fetch_d_value(pid, did, cid)
   • Description: Determines the success rate of user story completions in a sprint.
   • Formula: ratio of the story points of completed user stories to the total story points of the current sprint

5. Team Raw Contribution (Factor E):

   • Function: fetch_e_value(pid)
   • Description: Determines the contribution of the team in relation to the total story points that are completed as whole in the current sprint.
   • Formula: ratio of the story points of completed user stories for a specific department to the story points of completed user stories for all departments in the current sprint

6. Relative Team Productivity (Factor R2):

   • Function: fetch_r2_value(pid)
   • Description: The Metric computes the average story points completed per team member of a specific project and then normalizes it by the average story points completed per team member across several projects in the organization.

Formula Evolution

This section provides a history of the various changes made to both the parameters and the overarching formula. By documenting the iterative refinement process, we ensure transparency and traceability in our methodology.

Repository Contents

• SQL Queries:
  • Factor A Query
  • Factor B Query
  • Factor C Query
  • Factor D Query
  • Factor E Query
  • Factor R2 Query

Usage

1. Execute the SQL queries for Factors A through R2.
2. Create the view in the database.
3. The data shown in your visualization tool (e.g. Metabase) is now retrieved from the view and is ONLINE!

Detailed steps can be found in the usage guide or inline instructions in the Python script.

Contribute

Contributions, feedback, and improvements are welcome. To contribute:

1. Fork the repository.
2. Create a new branch.
3. Submit your changes with a descriptive commit message.
4. Open a pull request.

---