I’m a Program Manager for CyberSource with 10 years of in-depth experience with Agile methodologies. As a Scrum Master, Agile mentor and coach, I’ve helped to foster the growth of XP and Scrum teams on challenging projects in a variety of different industries and using a wide variety of different technologies.
I’m fascinated by finding creative ways to solve the problems that teams encounter. I am particularly interested in Agile and Lean techniques and the refreshingly honest perspective that they bring to the development process. Working with teams to solve ‘wicked’ problems is one of the most difficult and the most rewarding aspects of the work I do.
Currently I’m researching topics including but not limited to: Impediments, Swarm Intelligence, Lean & Kanban, as well as constantly seeking ways to create passionate teams that work together on topics that they find interesting.
Hi there,
I am working for agile42 and I would like to introduce Agilo for Scrum. Agile42′s core business is to support companies to implement Scrum and other lean approaches. The tool Agilo is open source and based on real project needs. It supports all main roles (Product Owner, Scrum Master, Team with Sprint Backlog, Product Backlog and Burn Down Chart) and gives an overview for everybody interested in the project.
I invite everybody to try it. We have a lot positive feedback and we are working hard to optimize Agilo for all Scrummers
agila
Congratulations! Your blog has been added to the AgileVoices.com aggregator ;o)
Groovy! Thanks!
So….scrum has nothing to do with Rugby?
It is only indirectly related to Rugby. Here’s how I understand it. In the early 90′s there were some guys who were curious about what the common attributes of high performing teams were. Guys like Takauchi and Nonaka, Ken Schwaber, Jeff Sutherland and others. To find out, they found the breakaway successful products, the real hot innovations and looked at the teams that created those products. For example, if I were to do this today I might go look at the iPhone design team.
The more they looked at these teams, the more attributes they had in common. It was things like:
1) High performing teams are autonomous and have few rules
2) High performing teams are unstable, with few fixed roles
3) High performing teams are highly focused
…and so on. So the story goes that when these folks attempted to summarize their findings they found themselves using sports metaphors to describe these teams. Now, when you think of a sport with very few rules and little in the way of prescribed roles, what immediately comes to mind? Rugby. So when they put together a methodology for others to try and implement similar success, they naturally called it “Scrum”.
It’s a little weird, but the way I see it, it could have been worse: the name could have been “Smear the Queer”.
It is only indirectly related to Rugby. Here’s how I understand it. In the early 90′s there were some guys who were curious about what the common attributes of high performing teams were. Guys like Takauchi and Nonaka, Ken Schwaber, Jeff Sutherland and others. To find out, they found the breakaway successful products, the real hot innovations and looked at the teams that created those products. For example, if I were to do this today I might go look at the iPhone design team.
+1
You’ve been linked!
http://agilescout.com/practice-agile-do-it/
Greetings from Sydney. Thanks for the useful info. I’m doing a project at uni and your content was quite useful. Thanks for sharing
Useful website. Thanks for sharing.
Hello Tom
Very useful link, good information and comparison, please have a look at Yodiz (www.yodiz,com), its a new tool, just introduced lat year
Asif
[...] Slowing Down: Actions Written by: Tom Perry [...]