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:
- Extract values needed to calculate lead an cycle times.
- Basic visualization.
- Create visualization that allows to do predictions.
- 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
Comments
-
over 4 years ago by jochenbreuer | Reply
To get a visualization of lead vs cycle time, see this: https://paste.opensuse.org/view/raw/97296568
-
over 4 years ago by jochenbreuer | Reply
A gist to query Github via graphgl is here and the Github project can be found here.
Similar Projects
Improved Product Development Process by rtsvetkov
[comment]: # (Please use the project descriptio...
Collect flaky test cases identified by the team in a GitHub board and highlight them in the Test report by oscar-barrios
Project Description
Flaky tests: Th...
Deep clean-up of the Uyuni documentation files by omaric
Project Description
This project is plann...
Avahi Integration and Network Connection by vojha
Avahi Integration and Network Connection
...
Collect flaky test cases identified by the team in a GitHub board and highlight them in the Test report by oscar-barrios
Project Description
Flaky tests: Th...
Test Results for openQA on GitHub by livdywan
Project Description
Jobs in openQA are us...