| Newsgroups |
gmane.comp.programming.scrum.general |
| Message-ID |
<[email protected]> |
Here is the situation at hand:
The vendor already positioned the engagement as transformation. In reality, we are actually doing what you say, piloting agile with a few selected projects as a realistic first step. It's not a company roll out, yet, however that's the long term hope of our internal sponsors.
But we have a meeting with the CFO and we have an opportunity to impact a major impediment, by seeing what can be done with portfolio management and governance (i.e. stable teams doing one project at a time). To quote, "Doing one thing at a time gets more things done." It's a big problem here and changing that will win a lot of middle management hearts and minds. I may plant the seed for a future conversation about annual performance reviews, etc., but that at least creates a space for the portfolio WIP conversation.
As well, I don't think it's too early to be prophylactically talking about creating a "blame free" environment that tolerates small failure as a learning gift, and that we hope to be able to expose and deal with systemic structural and cultural impediments safely when they come up.
Is this still to far a reach in your view?
Perhaps I'm just tired of AINO. I want to leave them with some tangible improvement in their day-to-day lives.
Michael
On Oct 10, 2015, at 8:02 AM, Michael Wollin [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote:
Yeah, Ron, but what do you REALLY think?
On Oct 10, 2015, at 5:20 AM, Ron Jeffries [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote:
Michael,
> On Oct 10, 2015, at 7:40 AM, Michael Wollin [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote:
>
> I you were to make one slide for the C-suite to explain why we use the term "agile transformation," what would it be?
It would say, in big bleeding red letters:
DO NOT UNDERTAKE AN “AGILE TRANSORMATION”.
NOT NOW, NOT EVER, NEVER.
I do not think an “Agile transformation” is something that should be undertaken by an organization until they have a number of successful ordinary Agile projects running. If they have those, they won’t be asking for an “Agile transformation” and they’ll almost certainly know what they should do rather than “roll out Agile".
Regards,
Ron Jeffries
ronjeffries.com
If it is more than you need, it is waste. -- Andy Seidl