BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • 50 Developers Answer: What Do You Want Your CIO to Know About Agile?

    Trying to explain the benefits of Agile Software Development to your CIO? Does your boss want some outside validation? Esther Schindler asked more than 50 developers and Agile practitioners one question: "If you could get the boss to understand one thing, just one thing, related to agile development...what would it be? Why that?".

  • Opinion: Agile Adoption is Distinct from Agile Practices

    Using Agile practices effectively is not as easy as knowing what Agile practices are. To use test driven development effectively is different than knowing that you should follow the red-green-refactor loop. How does one get from 'Agile seems like a good idea' to 'We have used Agile practices to significantly improve the value we deliver to our organization'?

  • Continuous Integration And Version Control for Databases

    After asserting that one must, as a rule, always version their database work, Scott Allen detailed an approach to making the best of versioning databases. Allen presented a comprehensive, practical approach to creating a baseline, using change scripts to manage schematic revisions, controlling programmatic database objects, and handling branching and merging.

  • How to Develop New Activities for the One Laptop Per Child Project?

    The One Laptop Per Child project has starting shipping its first generation of XO laptops. OLPC "is not a laptop project, it is an education project", explains Nicholas Negroponte, director of the project. A full Sugar based development environment is available for developers to contribute new activities to the project. Sugar supports collaborative activities when XOs are meshed together.

  • Questioning the Retrospective Prime Directive

    The 'Retrospective Prime Directive' is commonly used in retrospectives to encourage deep learning without recriminations. But what do you do when you *can't* agree that you "understand and truly believe" that everyone did their best? In this InfoQ article, a group of senior practitioners discusses the benefits and difficulties of using this practice.

  • Communicating Intent through Idiom and Paradigm Selection

    What about using idioms and programming conventions as signals to achieve more readability and expressiveness? This is what Reg Braithwaite advocates for, suggesting that syntax or even paradigm choices can be a means to communicate the intent.

  • Does "Done" Mean "Shippable"?

    There has been a lot of discussion on various agile forums and blogs about the difference between 'Done' and 'Shippable'. It might sound like both mean the same, however discussions on the lists and various blogs suggest that these are still widely misunderstood, mis-used terms. Here's a roundup of recommendations about how to handle "Done."

  • TDD/BDD Leading To Incomplete Unit Tests?

    Peter Ritchie raised concern about TDD and BDD keeping practitioners from writing good unit tests. He cites an over-reliance on “interaction testing", a core mantra and essence of TDD and BDD, as a driver with tendency to result in incomplete unit testing.

  • Responsibility, Personal Agility, and Other Touchy-Feely Ideas

    Successful Agile teams are predominantly characterized by their culture and not their practices. This sentiment rings true to many (if not most) in the Agile field. Christopher Avery, who has made his name in the world of organizational transformations, has taken his work on Responsibility and focused it directly on Agile practices. Is Personal Agility the key to successful Agile adoption?

  • InfoQ Presentation: Selecting the Right Methodology and Steering it to Success

    It's easy to agree with "anything more than 'barely sufficient' in is waste," but it's more complicated when we actually need to customize a process for a particular project. At Agile2006 Todd Little shared a model to help leaders choose the right flavour of Agile based on project and team attributes, and he emphasised the need to actively steer projects as development progresses.

  • Opinion: Programming Languages Shouldn't Enforce Style, Teams Should

    Some believe that, if you write a large enough cookbook, there will always be a simple recipe to solve our programming problems. Taking it to an extreme, some want programming languages to limit developers to safe constructs and clean style. Reg Braithwaite skewers this idea, and challenges teams not to give up accountability for style, asking "Whatever happened to code reviews?"

  • Does Continuous Production Lead To Extreme Agility?

    The idea of continuous production has been around for some time, with Cal Henderson revealing in 2005 that Flickr releases code to production about every 30 minutes. InfoQ investigates continuous production and explores the effects it has on the product lifecycle, and in turn the host organisation.

  • Agile2008 Reminder: Registration Discounts, Submission Deadline

    Agile2008 is scheduled for August 4th-8th 2008, in Toronto, Ontario, Canada at the Sheraton Centre Hotel. The Agile Alliance issued a call for participation in December and reminds us to submit by February 25th. Another way to attend for less is to nab one of the limited number of discounted super-early-bird registrations.

  • Right-Size Your User Stories

    For those using User Stories, getting them right is one of the difficult aspects of an Agile process - they can drive or bog down your work. Pat Kua recently addressed a key question: How much detail should you put in your story? The answer, of course, is "it depends" on where you are in the process.

  • Kent Beck on Implementation Patterns

    What does good code look like? In this interview, Kent Beck talks about his new book, Implementation Patterns, that deals with this question. Kent explains why Compose Method is so important, but also talks about the relationship between implementation patterns and XP, the history of software patterns and why he believes that Cockburn's Shu-Ha-Ri description of learning is naïve and simplistic.

BT