InfoQ

Presentation

   Good News: We have re-worked our video infrastructure to provide more reliable service. Please email bugs at infoq.com with any problems.

Recorded at:
Recorded at

Agile Quality: A Canary in a Coal Mine

Posted by Ken Schwaber on Nov 13, 2006 12:00 AM

Community
Agile
Topics
Delivering Quality,
Delivering Value,
Agile in the Enterprise
Tags
Business/IT Alignment,
Agile2006,
Scrum,
Antipatterns,
Planning,
Testing
Summary
Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. InfoQ presents video of his talk, The Canary in the Coalmine. Schwaber discussed how a degrading core codebase paralyses a team and negates any Agility gained through process improvement. He proposed strategies for management to identify, track and stop this downward spiral.

Bio
Ken Schwaber (www.controlchaos.com) codeveloped Scrum with Jeff Sutherland in the early 1990s. A 30-year IT veteran and an Agile Manifesto signatory, he subsequently founded the AgileAlliance, a nonprofit organization dedicated to training and supporting Scrum practitioners.

About the conference

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

4 comments

Reply

A ray of hope by Cameron Purdy Posted Nov 13, 2006 6:26 AM
The importance of Transparency and Ethics by Noah Campbell Posted Nov 13, 2006 12:29 PM
Re: The importance of Transparency and Ethics by Deborah Hartmann Posted Nov 13, 2006 4:37 PM
Re: The importance of Transparency and Ethics by Noah Campbell Posted Nov 14, 2006 11:45 AM
  1. Back to top

    A ray of hope

    Nov 13, 2006 6:26 AM by Cameron Purdy

    I tend to disagree with a lot of the Agile(tm) Consultants(tm) and Speakers(tm), but I really do like the core idea that one can view "Code Quality as a Corporate Asset". Whether or not one can have get "the CEO [to come] into the room and [say]" anything seems about as far-fetched as the other Schwaberisms, but we (anyone writing code -- even test code and example code) should always view "Code Quality as a Corporate Asset", and we should also view it as our craft, i.e. we should build it with great pride of worksmanship. Peace, Cameron Purdy Tangosol Coherence: Clustered Cache

  2. Back to top

    The importance of Transparency and Ethics

    Nov 13, 2006 12:29 PM by Noah Campbell

    Great presentation! I have to admit that I too find the Agile(tm) Consultants(tm) and Speakers(tm) to be a bit underwhelming in their rhetoric. Scrum as a management process is what usually draws me to these presentations and the key to this presentation is that Scrum builds in transparency into the process. That's not to say that RUP, Waterfall, etc. can have equal transparency, but short iterations do put the spotlight on potentially ugly practices...and that's the key to the this presentation. What do you do when presented with difficult decisions? In Beck and Schwaber's words: have the courage to do the ethical thing.

  3. Back to top

    Re: The importance of Transparency and Ethics

    Nov 13, 2006 4:37 PM by Deborah Hartmann

    Scrum as a management process is what usually draws me to these presentations and the key to this presentation is that Scrum builds in transparency into the process.
    Yes, this emphasis on transparency is one of the things that draws me to Scrum as well. But, as others have said, a good process cannot "fix" shoddy developers. Scrum relies on the team to bring skill and common sense into the mix. We can add: a good process cannot hide or compensate for a lack of coaching ethics. We need good processes and good people. If forced to choose... recent experience suggests: go with the good people :-)

  4. Back to top

    Re: The importance of Transparency and Ethics

    Nov 14, 2006 11:45 AM by Noah Campbell

    If forced to choose... recent experience suggests: go with the good people :-)
    Hopefully you're never forced to choose. I think your point about going with good people as a safe bet is that someone will emerge as a leader and put a process in a place.

Exclusive Content

Intentional Software - Democratizing Software Creation

Business users doing programming? Simonyi and Kolk presents how Intentional Software offers a radical new software approach that separates business knowledge from software engineering knowledge.

Getting Started with Grails

Jason Rudolph discusses Java/Grails integration, Grails plugins, creating a Grails sample application, Grails app structure, data querying and persistence, validation, controllers and tag libraries.

Creating Product Owner Success

The Scrum Product Owner role is powerful, valuable and challenging to implement. It brings healthier relationships between customers and developers, and competitive advantage - if you do it right.

Book Excerpt and Interview: Effective Java, Second Edition

Effective Java, Second Edition by Joshua Bloch is an updated version of the classic first edition, which won a 2001 Jolt Award. InfoQ asked Bloch questions about the areas that the new edition covers.

Tapestry for Nonbelievers

A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.

Pete Lacey on REST and Web Services

In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.

Business Natural Languages Development in Ruby

Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.

Distributed Version Control Systems: A Not-So-Quick Guide Through

Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.