Thread regarding ExxonMobil Corp. layoffs

snicker

The company hired me to lead their "Agile Transformation."
I don't know what Agile means.
Nobody does.
That's why it works.

I make $425,000 a year.
To move sticky notes.
From left to right.
On a board.
The board is digital now.
The sticky notes cost $80,000 in Jira licenses.
Progress.

Day one, I said "we need to break down silos."
Everyone nodded.
Silos are bad.
I don't know why.
But destroying them is a career.
My career.

I introduced "squads."
Squads are teams.
But disrupted.
We disrupted the teams into teams.
Different names.
Same people.
Same problems.
But Agile problems now.
Agile problems are strategic.

A senior engineer asked what we're actually changing.
I said, "The mindset."
He asked what that means.
I said, "It's a journey."
He asked where we're going.
I said, "Toward agility."
He asked what agility means.
I pointed at the sticky notes.
They were moving left to right.
That's velocity.
We have velocity now.

The VP of Engineering said two-week sprints don't fit their work.
I said, "That's waterfall thinking."
Waterfall is bad.
Like silos.
I don't know what waterfall is.
But I know it's bad.
She stopped talking.
Waterfall accusations end conversations.

We had a retrospective.
In the retro, we discussed what went wrong.
Everything went wrong.
We put it on sticky notes.
Then we moved the sticky notes.
Into a column called "Parking Lot."
The Parking Lot is where problems go to die.
It's full.
We don't look at it.
That's agile.

Velocity is up 40%.
I defined velocity.
I also defined the points.
I also defined the stories.
We're crushing it.
At the things I made up.
To measure.
Ourselves.

The CEO asked for ROI.
I showed a chart.
The chart went up.
Charts should go up.
This one did.
I didn't label the Y-axis.
Nobody asked.
Leadership is confidence.

We do standups now.
Every day.
We stand.
For 45 minutes.
Standing is agile.
Sitting is waterfall.
My legs hurt.
But we're transforming.

The transformation is now "Phase 3."
Phase 1 was assessment.
Phase 2 was implementation.
Phase 3 is "continuous improvement."
Continuous means forever.
Forever means job security.
I'm very secure.

My contract was extended.
Three more years.
For "cultural impact."
The culture is confused.
But impacted.

Agile transformation isn't about being agile.
It's about transforming.
Continuously.
Toward more transformation.
The destination is the journey.
The journey is billable.


by
| 3103 views | | 15 replies (last March 10) | Reply
Post ID: @OP+1kd3716ef

15 replies (most recent on top)

@bw

Agree, and that's why I found the @OP so easy to laugh at/with.
(Of course, my exposure was just one of these sessions or "groups". If I was told told attend more than one, I would have sought a PIP path.)

The team-building will stop only once the morale improves.

by
| | Reply
Post ID: @b9t+1kd3716ef

OP: Whoever originally wrote it - wrote well. Fire everyone at EM who is non "real value" generator and non-(real) worker.
We do not need more "leaders"

by
| | Reply
Post ID: @1vq+1kd3716ef

Chat GBT Summary of Agile Transformation

Understanding Agile Transformation

Agile Transformation refers to the process of adopting Agile principles and practices across an entire organization, rather than limiting them to specific teams or projects. It involves a cultural, structural, and operational shift to embrace collaboration, adaptability, and customer-centricity. This transformation aims to make the organization more responsive to change, innovative, and efficient in delivering value to customers.

The transformation impacts four key areas: people, processes, technology, and structure. It requires coaching and training employees at all levels to align with Agile values, such as iterative development, continuous improvement, and transparency.

Key Benefits of Agile Transformation

Agile Transformation offers several advantages:

Adaptability: Enables organizations to respond quickly to market changes and technological advancements.

Customer-Centric Approach: Prioritizes customer feedback and needs, ensuring better alignment with market demands.

Improved Quality: Focuses on delivering value incrementally while continuously improving processes and outcomes.

Risk Reduction: Identifies and mitigates risks early through iterative testing and validation.

Enhanced Collaboration: Promotes teamwork and accountability through practices like daily stand-ups and cross-functional teams.

Higher ROI: Accelerates delivery cycles, reduces waste, and improves resource utilization, leading to better financial outcomes.

