Aside Posted on
Thinking this morning about a conversation I had yesterday at happy hour with several truly impressive human beings.
Some characteristics of a high performance Lean-Agile team:
- no longer needs a scrum master or lean agile leader
- uses the best of Scrum as an empirical framework for an amazingly lean sustainable flow process
- also uses principles of Lean and a Kanban system
- has a natural affinity for pulling the right work at the right time
- possesses high trust within the team and externally known to consistently deliver successful outcomes; builds trust with other teams
- regularly pushes the boundaries of what is possible as innovators
- cares deeply about people and the organization
- committed to continuous learning and relentless improvement
Just in from the blogagility.com laboratory...
One of the many challenges faced by coaches in a Lean-Agile transformation is convincing resource owners/managers to relinquish the “control” part of command & control (see Capt. David Marquet on “Greatness”) to people & teams for the purposes of –self-organization & self-management. Or as I prefer to describe it, getting out of the way of people’s innate creativity and ability to innovate. Capt. Marquet offers pillars of competence and clarity as the recipe, of which I wholeheartedly agree.
As in the value systems of Scrum and the SAFe® – respect for people and culture, openness, and transparency are part of the fresh culture we are driving. Without these basic human elements of successful relationships and communication, trust doesn’t exist. The dual combo “T’s” of trust and truth are the kingpins in any long-lived organizational change / transformation. Read the rest of this entry »
I started a new series of posts where I will answer some actual problems/ideas presented in an I&A problem solving workshop as part of open space facilitation. This is the third of a few dozen that I plan on covering. If you have any comments, please, let’s learn together.
“Outside team interference and noise; unnecessary outside team involvement”
A SAFe Answer
This problem is not unique to the SAFe or Lean-Agile space. It exists in every organization I’ve encountered.
It is, however, a big, common problem. How many times have you or your team been “redirected” to work on the latest fire fighting drill? Was this time accounted for in the waterfall/traditional silo planned WBS that you are working against? I’m certain your manager and project managers always go back to the integrated master schedule (IMS) to reflect lost productivity. IMS’s always account for production down, maintenance, operations? Sure they do. Especially when the team doing costing gets to review the proposal and “tweak” the final numbers. [insert massive sarcasm]
Enhancing the understanding process by simulation of cadence and ceremonies. A very valuable teaching technique. Still experimenting with how to effectively integrate into various courses.
#SAFe #Scrum #Agile #Lean
Quote Posted on
Reblogged with permission from Adrian Lander, the original author of this content. Originally published on LinkedIn, August 6, 2017.
The Agile Guru – Not!
I was in shock, the other day. Really.
Yes, me getting shocked, after so many years in practice, hardly a believable start of a real story.
But it really happened, in front of my eyes. And I was in shock, for just a bit.
It was a clear demonstration of some of what is so wrong with a common way of “implementing agile”.
I saw someone with the title of agile coach being called “Guru, sir”. By his student. And he did not change that. His Ego and Power ATM just opened up to accept the dollar notes.
I had to reach for the toilet (virtually). Read the rest of this entry »