When all of the SUSE Manager squads switched from SCRUM to a Kanban we lost estimations and therefore also the ability to do predictions. But there are other ways to get insights that are even more reliable, since they are based on anecdotal data. The lead and cycle times of issues are the two most important here.

I'd like to extract those two for all of the issue from the spacewalk project and explore how they can be visualized in meaning- and helpful ways.

Steps:

  1. Extract values needed to calculate lead an cycle times.
  2. Basic visualization.
  3. Create visualization that allows to do predictions.
  4. Also explore other values like Reaction Time, Service Time, Response Time, Wait Time, Throughput.

Looking for hackers with the skills:

scrum kanban estimations leadtime cycletime projectmanagement graphql github

This project is part of:

Hack Week 18

Activity

  • over 2 years ago: okurz liked this project.
  • over 2 years ago: jochenbreuer added keyword "graphql" to this project.
  • over 2 years ago: jochenbreuer added keyword "github" to this project.
  • over 2 years ago: jochenbreuer started this project.
  • over 2 years ago: jochenbreuer added keyword "estimations" to this project.
  • over 2 years ago: jochenbreuer added keyword "leadtime" to this project.
  • over 2 years ago: jochenbreuer added keyword "cycletime" to this project.
  • over 2 years ago: jochenbreuer added keyword "projectmanagement" to this project.
  • over 2 years ago: jochenbreuer added keyword "scrum" to this project.
  • over 2 years ago: jochenbreuer added keyword "kanban" to this project.
  • All Activity

    Comments

    Similar Projects

    Requirements Management Tool on Graph Database by mknop

    Project Description

    Create a requirements...


    multipath-tools: improve CI by mwilck

    Project Description

    multipath-tools is ...