BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Project Management Content on InfoQ

  • Software Development Lessons Learned from Poker

    There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.

  • The "Consulting" Contract

    Coach Michael Spayd tells us that both contractors and permanent employees can play a "consultant" role, and should think about developing consulting contracts or "designed partnerships" with their clients - not about the exchange of money, but to help create stellar results for the client while working in a manner that adheres to their own values and preferences.

  • Visualizing Agile Projects using Kanban Boards

    In the spirit of "information radiators and “big visible charts” Kenji Hiranabe proposes using Kanban Boards to organize three viewpoints (Time, Task, and Team) so the whole team understands the current status of the project and can work in an autonomous, motivated and collaborative manner.

  • AgileAdvert Video Winners Announced

    At Agile2007's Google reception, the audience voted to make the (very sad) clip "Developer Abuse" the number 1 video, thereby making "Matthew" (name changed to protect the innocent) this year's AgileAdvert famous Agilist. Five more videos were also recognized, sporting singing, dancing, a beating, "outside the box" thinking, expletives (deleted), and charming children (not all in one video!)

  • SOA and Agile: Friends or Foes?

    SOA aims at making the entire enterprise agile by using services as the building blocks for applications. Agile software development aims at making organizations agile by introducing practices that increase communication and feedback. Which is right? Which is better? Are we comparing apples and oranges? Can they be used together, and if so, how? Join us in the discussion!

  • Agile User Interface Development

    The wider adoption of Agile software development has raised questions about how an approach that shuns up-front design and analysis can coexist with the emerging practice of user-centered design, which has a detailed user research and modeling phase before development begins. In this article Dave Churchville explores how the disciplines can be used together for an effective development process.

  • Good Agile Karma

    Agile relies heavily on discipline, rather than genius. We're told that average teams, even in the early stages, can achieve dramatic performance improvement if they are disciplined. As we do these things, the effects of our words and actions actively create, and re-create over time, the environment in which our teams and projects operate - for good or ill.

  • Agile Business Rules

    James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.

  • Interview: Jim Johnson of the Standish Group

    Jim Johnson, founder and chairman of the Standish Group, took time out from his vacation to talk with InfoQ editor Deborah Hartmann about his research, and the role of Agile in changing the IT industry. Johnson is best known for creating the CHAOS Chronicles: 12 years of independent research on project performance, including data on over 50,000 completed IT projects.

  • Agile: The SOA Hangover Cure

    Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.

BT