Changing Company Culture For Agile Project Management: Avoiding The “Can’t Ban” - PM 360 Consulting
17795
post-template-default,single,single-post,postid-17795,single-format-standard,wp-custom-logo,theme-bridge,woocommerce-no-js,ajax_fade,page_not_loaded,,qode-content-sidebar-responsive,columns-4,qode-theme-ver-11.0,qode-theme-bridge,wpb-js-composer js-comp-ver-5.1.1,vc_responsive

Changing Company Culture For Agile Project Management: Avoiding The “Can’t Ban”

Project Success and Failure

Changing Company Culture For Agile Project Management: Avoiding The “Can’t Ban”

Project Success and Failure

Yet another study has listed “culture” as the most difficult hurdle to an organization’s transformation. According to the survey of 1,100 software managers, “General organization resistance to change” (48%) and “Organizational culture at odds with Agile values” (44%) are two of the four top obstacles thwarting the improvement in project management. This is not new, however.

 

In 2015, Kugler Maag Cie conducted an Agile in Automotive Survey and found one of the major barriers was organizational culture. And Forbes’s 2011 article stated, “Changing an organization’s culture is one of the most difficult leadership challenges … [where] single-fix changes, such as the introduction of Kanban, Lean, Agile or Scrum … may appear to make progress for a while, but eventually the interlocking elements of the organizational culture take over and the change is inexorably drawn back into the existing organizational culture.”

Instead of Kanban, company cultures quietly and accidentally institute a “Can’t Ban”.

But what does “culture” mean, though? That term is so vague and amorphous that a high school chemistry teacher’s lecture might reference it or replace it by “bacteria” or “aberration”. To help make culture more tangible, here are four examples of anti-Agile cultures that have been personally experienced within the auto industry and avoidance strategies for teams witnessing such organizational dysfunction.

Young brazilian woman In hurry pointing to watch time, angry for deadline delay

“I understand your urgent project is out of control, but ours isn’t because we controlled it.” High-profile emergencies steal team members, capacity and time away from the important transformation.

The Urgent Trumps The Important

Those readers familiar with Stephen Covey’s “The 7 Habits of Highly Effective People®” know the basic premise: If something is urgent, it will naturally pull attention away from the important because of its burning need. Improving a way of working akin to Agile constitutes important, but disaster is urgent and scary. That malevolent interruption usually comes in the form of flailing coworkers on a different project about to miss a near-term delivery and/or at the brink of a plant-shutdown. These high-profile emergencies force executives into knee-jerk reactions that override any improvement strategies. The common mistake: reorg key firefighters from the Agile team to extinguish the raging blaze elsewhere, thereby creating a dysfunctional hole on the healthy project. The result is mistrust between the supposedly-empowered team and the poorly-supporting managers.

Strategy to Overcome:  Emergency assistance can be applied without breaking up the band. In the scenario where another team needs help, the whole Agile team may apply a portion of its upcoming development time to the higher-priority work. This would result in applying less effort on the current project, but tradeoffs are the very foundation of Agile and build transparency via plotting the effects downstream. “If we do this supposedly critical item, then we cannot deliver this lower-priority item until much later. OK?”

 

If They Can’t Figure Out, The Adults Will Step-In

Frequently managers’ lip-service supports empowerment until they feel things have stopped proceeding according to their Fantasyland expectations. Therein, a “catastrophe” arises on the Agile team’s current project, and the management’s misguided, cultural gaffe is to dictate a solution. Sometimes that’s rigid oversight including attendance and domineering the team meetings — a.k.a. “getting things back into shape” — or maybe it’s the worst-case scenario of falsely imposing a desired velocity to supposedly beat the crisis. In this case, the director dictates an efficiency 20-30% higher than what the team can naturally achieve. The team quickly realizes the difficulty with that inflated number and works significant overtime to temporarily achieve the expectations. However, “shock the cage” jumping isn’t sustainable, and either turnover, illness or both turn the velocity southward after a few weeks. The results are usually missed deadlines, disgruntled teams, and a failed improvements. The end of the organization’s improvement initiative mirrors its foolish beginning, i.e. zero improvement (at best).

