Kane Mar

Adventures in Agile Software Development and Scrum

The Thai Restaurant Model (and its applicability to Software Development)

Personal note: I started this article about 9 months ago. Although it’s quite a fun article, I have become increasingly critical of the use of analogies to describe software development. My feeling is that analogies lead to assumption that may, or may not, be valid. So, rather than talk about building a bridge, a house or cooking Thai food I’d rather talk about software specific problems or situations.

After some personal doubt I finally decided to complete the article because it is amusing, if not insightful. I hope you enjoy the article. In the future I’ll endeavour to keep analogies far, far away.

Mae Phim is a small Thai restaurant in Seattle [1]. I went there with my colleagues last year and we were impressed with their speed of operations. Within the space of a few short minutes, we were able to place an order and received a hot, freshly cooked meal.

Despite the short duration, it was sufficient time for us to wonder if there were any lessons here to use in Agile software development. After all, if we were able to deliver software as rapidly and with the same high quality as Mae Phim delivers food then that would surely be a good thing.

An interesting observation was that the business model for Mae Phim is common to the business model of other Thai restaurants [especially those that cater to the lunchtime crowd who present their own set of unique challenges]. This article discusses some of the characteristics of their operation and discusses the applicability (or not) to developing software.
Read the rest of this entry »

Filed under: Agile Software Development, Cultural Change, Organisation Change, Patterns, Planning, Project Management, Scrum

Controling the flow of daily meetings with a team mascot

When introducing Agile/Scrum practices to a new team it’s common for the team to have very chaotic or drawn out meetings. Often the daily scrum will degenerate into a long conversation over topics that are of little interest to the team.

Long daily meetings are insidious for Agile teams. If the the team spends more than 15 minutes in a daily meeting they are more likely to stop having them. It’s important therefore to keep the meetings short and to the point.

Read the rest of this entry »

Filed under: Agile Software Development, Cultural Change, Organisation Change, Patterns, Project Management, Scrum

Selecting ScrumMasters (Facilitators)

Many teams often ask who is the best person to fill the ScrumMaster role. The assumption is that this role is best filled by someone who was previously a project manager [or is the current project manager of a team]. Clients ask: “What’s the difference between leading a RUP (or Waterfall) team, and leading a Scrum Team?”

Read the rest of this entry »

Filed under: Agile Software Development, Cultural Change, Organisation Change, Project Management, Scrum

Share This Blog

Bookmark and Share

My Twitter Updates

Agile Carnival