BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Collaboration Content on InfoQ

  • Designing Collaborative Spaces for Productivity

    The typical Agile team may work in a common "teamroom", but personal space is also needed. Teams find out fast enough that some of the creature comforts left behind in their former traditional spaces were there for good reasons. This article shares the collected wisdom of dozens of teams who created their own work spaces, as collected by several experienced Agile coaches.

  • Key Takeaway Points and Lessons Learned from QCon London 2007

    This article presents the main takeway points and further reading as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Case studies (amazon, eBay, Yahoo!) Java, Agile, the Agile Open Space, Qualities in Architecture, Ajax and Browser Apps, .NET, Ruby, SOA, Usability, Banking Architectures followed by a summary of peoples over all opinions of QCon.

  • Agile Business Rules

    James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.

  • Book Excerpt: Agile Retrospectives: Making Good Teams Great

    Project retrospectives help teams examine what went right and what went wrong on a project. Traditionally held at the end of a project, they're actually too late to help - no wonder we call them "post-mortems". Agile teams need retrospectives that are iterative and incremental, to find problems and design solutions to help teams improve early on, when improvement yields the most benefit.

BT