Strategy to Overcome:  When facing an impossible, near-term deadline, there are three scenarios towards healthy resolution: 1) add new team members, 2) re-negotiate the deadline or 3) throw off ballast. The trickiest is probably adding new team members since this usually doesn’t happen quickly, may upset the project’s business case and many times can reduce the throughput of the team.  Renegotiating the deadline seems equally improbable, but this happens occasionally by either downloading software after delivery or retrofitting prototypes after assembly. The last strategy is the most probable: making hard decisions upon as a holistic team about what development is presently ballast and can be postponed until a later delivery. Does that slightly-nagging defect have to be eradicated for this build or could it wait? Could regression testing substitute for the full integration or qualification testing for now? Making these decisions with all stakeholders – possibly including the customer – will help with the cultural aspects of transparency and trust.  Management can help facilitate discussion but should avoid being heavy-handed.

 

Interruption vs. Intraruption

A common mistake is a functional-line manager or executive having a pet project needing some help from a portion of the team. “I need Jim for just a little bit to fix the test bench” or “Allison’s expertise would be great for this offsite Strategy Workshop.” In a culture of interruptions where everything is the #1 priority, these are managed just as everything else: supposedly minor disruptions and possibly even referred to as “some quick non-Agile work”. And if they are quick assignments, that might even be true.

And if not, this repeatedly disrupts the Sprint Plan and the team wonders why they bother planning.

Strategy to Overcome:  Imagine instead of interrupting (“inter” being a Latin root meaning “between”), the executive intrarupts (with “intra” being a prefix meaning “within”). Those projects could easily be a bundle of work for the Agile Team (a.k.a. Epic or User Story), which the Agile Team could prioritize based upon feedback from the management. Doing this planning from within the team once again helps with the aforementioned cultural issues, but additionally addresses some of the other top obstacles such as “Not enough leadership participation” (46%) and “Inadequate management support and sponsorship” (43%).

 

Fear of Failure Becomes Self-Fulfilling Prophecy

Despite quotes from Samuel Smiles and Sir James Dyson (e.g. “It is a mistake to suppose [people] succeed through success; they more oftener succeed through failure” or “Success is made up of 99% failure”), fear of failure plagues 31% of the population on average, which far exceeds the fear of being home alone (which was 9% before coronavirus; arguably higher or lower after sheltering-in-place). Agile teams supposedly disperse that anxiety, but the Product Owner especially can experience the heavy weight of urgent decisions and unyielding second-guessing of every decision. “Agile turns into micromanagement as a result of middle management’s resistance to change,” states Age of Product. “Despite better knowledge, changing an organization into a learning one … is not in the best interest of everybody.” In the end, the Product Owner or Agile team may revert to capitulation, e.g. “Rather than guessing and being wrong, why don’t you tell me what to do?”

 

Article written by Steve Tengler July 30th 2020 www.forbes.com

https://www.forbes.com/sites/stevetengler/2020/07/30/changing-company-culture-for-agile-project-management-avoiding-the-cant-ban/?sh=730cb0c93df7

 

