How to start with Flow Metrics using Cycle Time

Поділитися
Вставка
  • Опубліковано 10 січ 2024
  • In this video I talk about how to start with flow metrics. The answer to that is to calculate your cycle time. I show you why it is important, why it's the first step and exactly how to do it with examples from Jira and Time in Status by RVS using Excel for the calculations. It's quick and easy to do so check the video out and get started using data to help you improve your process and provide better reporting to both the team and leadership.
    UPDATE In this video I say that you cannot natively extract cycle time data from Jira but I have since found a way to do it natively, for free, no apps needed. Check out the video here on how to do it with Jira automation rules and some custom fields • Extract data from Jira...
    For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk
    Join my channel through memberships to get access to perks:
    / @theagileleangardener
    I now offer personal coaching and mentoring, head over to my website for subscription plans and pricing.
    www.spa-agile-consulting.co.uk
    Buy Me A Coffee:
    www.buymeacoffee.com/theagile...
    How to start using Monte Carlo Simulation for Sprints in Scrum
    • Monte Carlo Simulation...
    Monte Carlo Simulation for Scrum
    • Estimation in Scrum | ...
    How to use Flow Efficiency
    • What is flow efficienc...
    How to use work item age in Scrum
    • Scrum Metrics Ageing W...
    How to start using flow metrics in Scrum
    • How to start using Flo...
    Limit your work in progress and reduce your context switching
    • Limit work in progress...
    Agile Thoughts Playlist
    • Agile Thought Leadership
    Follow me on LinkedIn
    www.linkedin.com/comm/mynetwor...
    #theagileleangardener

КОМЕНТАРІ • 48

  • @johnterry7397
    @johnterry7397 6 місяців тому +9

    Fantastic overview of cycle time 👍

  • @vinventdepaul2401
    @vinventdepaul2401 6 місяців тому +7

    Excellent, looking forward to your big monte carlo update!

  • @user-sw2dj1us7f
    @user-sw2dj1us7f 6 місяців тому +5

    Your content is just amazing I can’t understand why you don’t have more subscribers, I’ll promote it as much as I can 👍

  • @user-kd2nn3qs6t
    @user-kd2nn3qs6t 6 місяців тому +8

    I really enjoy the style of your videos Steve keep it up - this one answered a few questions for me around percentiles thanks 👍

  • @JasonHaas-ur2sg
    @JasonHaas-ur2sg 6 місяців тому +4

    As others have said your channel deserves far more subscribers it's the best out there, keep it up, it'll happen 👍

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому +1

      Thank you that’s a lovely thing to say, yep it’ll happen eventually 😊😎

  • @cohouseasy5055
    @cohouseasy5055 6 місяців тому +1

    Been waiting for a good video on cycle time thanks its really helped 👍

  • @user-dp2gk7eb6m
    @user-dp2gk7eb6m 6 місяців тому +1

    Very well explained and it helped me with a percentile issue I was having, thanks! 👌

  • @AriK-sz6qu
    @AriK-sz6qu 6 місяців тому +3

    Awesome video really helpful thank you ❤

  • @steveang6790
    @steveang6790 6 місяців тому +1

    Yeah looking forward to that monte carlo update steve !

  • @GrahamHaughton-xm7qv
    @GrahamHaughton-xm7qv 6 місяців тому +1

    Fantatsic overview on how and why to use cycle time 👍

  • @paulgood3074
    @paulgood3074 6 місяців тому +1

    Great update on cycle time thanks 👍

  • @user-kh5ku9hu6l
    @user-kh5ku9hu6l 6 місяців тому +1

    Wow just wow, amazing video! ❤

  • @RickTonoli
    @RickTonoli 6 місяців тому +1

    Great video as usual, just wanted to add for Jira users not wanting to purchase a plug in, it is entirely possible to do it instead with Jira's automations and one or two additional custom fields, it's how I'm doing it at the moment.

  • @user-od5ni3qg4k
    @user-od5ni3qg4k 6 місяців тому +1

    Quality content as always 👍

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому +1

      Thank you it keeps me going when I hear such nice words, thank you 🙏👍

  • @user-pt6xc5ws7h
    @user-pt6xc5ws7h 6 місяців тому +1

    Awwweesome!!!!!!!

  • @liftyohands3795
    @liftyohands3795 6 місяців тому +6

    Thank you for the time and effort you put into your videos.
    Question: Have you heard of the platform NAVE? It’s used to track metrics such as lead/cycle time, WIA, Throughput, Monte Carlo etc.
    I’d love to get your thoughts on the platform.

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому +2

      Thank you that means a lot to me 🙏👍 No I haven’t heard of it but thank you for letting us know about it, I’ll check it out and report back 🙏👍

    • @dougslay96
      @dougslay96 6 місяців тому +1

      Do you happen to have a link to the NAVE app? I would like to compare it to ActionableAgile and the various Excel templates. Thank you!

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому +2

      I’m pretty sure it’s this getnave.com

    • @liftyohands3795
      @liftyohands3795 6 місяців тому

      Thank you. Looking forward to hearing your thoughts

  • @RudigerWolf-jo1pv
    @RudigerWolf-jo1pv 3 місяці тому +1

    Blocked Column is considered by many to be an anti-pattern. How about flagging a work item instead? This way the work item retains the context of what column it got stuck in.

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  3 місяці тому

      I would say use work item age charts daily and you’ll know if there may be a problem before it happens 👍

  • @syambangkok
    @syambangkok 4 місяці тому +1

    Hi,
    Do you only consider story issue type for calculating cycle time? Or do you consider all other types of issues (bugs & chores) as part of the cycle time calculation?

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  4 місяці тому

      I would only consider the same type to calculate cycle time. If all you’re doing is bugs then only consider bugs. But if your main work is for example stories but you do a few bugs I would only consider stories and exclude bugs from the calculation. The bugs have presumably come from previous stories so that cycle time has already been accounted for.

    • @syambangkok
      @syambangkok 4 місяці тому

      @@TheAgileLeanGardener how about chores or tasks ? Do you include them along with stories ?

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  4 місяці тому

      No, you only include the same ‘types’ of work.

    • @syambangkok
      @syambangkok 4 місяці тому +1

      @@TheAgileLeanGardener thank you very much for your response and keep sharing valuable content 😊. Good work!!! 💯

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  4 місяці тому

      Thank you I really appreciate that 🙏👍

  • @dougslay96
    @dougslay96 6 місяців тому +1

    Quick question. In your previous videos you recommended calculating cycle time on the number of calendar days and not business days. Why change that philosophy in this video?

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому

      Hi Doug, that’s a good question! I haven’t really changed my philosophy but a lot of people have been asking for it as well as some clients so I decided to provide a way. For me it’s a temperature check, it’s meant as a guide, not to be taken to the ‘exact day’. If you do that you can get overly obsessed with it rather than focusing on fixing the real issues. But. Some people want it as exact as it can possibly be.

    • @dougslay96
      @dougslay96 6 місяців тому +1

      I get that. I watched a video by Daniel Vacanti showing why using calendar days is more accurate, especially when using the info for MCS.
      I am looking at using ActionableAgile for all flow metrics and it still calculates it as calendar days.

    • @TheAgileLeanGardener
      @TheAgileLeanGardener  6 місяців тому

      Yep exactly. Also a lot of the people I work with work over weekends anyway.