Challenges in Agile Transformation

Despite its benefits, Agile Transformation is not without challenges:

Resistance to Change: Employees and leadership may resist altering established workflows and hierarchies.

Leadership Commitment: Success requires consistent support and involvement from leadership.

Alignment with Goals: Misalignment with organizational objectives can hinder the expected outcomes.

Sustainability: Without persistent effort and urgency, the transformation may lose momentum before its benefits are fully realized.

Conclusion

Agile Transformation is a long-term commitment to fostering a culture of continuous learning, innovation, and adaptability. By embracing Agile principles, organizations can improve their responsiveness, collaboration, and customer satisfaction, ultimately driving better business outcomes.

by
| | Reply
Post ID: @1ae+1kd3716ef

After valdez, we talked about Total Quality Management, Continuous improvement, Six Sigma, and changing culture ("Teaching the elephant to dance"). Unfortunately we never realized that genetically Elephants cannot dance. This elephant cannot dance because of its DNA. We are only going to slim down the elephant and help it lose weight, but it will never dance. These are "flavor of the month" initiatives, just wait a year and it will go away or wait 2 years and you will go away

by
| | Reply
Post ID: @1a5+1kd3716ef

Copying agile satire from LinkedIn post now, are we?

by
| | Reply
Post ID: @fa+1kd3716ef

@en you'd think if you were so smart you could Google a unique phrase from the post and find the original X source. Typical.. so ready to cynically jump on something you abandon critical thought.

by
| | Reply
Post ID: @ew+1kd3716ef

No one at XOM uses Jira. We use Azure DevOps. This must be in a space that has no idea what they are doing. So either this person is not from XOM or they are off doing their own thing pretending to be experts which happens a lot XOM. Don't actually need to know how it works if I memorized the talking points.

by
| | Reply
Post ID: @en+1kd3716ef

@OP You know what? This was actually pretty good.

Happy Holidays.

by
| | Reply
Post ID: @ct+1kd3716ef

With AI you can become Shakespeare. This bullsh-t bingo was played at the oil company I retired from. Never worked. Management by Best Seller. There’s something else around the corner and your marching orders will change. Watch.

by
| | Reply
Post ID: @by+1kd3716ef

I find it hard to laugh at this because I have been in a handful of "workshops" in the past year where we moved sticky notes around for 4 hours.

by
| | Reply
Post ID: @bw+1kd3716ef

Maybe we should throw "agile transformation" over the fence to Global Capital Projects or the IT GBU to implement. We have been moving "Post It" notes around on brainstorming boards for decades.

As a way of working, agile is an iterative approach to work that helps teams deliver value faster and with fewer headaches. Instead of betting everything on a big launch, agile teams deliver work in small, consumable increments. There are several widely used agile methodologies, including Scrum, SAFe, and Extreme Programming.

Agile is also a mindset that influences how we choose to think and act. As agilists, we choose to:

(1) Accelerate our value realization by embracing worthwhile changes.

(2) Delight customers by taking a customer-centric view to our work.

(3) Improve group capability by proactively collaborating instead of working in functional silos.

(4) Improve predictably by refining our understanding of what is needed through regularly showing our work and acting on feedback.

(5) Optimize flow by working on small things instead of big things. Big things are accomplished incrementally as a series of small things.

(6) Keep workloads within capacity by finishing the things we work on instead of starting lots of things. This is called limiting work-in-process (WIP).

(7) Improve continuously by frequently learning from our experience and evolving our practices based on what we learned.

(8) Agility predictably, sustainably, and rapidly delivers high-quality value in a changing, complex environment.

by
| | Reply
Post ID: @bk+1kd3716ef

We never used Jira in my team
and I don't know of any team using Jira.
But I am a worker bee that does the job mentioned in the sticky
and I only make a forth of the OP.
Sad.

by
| | Reply
Post ID: @ba+1kd3716ef

it's funny because it's true - Dr. Sheldon Cooper

by
| | Reply
Post ID: @b0+1kd3716ef

This post is elite.

by
| | Reply
Post ID: @ax+1kd3716ef

This was surprisingly well written. Thanks for sharing!

by
| | Reply
Post ID: @a4+1kd3716ef

Post a reply

: