AGILE IN ACTION

Tag: agile-2008

Wednesday, December 10, 2008

Pomodoro-powered promiscuous pair-programming

Posted by Simon Baker
At Agile 2008, Gus attended a session about the Pomodoro Technique by Stefan Noteberg and has been using it since.
Read more... Comments: 3

Monday, November 10, 2008

Beer helped

Posted by Simon Baker
When Energized Work turned one year old back in June we started to give a lot more attention to our ideas to develop the company. We decided it was time for action. While attending Agile2008 in Toronto, we talked and talked over beers in the bar at the top of the CN Tower and talked some more in Fynn's of Temple Bar. Since then we've been beavering away behind the scenes, occasionally alluding to progress in my tweets.
Read more... Comments: 1

Tuesday, August 26, 2008

Welcome to Agile Skywalker

Posted by Simon Baker
I've invited our effervescent friend Nana Abban to contribute to the blog. Nana joined the crew a while back and we invited him to join us at Agile2008 where he did a splendid job drawing attention to us. Those of you at the conference will remember him as Agile Skywalker. That's him in the t-shirt. And that really is his job title.
Read more...

Saturday, August 23, 2008

Craftsmanship and Artful Making

Posted by Simon Baker
At Agile2008, in his banquet keynote, Uncle Bob proposed over execution" be added to the Agile Manifesto as the fifth value statement. I've blogged before about the lack of craftsmanship in software development and it continues to concern me.
Read more...

Monday, August 18, 2008

Energizers in Toronto

Posted by Simon Baker

Sunday, August 17, 2008

The natural laws of software development

Posted by Simon Baker
At Agile2008, I watched Ron Jeffries and Chet Hendrickson talk about the natural laws of software development.
Read more... Comments: 1

Saturday, August 16, 2008

Converting business value into actual money

At Agile 2008, Luke Hohmann from Enthiosys talked about converting business value into actual money. Luke said prioritizing the backlog by ROI doesn't work and suggested developing attributes for backlog prioritization that drive profitable growth. In terms of what we've been doing at one of our clients using throughput accounting this means increasing revenue without significantly increasing investment and decreasing costs without impacting throughput (or the capacity to deliver).
Read more... Comments: 2

Wednesday, August 13, 2008

A 'nut it out' norm

Posted by Simon Baker
I really like the idea of having a team norm in place to help deal with interpersonal conflict. The norm would require the people involved in the conflict, as part of their membership of the team, to work together (with the help of a facilitator; aka Scrum Master) to find the root cause of their conflict. Basically get in a room and work it out before the conflict gets bigger and pulls the whole team down. The people involved are required to bring their analysis and agreement to the next retrospective and report it to the team so that everyone learns from the experience.
Comments: 1

Saturday, August 9, 2008

Lack of humble pie leaves bitter aftertaste

Posted by Gus Power
A cornerstone of the agile community is collaboration. However, I came away from Agile 2008 feeling slightly deflated. Over the past few months one of our teams cited the lack of respect as the root cause for the breakdown in collaboration they were experiencing. A lack of respect is in itself a symptom of something else more fundamental - the absence of humility. Humility is not self-debasement but rather the ability to get over ones own ego and false pride. The humble person genuinely listens with interest and without conceit to other peoples' points of view. Humility creates context for the open exchange of information and ideas regardless of the difference in experience of the people involved and sets a stage for shared learning.
Read more... Comments: 2

Friday, August 8, 2008

Discovering what business value is and what to do about it

Posted by Simon Baker
Joe Little's session was interesting. Basically, you need to define what business value is for your product and that definition may evolve over time.
Read more...