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

  • 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.

  • Survey: The State of Agile in Practice

    In March Scott Ambler surveyed over 4,200 people to discover the actual rate of Agile process adoption and effectiveness. His conclusion: Agile is not only growing in popularity, it's working so well that adopting an Agile approach appears to be an incredibly low-risk choice. Ambler recently published not only his conclusions but also the raw data he collected.

  • Opinion: Working in isolation breeds mistakes

    Should the team room be a sanctuary? or a jazz improv session? On butUncleBob.com, Tim Ottinger blogs about his belief that the quiet bullpen is where mistakes are born, and allowed to breed.

  • Interviewing for Agile Teams Podcast

    Team dynamics can dramatically affect team performance, so staffing teams well is a critical success factor. Rob Myers, an Extreme Programming coach, has recorded a podcast "Interviewing Techniques for Staffing Lean-Agile Teams."

  • The Creeping Featuritis Chart

    Creeping Featuritis is an insidious sort of product rot, reducing useful software into heaps of expensive widgets and aggravating help features. Peter Abilla brings us a chart by Kathy Sierra, capturing what it looks like from the customer's point of view, and reminds us to "focus on the customer and abandon the competitor-focused strategy all-together."

  • Measuring Performance in the Adaptive Enterprise

    Traditional thinking has turned budgets into fixed performance contracts that force managers at all levels to commit to specified financial outcomes, despite the fact that many of the underlying variables are beyond their control. As Agility increases the futility of this exercise becomes apparent. Thought-leader Jim Highsmith proposes a helpful alternative more harmonious with Agile values.

  • Naked Agile and Naked Skydiving

    Prompted by recent discussions on the ScrumDevelopment list, Alistair Cockburn and Jeff Patton sound a call to focus on the basics: "Listening, Designing, Coding, Testing. That's all there is to software. Anyone who tells you different is selling something."

  • Throwing the Keyboard is Not the Answer

    Conflict is inevitable at work. Sooner or later, you will disagree about what to test, when to test, or how long to test software. How you approach the conflict affects the outcome and, more lastingly, how you feel about the exchange. On StickMinds last week, Esther Derby looked at some of the ways we approach conflict and how they affect solutions - and relationships.

  • Tech Stories Need to Include People and Technology

    Brian Marick, reflecting on conversations heard at Agile2006, blogged about his concern that some of us are telling stories from the purely human or social viewpoint, while other are telling technology-only stories, noting that that XP isn't a story you can tell well without talking about both of these. Marick encourages us to include both when we communicate in and about projects.

  • Agile, Orthodoxy and a Message From God

    A long and complex thread on the ScrumDevelopment list, set off by the phrase "Agile 2.0," has been exploring the past and future of Agile methodologies (for good or ill) including so-called "next generations" approaches like AUP, MSF Agile, and AMDD. Ron Jeffries, Ken Schwaber and Scott Ambler are just a few of the serious agilists who participated in this lively conversation.

  • Does Agile Dispense with Project Managers?

    Agile does away with many of the tasks by which Project Managers formerly measured their own performance. The Product Owner and Dev Team take on these activities, leaving PMs confused and wondering: "Am I redundant?" Agile coach Michele Sliger offers some reassurance, mapping PMI PMBOK practice areas to new Agile practices in her whitepaper "A Project Manager's Survival Guide to Going Agile".

  • 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.

  • Mary and Tom Poppendieck Discuss Their Next Book

    Bob Payne interviewed Mary and Tom Poppendieck at Agile2006 about their next Lean book, which focuses even more on software than the last. Mary summarizes it as "So you think Agile is a good idea: now what?" saying it will help people get started with Lean, going beyond the recipes of the first book to provide practical information and case studies to help teams do their own process experiments.

  • Leveraging the Wisdom of Project Newcomers

    Experienced newcomers can't be onboarded like programmers just out of school. The experienced professional will have specific but difficult-to-anticipate gaps that will impede their performance. In addition, this provides a great opportunity to get a fresh but experienced feedback on your processes. Gannthead.com offers some pointers wrapped in three fictional Dr. Phil episodes... (really?)

BT