I have always felt that agile is really about values: Openness, Honesty, Courage, and Trust. Personally Whenever I remained true to these values things went OK. In those (rare) cases when I have given into temptation, danger was lurking.
|Thanks to Geek and Poke|
This cartoon illustrates a classic case. Three levels of management get three different answers about the state of the project. As the report moves up the management chain, its status changes from Red to Yellow to Green. Sound familiar?
Why does this happen? A project leader colleague of mine was literally afraid of losing his job if he told his managers the truth about his project. So he didn’t. Until one day, the truth could not be hidden any longer. Unfortunately, this was three days before a release party (which had to be canceled). Bad thing.
Did the impact of the truth get smaller as time went on? No. Did it become easier to deal with the problem as time went on? No. So why do people hide the truth? I think lack of trust (and the fear it inspires) is the root cause.
In another case, a ScrumMaster I know didn’t want to show the release burn down to the product owner or discuss how much the team had worked on the project during the first sprint. The team hadn’t met its goals for the sprint (and had spent much more time than planned on support duties from a previous project).
Why didn’t she want to show the P-O this information? “He’ll flip out when he sees the project is late after just one sprint.” I insisted and she made the information available. She was right, though. The P-O did flip out. And when he settled down, he and the relevant managers had a talk about the amount of support work the team was allowed to do, which eliminated the problem.
If someone is afraid of the consequences of being honest, then that person is more likely to tell people what they want to hear. An policy of trust implies that people can tell possibly unpleasant truths without fear of retribution.
A policy of openness means that all stakeholders in a project have a right to complete, correct and up to date information about the state of the project. It means that there is no good news and bad news, just facts, and we want to react to facts as soon as they become known. If you know the facts, you can deal with them.
Some of you may be thinking, “we can’t tell the customer about that.” If you think openness is a bad thing, consider the alternative. What are the consequences of a lack of openness? What will happen when the information eventually comes out? (Don’t worry, it will come out!) Can you have a policy of selective openness? And if yes, how will that impact your customer’s trust and how will that impact your business?
|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.|