Comments on: 78 Things I Have Learned in 6 Years of Agile Coaching

By: Jean Tabaka

Jean Tabaka — Tue, 03 Aug 2010 00:45:09 +0000

Wow. Reading through the comments to this post is phenomenal: as good as or better than reading the original 78 items. I think I need to write an addendum attributing all of you who have provided additional “learnings”.

Thank you so much for sharing all your insights.

Jean

By: Steve Mecham

Steve Mecham — Thu, 03 Jun 2010 17:47:16 +0000

Jean, thanks for the post! I suggest a few additions:
* Effective team members practice self leadership.
* The organization’s personnel practices must support instead of hinder teams, servant leadership and Agility in general. Remember the old adage “You get what you measure.”

By: Everbridge

Everbridge — Sat, 08 May 2010 15:34:13 +0000

We learned that Agile helps control scope creep, which had always been a problem before we went to Agile. Our Agile teams now do a fantastic job of defining and controlling the scope of a release and an iteration.

By: Tweets that mention 78 Things I Have Learned in 6 Years of Agile Coaching | Agile Blog: Scaling Software Agility -- Topsy.com

Sat, 01 May 2010 04:21:13 +0000

[...] This post was mentioned on Twitter by Centripetal Software. Centripetal Software said: 78 Things I Have Learned in 6 Years of Agile Coaching – http://bit.ly/a9jDfc [...]

By: Tweets that mention 78 Things I Have Learned in 6 Years of Agile Coaching | Agile Blog: Scaling Software Agility -- Topsy.com

Fri, 30 Apr 2010 21:27:00 +0000

[...] This post was mentioned on Twitter by Jennifer Bleen. Jennifer Bleen said: http://www.rallydev.com/agileblog/2010/03/78-things-i-have-learned-in-6-years-of-agile-coaching/?elq=4d4ded28740149a89c5dbdebf19915a0 [...]

By: Ron Lichty

Ron Lichty — Fri, 30 Apr 2010 00:29:30 +0000

I might add,
Refactoring is cheaper than reuse.

It didn’t take agile to teach me that making code reusable takes three “uses” – you don’t begin to get reusability right until the third. There’s a rule-of-thumb that’s pretty widely known to that effect. But yet many of us kept trying to architect for reusability instead of letting architecture and reusability emerge – until agile pointed out the foolishness of doing so from a different angle.

By: Ron Lichty

Ron Lichty — Fri, 30 Apr 2010 00:23:39 +0000

Jim, it’s hard to know if Tech Republic or writer Shelley Doll who posted there is a competent methodology expert, but Shelley has been a prolific writer there and both defined and favored the approach in the post at: http://articles.techrepublic.com.com/5100-10878_11-1046507.html

By: Glyn

Glyn — Thu, 29 Apr 2010 21:39:40 +0000

Item 2 “Distributed teams need love and a ScrumMaster at each site.” caught my eye as my company has distributed teams. Question: Does this suggest that the scrumMasters at each site “co-master” the team? Where can I find additional info on this?

By: Tweets that mention 78 Things I Have Learned in 6 Years of Agile Coaching | Agile Blog: Scaling Software Agility -- Topsy.com

Thu, 29 Apr 2010 21:32:13 +0000

[...] This post was mentioned on Twitter by sweigarts, Tech Pit. Tech Pit said: For agile enthusiasts, this is a really great article – 78 Things I Have Learned in Agile Consulting – http://ow.ly/1ENXh [...]

By: Joe

Joe — Thu, 29 Apr 2010 21:30:04 +0000

“…silly alleged traditional approach that no competent methodology expert ever favored”

There are lots of these still in practice out there. Even their practitioners refer to their own process as “waterfall” or “waterfall like”