22 Comments
  • Stefanie
    Posted at 18:49h, 31 December Reply

    This is my first time go to see at here and i am truly pleassant to read everthing at alone place.

  • Finlay
    Posted at 19:52h, 01 January Reply

    you are really a good webmaster. The website loading velocity is incredible.

    It kind of feels that you’re doing any distinctive trick.
    In addition, The contents are masterwork. you’ve performed a great activity on this matter!

  • Brian
    Posted at 20:01h, 01 January Reply

    This design is steller! You obviously know how to keep a reader amused.
    Between your wit and your videos, I was almost moved to start my own blog (well, almost…HaHa!) Great
    job. I really enjoyed what you had to say, and more than that,
    how you presented it. Too cool!

  • Barry
    Posted at 20:45h, 01 January Reply

    bookmarked!!, I love your website!

  • Charis
    Posted at 00:52h, 02 January Reply

    With havin so much content and articles do you ever run into any
    problems of plagorism or copyright violation? My website has a lot of unique content
    I’ve either created myself or outsourced but it looks like a lot of it is popping
    it up all over the web without my agreement. Do you know any
    techniques to help reduce content from being ripped off?

    I’d really appreciate it.

  • Gregorio
    Posted at 20:28h, 04 January Reply

    You are so cool! I don’t suppose I’ve read anything
    like this before. So wonderful to discover someone with some original thoughts on this subject matter.
    Really.. many thanks for starting this up. This web site is
    something that is required on the web, someone with a little originality!

  • Robin
    Posted at 01:40h, 05 January Reply

    certainly like your website however you need to
    check the spelling on quite a few of your posts.
    Many of them are rife with spelling problems and I find
    it very bothersome to tell the reality however I’ll certainly come back again.

  • Buster
    Posted at 22:30h, 05 January Reply

    Do you mind if I quote a few of your posts as long as I
    provide credit and sources back to your blog? My blog is in the very same area of interest as yours and my visitors would definitely benefit from some
    of the information you present here. Please let me know if this okay with you.

    Thanks a lot!

  • Valeria
    Posted at 23:42h, 06 January Reply

    What’s up to every body, it’s my first pay a visit of this website; this blog
    includes amazing and actually good material in support of
    visitors.

  • Kayleigh
    Posted at 03:12h, 07 January Reply

    Excellent way of explaining, and good article to get information concerning my presentation subject, which i am going to convey in academy.

  • Modesto
    Posted at 21:24h, 07 January Reply

    Hi! Someone in my Facebook group shared this site with us so I came to take a look.
    I’m definitely enjoying the information. I’m book-marking and will
    be tweeting this to my followers! Outstanding blog and excellent
    style and design.

  • Michael
    Posted at 18:57h, 08 January Reply

    I’m extremely impressed together with your writing skills as
    neatly as with the format to your weblog. Is that this a paid theme or did you customize it yourself?
    Either way keep up the excellent quality writing, it is uncommon to look
    a nice blog like this one today..

  • Keesha
    Posted at 22:55h, 09 January Reply

    Hmm it looks like your site ate my first comment (it was super long) so I guess I’ll just sum it
    up what I wrote and say, I’m thoroughly enjoying your blog.
    I as well am an aspiring blog blogger but I’m still new to the whole thing.
    Do you have any suggestions for first-time blog writers?
    I’d certainly appreciate it.

  • Merlin
    Posted at 00:18h, 10 January Reply

    My family members all the time say that I am killing my time here
    at net, however I know I am getting experience all the time
    by reading thes pleasant posts.

  • Jennie
    Posted at 19:47h, 10 January Reply

    Wonderful work! This is the kind of info that are meant
    to be shared across the net. Shame on the seek engines for now not positioning
    this publish higher! Come on over and talk over with my site .
    Thank you =)

  • Elizbeth
    Posted at 02:57h, 12 January Reply

    This website was… how do you say it? Relevant!! Finally I have
    found something which helped me. Cheers!

  • AssosaDow
    Posted at 15:14h, 14 January Reply

    https://bit.ly/3FbHzRt
    indugasser,.218943

  • Janessa
    Posted at 04:07h, 16 January Reply

    Hello, i think that i saw you visited my web site thus i got here to go back the want?.I’m trying to to find
    things to enhance my web site!I suppose its ok to use a few of your concepts!!

  • Blythe
    Posted at 20:25h, 18 January Reply

    Touche. Sound arguments. Keep up the great spirit.

  • Elise
    Posted at 17:57h, 19 January Reply

    This information is priceless. When can I find out more?

  • Maxie
    Posted at 01:57h, 21 January Reply

    What’s up everyone, it’s my first pay a visit
    at this website, and piece of writing is actually fruitful in favor of me, keep up posting such
    articles.

  • Bev
    Posted at 14:05h, 21 January Reply

    My spouse and I stumbled over here from a different page and thought I might
    check things out. I like what I see so now i am following you.
    Look forward to going over your web page yet again.

Post A Comment