By its very nature, Scrum is a constant journey of inspection and adaptation. But there comes a time when it’s a good idea for an Agile team (mature or not) to take a step back to review and relearn the foundation principles and practices of Scrum. In other words, have a team “reset.” I’m [...]

{ 0 comments }

Yankee Agile Geek Puts the scrum in hockey games I bet kids love him Dan Mezick’s Agile Coach Journey Haiku Original haiku written by John Sinkankas when his company, Data Directions, used the Coaching Agile Teams book as a group learning text. Illustration copyright 2010 Pearson Education.

{ 0 comments }

Project teams struggle Life coaching enhances scrum Now the teams can thrive Kathy Harman’s Agile Coach Journey Haiku Original haiku written by John Sinkankas when his company, Data Directions, used the Coaching Agile Teams book as a group learning text. Reworked by Kathy Harman. Illustration copyright 2010 Pearson Education.

{ 0 comments }

Irish coach in emotional turmoil Stopped the self-centered desiring Now owns a pretty good mirror Martin Kearns’ Agile Coach Journey Original haiku written by John Sinkankas when his company, Data Directions, used the Coaching Agile Teams book as a group learning text. Reworked by Martin Kearns. Illustration copyright 2010 Pearson Education.

{ 0 comments }

Managed lives away Velvet hammer awed by scrum She now walks in peace Lyssa Adkins’ Agile Coach Journey Original haiku written by John Sinkankas when his company, Data Directions, used the Coaching Agile Teams book as a group learning text. Illustration copyright 2010 Pearson Education.

{ 0 comments }

Dear Lyssa, When we met in June we discussed the high performance tree and I told you I was using it to set the vision of the Agile journey with the teams I coach. You asked me to write an article in French about the performance tree and I promised I would to it. Done [...]

{ 0 comments }

It had been a long time since we had done our last retrospective. There were a few reasons for not doing it, but the most important was the customer and his deadlines. We did everything in a hurry as more and more functionality had to be added, having no time for internal process improvement. Release had been done [...]

{ 0 comments }

Thirty-five

by Paul Tevis on January 8, 2011 · 1 comment

Thirty-Five is a collaboration technique1 I learned from Lyssa Adkins at Agile 2010. She mentioned it in one of the sessions she was leading and didn’t have time to include it but said she’d teach it in an Open Jam if anyone was interested. About a dozen of us were, so later in the week [...]

{ 1 comment }

I appreciate Lyssa’s point about there being many journeys to becoming an Agile Coach.  Though my college degree is in engineering, my career has traveled far from that discipline and looped back around via a management path.  Software engineering is not even in my background!  So, I am perhaps the most unlikely of software development [...]

{ 0 comments }

When I was hired on a contract basis to fulfill the brand new role as Agile Coach, I realized that my “coaching” would be difficult to quantify for my manager. Having just read “Coaching Agile Teams,” I decided to follow’s Lyssa’s suggestion of keeping an Accomplishment Log (aka Value Journal). When my contract was up [...]

{ 1 comment }