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

  • "Good Design" Means ...?

    It's not news that at the heart of successful software systems (and, frankly, fulfilling software careers) is good design. Also not news is that defining what "good design" really means has been at the heart of many debates, papers, talks, books, discussions, and more for ages. To help, J.B. Rainsberger and Scott Bellware offer some advice to follow until that one true definition comes along.

  • Interview: Similarities Between Interaction Designers and Agile Programmers

    In this interview taken during Agile 2008, Alan Cooper, the father of Visual Basic and supporter of interaction design, talks about his contact with the Agile movement and the similarities discovered between Agile programmers and interaction designers.

  • Agile Risk Management

    Risk management is an activity directed towards the assessing, mitigating and monitoring of risks. Agilists suggest ways to effectively manage risk and use it to make better commitments to the stakeholders.

  • Track Velocity, Not Time Spent on Tasks

    A member of a new agile team asked the Scrum Development list how to keep track of the actual time engineers spend on tasks, and how this relates to the agile concept of velocity. Velocity is the agile metric for tracking how fast the team is completing features, and thus how long it will take to complete a project. The group's opinion was that tracking time spent isn't necessary or useful.

  • Measure Agile Productivity in $

    Earlier Scott Ambler posted an article of how to measure productivity on agile teams by utilizing acceleration. Recently he followed up with another post where he answers some frequently asked questions related to agile productivity and acceleration. Specifically one question answers how to measure the amount of $ saved by an accelerating team.

  • "Classic" versus "Mockist" TDD, Distinction Real?

    Hot in the TDD Yahoo group is a discussion concerning the perceived continuum between the "Classic" and "Mockist" TDD. Steve Freeman, Nat Pryce, Michael Feathers, Dale Emery, and many more discuss terminology and describe their approaches. The discussion also debates whether there even really exists such a continuum, and if so, what distinguishes the approaches that represent it's extremes?

  • Example Driven Acceptance Testing

    Unit and Integration testing often get more importance in Agile teams as compared to acceptance testing. Gojko Adzic and Lisa Crispin suggest approaches to efficiently include acceptance tests as a part of development.

  • Eclipse PHP Development Toolset 2.0 released

    The Eclipse Foundation has announced the immediate availability of PDT 2.0, a major upgrade to the popular Eclipse PHP Development Tools project. PDT is an open source development tool that provides all the basic code editing capabilities developers need to get started developing PHP applications.

  • Venkat Subramaniam on Facts and Fallacies of Everyday Software Development

    Software development is challenging and lot of fun, but there are several factors that interrupt teams from succeeding in IT projects. These are usually not tools or technologies but it is the people that affect the success of software projects. In a keynote presentation at the recent CodeMash 2009 conference, Venkat Subramaniam talked about facts and fallacies of everyday software development.

  • Pair Programming vs. Code Review

    Pair programming and code review are each practices that improve the quality of software, as well as promote knowledge sharing. When the agile vs. lean, XP vs. Scrum, and vi vs. Emacs debates get slow, developers have been known to debate the merits of pair programming vs. code review. Theodore Nguyen-Cao described code reviewers as chickens, and paired programmers as pigs.

  • Presentation: Kent Beck: Trends in Agile Development

    In this presentation, Kent Beck, the father of eXtreme Programming, shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.

  • Presentation: Testing is Overrated

    In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?

  • First Kanban Conference

    First annual Lean Kanban Process and Practices will be held in Miami, Florida, May 6-8th and featuring keynotes from Dean Leffingwell, Alan Shalloway and David Anderson. The other speakers include most of the players in Kanban movement (Corey Ladas, Karl Scotland, Eric Landes et al.).

  • Agile For Embedded Systems

    Some might say that agile development and embedded software (ie. "software supporting a hardware device") do not mix well. Mark Levison has taken some time to assemble and writeup a resource reference of people, experiences, and advice that help to show otherwise.

  • Over-Commitment Versus Over-Delivery

    A major goal of sprint planning is to make a commitment to what is intended to be delivered by the end of the sprint. However, many teams either over-commit or over-deliver. Both situations are considered as smells and lead to lack of predictability along with other related pitfalls. The team is required to walk a fine line between the two.

BT