Extract lead and cycle times from Github
an invention by jochenbreuer
Updated almost 6 years ago. 1 hackers ♥️. 1 follower.

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 6 years ago: okurz liked this project.
  • over 6 years ago: jochenbreuer added keyword "graphql" to this project.
  • over 6 years ago: jochenbreuer added keyword "github" to this project.
  • over 6 years ago: jochenbreuer started this project.
  • over 6 years ago: jochenbreuer added keyword "estimations" to this project.
  • over 6 years ago: jochenbreuer added keyword "leadtime" to this project.
  • over 6 years ago: jochenbreuer added keyword "cycletime" to this project.
  • over 6 years ago: jochenbreuer added keyword "projectmanagement" to this project.
  • over 6 years ago: jochenbreuer added keyword "scrum" to this project.
  • over 6 years ago: jochenbreuer added keyword "kanban" to this project.
  • over 6 years ago: jochenbreuer originated this project.


    • Comments

    • jochenbreuer
      over 6 years ago by jochenbreuer | Reply

      To get a visualization of lead vs cycle time, see this: https://paste.opensuse.org/view/raw/97296568

    • jochenbreuer
      over 6 years ago by jochenbreuer | Reply

      A gist to query Github via graphgl is here and the Github project can be found here.

    Similar Projects

    The Agentic Rancher Experiment: Do Androids Dream of Electric Cattle? by moio

    Rancher is a beast of a codebase. Let's investigate if the new 2025 generation of GitHub Autonomous Coding Agents and Copilot Workspaces can actually tame it. A GitHub robot mascot trying to lasso a blue bull with a Kubernetes logo tatooed on it

    The Plan

    Create a sandbox GitHub Organization, clone in key Rancher repositories, and let the AI loose to see if it can handle real-world enterprise OSS maintenance - or if it just hallucinates new breeds of Kubernetes resources!

    Specifically, throw "Agentic Coders" some typical tasks in a complex, long-lived open-source project, such as:


    ❥ The Grunt Work: generate missing GoDocs, unit tests, and refactorings. Rebase PRs.

    ❥ The Complex Stuff: fix actual (historical) bugs and feature requests to see if they can traverse the complexity without (too much) human hand-holding.

    ❥ Hunting Down Gaps: find areas lacking in docs, areas of improvement in code, dependency bumps, and so on.


    If time allows, also experiment with Model Context Protocol (MCP) to give agents context on our specific build pipelines and CI/CD logs.

    Why?

    We know AI can write "Hello World." and also moderately complex programs from a green field. But can it rebase a 3-month-old PR with conflicts in rancher/rancher? I want to find the breaking point of current AI agents to determine if and how they can help us to reduce our technical debt, work faster and better. At the same time, find out about pitfalls and shortcomings.

    The Outputs

    ❥ A "State of the Agentic Union" for SUSE engineers, detailing what works, what explodes, and how much coffee we can drink while the robots do the rebasing.

    ❥ Honest, Daily Updates With All the Gory Details

    Is SUSE Trending? Popularity and Developer Sentiment Insight Using Native AI Capabilities by terezacerna

    Description

    This project aims to explore the popularity and developer sentiment around SUSE and its technologies compared to Red Hat and their technologies. Using publicly available data sources, I will analyze search trends, developer preferences, repository activity, and media presence. The final outcome will be an interactive Power BI dashboard that provides insights into how SUSE is perceived and discussed across the web and among developers.

    Goals

    1. Assess the popularity of SUSE products and brand compared to Red Hat using Google Trends.
    2. Analyze developer satisfaction and usage trends from the Stack Overflow Developer Survey.
    3. Use the GitHub API to compare SUSE and Red Hat repositories in terms of stars, forks, contributors, and issue activity.
    4. Perform sentiment analysis on GitHub issue comments to measure community tone and engagement using built-in Copilot capabilities.
    5. Perform sentiment analysis on Reddit comments related to SUSE technologies using built-in Copilot capabilities.
    6. Use Gnews.io to track and compare the volume of news articles mentioning SUSE and Red Hat technologies.
    7. Test the integration of Copilot (AI) within Power BI for enhanced data analysis and visualization.
    8. Deliver a comprehensive Power BI report summarizing findings and insights.
    9. Test the full potential of Power BI, including its AI features and native language Q&A.

    Resources

    1. Google Trends: Web scraping for search popularity data
    2. Stack Overflow Developer Survey: For technology popularity and satisfaction comparison
    3. GitHub API: For repository data (stars, forks, contributors, issues, comments).
    4. Gnews.io API: For article volume and mentions analysis.
    5. Reddit: SUSE related topics with comments.