About the Blog

  • Software is our business, and perfecting the art and science of delivering it is our mission. The contributors to this blog are passionate about the impact that great teams and good software can have on an organization’s bottom line. They bring decades of experience designing, developing and delivering great software, and each is playing a critical role in Borland’s own transformation.

Blogging Authors

« The new team rooms | Main | Using a Repository for Agile Requirements Collaboration »

January 19, 2009


Feed You can follow this conversation by subscribing to the comment feed for this post.

Stephen Palmer

Couldn't agree more. Dale's role is a vital one.

An underlying principle of Scrum is stated as frequent inspection and adapting accordingly (see Ken Schwaber's books).

It is a big problem if a team are not allowed to adapt (improve) their process because it would then no longer be 'Scrum'.

On the other hand, slowly adapting a process until it has reverted back to old ways of doing things is a temptation I have seen inexperienced agile teams fall foul of.

The comments to this entry are closed.