Archive for the ‘Methodology’ Category

2011 Agile Morning Session with Ron Jeffries and Chet Hendrickson

August 9, 2011

Two kittens on screen – one hissing, one looking glum. 🙂

“What We Got Got Right; What We Got Wrong”

Manage value not cost (management gonna like dat?)

Need for solid technical practices – how this translate across to what we’re doing in advertising.

What (you) got wrong: Dogmatism
– beginners particularly
– competition between methods and demonizing other methodologies

“rituals are not that cool” – Chet

“Zero-sum” thinking

“There’s new lousy things being developed every day this week.”

Estimation and planning is focused on wrong end of stick; should be focused on value. Tends to become typical corporate command and control approach – not Agile.

Release planning becomes fixed scope thinking.
Features not solutions.

Like Jeff Patton, thinks make all stories same size and count them.

If software value does not outweigh many times over, then should get a better idea.

Multiple product owners leads to thrash.

Mentions Mary Poppendieck – a really good team is a creative unit – and splitting out product owner is risky. Makes them someone special. ( and so not as part of team)

Ron on no “I” in team: much of joy on team is self growth and recognizing this comes from circumstances of team.

“Iterations Themselves Are Suspect” – too many get it wrong therefore must be wrong (? – is this a logical conclusion?)

Change Is Hard
Too scary to try – too difficult to do.
– The Kanban –
Can be powerful because requires you to look at everything that is going on. A Lean value stream view like Kanban can let you see this.

[gummy bears? storyboards?]

All emergent, but best if substrates is good ideas, or may take longer for processes do really the good they are meant to do.

Simple isn’t easy: leaving out critical practices – license people to do what’s needed (just follow ceremonies and not really inspect and adapt) – Scrum Alliance – offering certification with no substance – deprecate necessity for skill and craftsmanship.

Chet: “Agile” sounds so good that companies wanna be that – and want to rewrite the Manifesto so it fits their circumstance. “We are Agile, and if we have to rewrite manifest,to to prove that, we will.”

Ron mentioned Ken’s comment about not letting. agile dissolve and Brian Marick’s follow on that eventually economy could be affected by 10 people.

Aha: pushed towards respecting people

Be careful of just staying at your safe spot. Life is pain and anyone telling you it’s not is trying to sell you something.

Ron feels lean, Kanban and retrospectives are *not* Agile.

(Retrospectives?! But those are inspect and adapt)

CERTIFICATIONS: don’t think makes you a master BUT at least gives training.

Think single piece flow industrial logic out of Kanban a good idea.

Question on documentation. Draw pictures every time. Stephen Mellor on park bench does not show why we did NOT do something. ( I had thought Steve proponent documentation – was I wrong?)

Do not get into fixed price contracts

Post Script: was able t figure out how to ask Ron for a book in the right way. 🙂

2011 Agile Signatory reunion

August 8, 2011

Getting here early at 5:20 – too early? My session next door and walls came down – why not avoid crowd and risk being in wrong spot?  [Got front row seats 😉 ]

Session start:  History of Snowbird with Alistair Cockburn and “Uncle” Bob Martin. The meeting was originally called Lightweight Methods conference.

What’s interesting is the Manifesto came out of this *team*; and just as this occurred to me Martin Fowler is talking about this quality.

Talking about would they change Manifesto, and [the role of the] individual [in Agile]. Ward Cunningham, founder of XP, mentioning importance of what almost sounds akin to a military unit. Growing a community of people that appreciates excellence.

Fascinated to see who grabs mic. What topic.

Jeff Sutherland: “It would not have happened with [any] one of us.”

Martin Fowler: hates the no “I” in team saying. Always an “I”- I will commit. I will be great [for the team].

Brian Marick:  [story of a ] software dev saying ” my job does not suck as much as it used to.”

[Question from audience.] What did they argue over most? Timeframe. (Jon Kerns)

Alistair mentioning [word] “iteration” was in contention.

Steven Mellor mentions [the word] “software” was used instead of code.

Ron Jeffreys – people want to do Agile but don’t want to do it. Likes to see us [the audience] taking to next level.

By the way – sitting by Lean master Mary Poppendieck, who totally changed how I think of performance reviews.

Alistair – like to see [the word] “agile” melt and just be the way people do things.

Steve thinks documentation needs real work.  [Why did someone code something in a particular way should be captured.]

