A practical measure of agility: What is the minimum time that a team (or a company) needs in order to deliver an increment of business value to its customers? This is more formally known as “minimum cycle time.”
Example: Your sprint duration is 4 weeks. So how long does it take to deliver an increment of business value (where that increment is doable in the course of a single sprint)?
Why? It’s clear the team needs the duration of one sprint to realize the functionality, but under normal circumstances, the team can only start processing a request when that requested is included in the planning meeting at the beginning of the sprint. So it has to wait until the start of the next Sprint. That duration depends on where you are in the current sprint: beginning, middle or end.
By mainting a constant 4 week sprint duration, you can guarantee to management or to customers an average response time of 6 weeks, and a worst case of 8 weeks. If the sprint duration is variable or not defined, it is very difficult to measure or calculate how agile the team is, which is probably a synonym for “not very”.
BTW – there are a variety of strategies for improving this measure of agility: shorter sprints, multiple teams with overlappying start dates (you’re never more than 2 weeks away from a sprint planning, so you average response time is reducted from 6 weeks to 5 weeks, and the worst case from 8 to 6 weeks).
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|mailchimp_landing_site||1 month||The cookie is set by MailChimp to record which page the user first visited.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_42152348_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|NID||6 months||NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|COMPASS||1 hour||No description|
|cookies.js||session||No description available.|
|S||1 hour||No description available.|
I’m new to scrum and agile development and we are working towards implementing this where I work.
Would you please explain this with a little more detail?
Thanks for the suggestion! As a first step, I put up a poll to see what scrum teams are actually doing.
Did you see my post How long to Sprint? It deals with many of these issues.
Or do you have a specific question?