BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Techniques Content on InfoQ

  • Practical Advice for Implementing Scrum

    As Scrum continues to gain momentum, it's not surprising to hear the call for practical help for these many novice teams. Mike Vizdos, a Certified Scrum Trainer and Agile coach with experience in both small and large enterprises, has responded with a site called "Implementing Scrum", using cartoons and straight talk to lay out the basics.

  • Practitioners Adapt Agile to Local Constraints

    Some people think they can only be Agile with small, co-located teams and full management support, but most teams aren't that lucky. So, should they should give up on Agile techniques? Scott Ambler's answer is a resounding "No!" His Dr. Dobbs article "Imperfectly Agile: You Too Can Be Agile!" outlines how Agilists overcome common challenges that others use as excuses for not being Agile.

  • Opinion: Putting Overtime in Perspective

    Agile work, when done in a disciplined, creative way, tends to be very intense, so Agile leaders encourage balanced lives for team members and promote "sustainable pace". Mitch Lacey, a Microsoft Program Manager, recently blogged about his emerging understanding of how to use this XP practice appropriately.

  • Choosing a Continuous Integration Server

    In the first of a series of articles on continuous integration Paul Duvall compares three popular continuous integration servers, Continuum, CruiseControl, and Luntbuild. He considers criteria such as features, longevity, target environment, and ease of use.

  • Is Project Status Relative?

    Scott Ambler introduces a term for a familiar project phenomenon: the "green shift" that occurs when people rework status reports to make them more politically palatable to management. But can management actually handle the truth?

  • Book Excerpt: Agile Retrospectives

    InfoQ brings you an exclusive chapter excerpt from the recent book "Agile Retrospectives: Making Good Teams Great", by Esther Derby and Diana Larsen. These expert facilitators show how teams can run focused, helpful retrospectives themselves, without an outside facilitator. We asked the authors a few questions about the making of their book.

  • Tackle Testing Debt Incrementally

    Technical debt can shorten a product's life. But when technical debt mounts, it can be difficult to see how to pay it off. In her StickyMinds column, Johanna Rothman explains practices to help teams start paying off that debt - thereby easing their product's development and maintenance for a long time.

  • Interview: Real-World Agile for .NET Developers

    Kathleen Richards interviews Robert C. Martin about his new book, co-authored with his son Micah: "Agile Principles, Patterns and Practices in C#," which puts Agile practices to work in a .NET environment,

  • Tips for Effective Kaizen Process Improvement

    Agile software development and Lean Thinking go hand-in-hand for many practitioners. Six-Sigma blackbelt Mike Wroblewski has blogged some lessons learned from a recent kaizen session. People are a key variable in both manufacturing and software environments, so his lessons learned in manufacturing are also interesting for Lean Software practitioners using kaizen events for process improvement.

  • Hanselminutes Podcast on Scrum Project Management

    Scott Hanselman, a Certified Scrum Master at Corillian, has posted a podcast on the Scrum project management methodology. He uses Scrum in his own projects and feels that Scrum makes Agile approachable and easy to grasp. He goes over just-in-time task-level estimation, velocity, how burndown charts help forecast delivery dates, and the concept of when a feature can be considered really "done".

  • InfoQ Article: Using Logging Seams for Legacy Code Unit Testing

    Ian Roughley shows how to use logging seams to easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes.

  • InfoQ Article: Exclusive Excerpt from Practices of an Agile Developer

    Andy Hunt, one of the originators of the Agile Manifesto, and Venkat Subramaniam have written a compilation of the habits, ideas, and approaches of successful Agile software developers in "Practices of an Agile Developer". InfoQ brings you a free excerpt on Agile Debugging.

  • Patterns for Daily Stand-up Meetings Published

    Jason Yip has published "It's not just standing up", Patterns for Daily Standups on Martin Fowler's Bliki. In the article he discusses the benefits and consequences of common practices for daily stand-ups. The patterns are intended to help direct the experimentation and adjustment of new practitioners as well as provide points of reflection to experienced practitioners.

  • Studies Concur, Small Teams Are Best

    Knowledge@Wharton asks: Is Your Team Too Big? Too Small? What's the Right Number? Decades of research suggest the sweetspot may be between 4 and 6, though corrections to team size are unlikely to resolve all of a team's problems.

  • Agile Testing Practices Overview

    Jon Kern, one of the original authors of the Agile Manifesto, has written a good overview of Agile approach to software testing. In it he talks about mixing different kinds of tests - including manual tests - and testing techniques.

BT