Ken responds to Alistair that [regarding the word] “Agile” [we] should not let it disappear. May mean opacity is back.[ and that] the evil empire has won.

Ron Jeffreys example of a book and an illustrator who would only work alone and now will draw on the page. [This is interesting to me because it talks about the creative who wants to go off and be in “flow” all by themselves rather than collaborate.]

Want to hear from Arrie DSDM guy.  [He did not speak once during the entire gathering. Pity!]

Alistair mentions 2001 first time Arrie met Kent Beck.

Slowly slowly they are abandoning the park bench – standing, staying where they are. [Moderator got them back in shape later, though, reminding them of the rules.]

The manifesto came from the space between all of us (that Uncle Bob?)

Jeff Sutherland: Lean as a community of learning from the Japanese founders perspective. What actually happens is inspect and adapting. How the lean company’s became great. “Lean needs to be about people and rise to Agile.”  [What this was about was that the western notion of lean loses that sense of community.]

Ken Schwaber:  team

Alistair:  [Talking about when he first encountered Kanban that he thought it amazing that you could] pull out a foundation stone (time box) and nothing crumbled.

Ended with a skit with a bishop and [a salesman – one espousing the religion of Agile; the other espousing the religion of conferences, books and certifications.  I think Tobias Mayer would have loved that part! LOL 🙂 ]

8/9: Edited in the morning and put fixes in brackets for some reason.

2011 agile conference kind of live – session 1

August 8, 2011

Howdy – i am being chaotic a bit and publishing unedited notes. See how it goes. 🙂

In “Becoming Agile in an Imperfect World” as first session. So many sessions I want to attend – so difficult to decide. So many folks love to talk with for hours. Ran into Alistair Cockburn and Ghennipher Weeks on the way in; great breakfast conversation with strangers.

10am: Looking at chart in this session talking about initial spike of happiness, then resistance and chaos. We “just need to know have tools to get out of it.”. Must do homework upfront and work on organizational impediments like no collaboration, like too many concurrent projects and multi- tasking.

(Thinking of Dept. Defense as the ultimate in h2ofall but they here!)

11:30 Pick shorter projects, pick lower priority projects so comfortable if don’t succeed. (But doubting on “agile lifecycle” a little. They are not advising purity. )

Customers may derail agile adoption. (Should they be exposed to sausage-making?)

ikiwisi – I’ll know it when I see it

Standardizing processes a demand? Just standardize values and principles.

For roll-outs: Iterate into small VALUE based increments. Collaborative, evolutionary, integrated, adaptive, encompassing. Embrace change to deliver customer value, plan and deliver often, human centric, excellent work, collaboration with business people.

Have retrospectives every month.

Modeled on the Tipping Point.

1 collaborative – enhancing communication and collaboration.

When people get the value they get they rituals.

11:54 implementing in fortune 20 company – Ahmed Sidkey mentions a focus NOT on practices but just on collaboration. Main issue is “we think we know” in development. And business people think ” well they did not ask me.”. People don’t talk to each other.

12 pm How does this relate to our companies. My thought – is there a roll for some design upfront? Purists may object…

On this chart see “Cockburn” level 2 and 3 people? Means ha and ri? For third iteration.

Mindset surveys – I think some people are not that interested in process. They just want to do the work. Some process improvement stuff may seem nerdy to these people. Sometimes awareness comes across as nerdy: hyper self focused and not other-aware. Low social skill.

To combat?

Inspire people. – make it real and tangible.

1 make a specific goal
adoption schedule specific
don’t try to achieve all benefits immediately
Reduce WIP – so people dont waste time re- orienting
2 make it personal – benefits financial
Don’t be pie in sky
3 shape path make it easier
( for people who think we are being nerdy – how to handle?)

Prioritize the workstream.

Losing job security if you give up command and control.

At the end collected feedback. Inspect and Adapt!

Tailored Content, Laziness and Self-directed Teams

May 4, 2011

I’ve been challenged in thinking about how human laziness influences self-directed teams.

This morning I stumbled on this talk by Eli Pariser about the affects of  “tailored content.” “Tailored content” means content on the web is algorithmically filtered and, so, “tailored” for you according to your behavior, according to what you click on. In practice, this can mean you don’t get to see links that might challenge you and might not be in accordance with your usual patterns. (more…)