“These are the only ones
of which the news has come to Harvard.
There may be many others
but they haven’t been discovered.”
– Tom Lehrer, The Elements
While collecting feedback and materials for Ten Contracts, I received plenty of additional thoughts on what could go wrong. Top of the list were:
an agile or a classical basis? Do you need to collaborate effectively across more than one company border? Who is empowered to address systematic impediments to success? Who gets to make decisions?
Issues almost by definition crop up. This list will no doubt continue to grow. How can you handle risks?
Creating a product is a challenging endeavor. Things can go wrong. The client wants something different than you thought. The stakeholders change their minds. Therefore, dealing with risk is a normal activity in any project.
You handle risks in Scrum by limiting your commitment to a particular course of action to a relatively short period of time. During the sprint, you are committed. At the end of the sprint, you can change direction if necessary.
Each Sprint the Whole Team collaborates to identify the best step forward given the situation at hand.
Every Sprint, the Product Owner – who is financially responsible for the success of the project – can reflect on the current situation to re-prioritize features, request a release or even cancel development.
If the Product Owner is constrained by contract to keep developing toward the original goal, regardless of what is learned along the way, money could be wasted, or the time could be better invested doing something else. Fixed scope projects are usually not in the client’s interest and they are not agile.
If you want to get the whole list right away, you can get my book “Ten Agile Contracts: Getting beyond fixed-price, fixed-scope.” Or can click through the articles one by one…. Let’s start get started in the top 10 with Number 10 (and my personal favorite): Bullshit Risk!
|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.|