Recently, I asked myself, “What does it mean for a company to be agile?” and came to the conclusion that “Agility is the ability to change your mind intelligently, based on new information.”
Why is the Waterfall so cumbersome, so un-agile, and why are companies stuck in the waterfall? One reason is Work in Progress. Let’s take the example of a large services company which provides its services to other large, institutional customers. A typical such organization might have:
Sales is selling services which the development team will work on, say, a year from now. Pre-Sales is writing specs for software which the development team will work on in 6 months. The development is working now to satisfy contracts that were signed over a year ago. And the QA is working on software that the development team “finished” 3 to 6 months ago and for which the contracts were signed as long as two years ago.
The pipeline is permanently full, it takes a long time to for wishes to be transformed into working features, and there is constant pressure to keep the flow moving (just like in fluid dynamics!). So the company has great difficulties changing priorities, because that means throwing away vast amounts of unfinished work, and that can be expensive!
So if WIP creates inertia which makes a company cumbersome, stiff, inflexible or worse, what would be the state of perfect corporate agility? Having no work in progress at all.
At the end of every sprint, a Scrum team should have no work in progress. The software is (potentially) shippable. If the Scrum Team has done its job well, all backlog items are “done”, there is no undone work, and there is nothing preventing the product owner from requesting a shipment. This is a natural point for changing priorities and direction.
As I understand Kanban, it emphasizes limiting WIP to improve flow. But the pipeline is never empty. The pressure is limited, but there is no point where there is zero WIP. Scrum provides natural points to set entirely new priorities: the planning for the new sprint.
Is Zero WIP something that customers value? One concrete expression of the Zero WIP approach is the “Money for Nothing, Changes for Free” contract. Since the project has Zero WIP the end of each sprint, there is no reasons not to accept changes in the product backlog, or for a fee, the cancellation of the rest of the project.
Are moments of Zero-WIP a desirable goal? Does this offer an important advantage to Scrum which is not achieved by the flow optimizing Kanban?
|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.|