BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile in the Enterprise Content on InfoQ

  • Failures in Agile Development

    The Agile software development community discusses it successes on a regular basis, but rarely do we publicly discuss our failures. Robin Dymond has taken the first step by documenting one of his.

  • Interruption Driven Development

    Scrum talks about having minimum disruptions during the sprint. However, in the real world, if the system is already in production, within each sprint there is a strong possibility of getting production support issues. The post tries to uncover some ways to take care of these interruptions with Scrum.

  • The Complexity Around Simplicity

    Almost all Agile techniques focus on simplicity. Understanding simplicity could itself be a complex task. Many Agile community members believe that simplicity is often misunderstood and this often results in unwanted complexity.

  • Voting Someone Off the Island on an Agile Team

    On Agile teams there is a definite possibility of having a team member who is not a good fit. Members of the Agile community discuss the reasons and possible ways of voting someone off the island.

  • Agile Business Intelligence

    Large centrally designed BI systems often don't meet the expectations of their end users. In this article at Cutter IT journal Scott Ambler has written about using Agile methods to help meet the user's expectations and deliver business value quickly.

  • Do Specialists Outperform Generalists on an Agile Team?

    An Agile team is mostly a cross functional team comprising of generalists and specialists. Jurgen Appelo, challenges this concept and suggests that having just specialists on an Agile team adds more value. The post tries to correlate various view points on team composition by other members of the Agile community.

  • Handling Interruptions on an Agile Project

    Interruptions on a project, are known to, damage the flow of work. A discussion on the Extreme programming group and Alistair Cockburn with his "Sacrifice one person" pattern suggest ways to handle interruptions so that the impact on the project is minimized.

  • Presentation: Jeff Sutherland Talks about Companies Adopting Agile

    In this presentation, Jeff Sutherland, the co-creator of Scrum Agile Development Process, talks about small and large companies which are adopting Agile.

  • Are Business Analysts Ready to Become Programmers?

    Microsoft seems to think so as they prepare to deliver on the Oslo vision. Back in November 2007 Doug Purdy made a veiled reference to a new project in development calling it "Emacs.NET". This fueled rampant speculation far from the intended mark.

  • Results of Agile Adoption Survey 2008

    In February 2008, Dr. Dobb's conducted a survey on Agile adoption and the success rate of Agile software development. The survey revealed some interesting results on various parameters, including: adoption, scalability, iteration length, and team location.

  • Seniority, Respect, Authority and an Agile Team

    Senior members, who have been working in traditional teams, can face issues related to respect and authority when they come to an Agile team. An interesting discussion on Scrum Development group and Agile India group tries to uncover answers that Agile might have for the situation.

  • Does Sustainable Pace mean a 40 hour week?

    Sustainable Pace is a well known XP practice however, different people relate to it in different ways. Could an Agile team increase its sustainable pace by working longer? An interesting discussion on the Scrum Development group tries to debate the correlation between the number of work hours per week and sustainable pace.

  • Impediments To Your Value-Stream

    Scrum defines an impediment as "anything keeping the team from being more productive" and clearly stresses that teams establish means to remove them as continuously as possible. Joe Little proposes an impediment's scope may be better established as being anything keeping the organization from delivering value.

  • Creating The Culture For An Agile Environment

    Greg Smith offers an in-depth practical perspective on making your agile transition just as much about culture change as it is about process change.

  • A Preview of Mingle 2.0

    On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0.

BT