BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Lean Content on InfoQ

  • Use Cases Considered Valuable (but Optional) For Lean/Agile Requirements Capture

    Dean Leffingwell, author of Scaling Software Agility and Chief Product Methodologist at Rally, has concluded that Use Cases can be a valuable tool to model requirements for a large-scale Lean/Agile Project. Use cases are not commonly encountered in Lean/Agile (especially XP and Scrum), where stories are the requirements gathering tool of choice.

  • Article: Lean and Agile, Marriage Made in Heaven or Oxymoron?

    Dave West takes a look at the world views of the Agile and Lean communities and finds them in conflict. If true, then many of us in the community blending Lean and Agile and unaware of the inherent clash in ideals could be making some big mistakes. As an example of a manifestation of this conflict Dave takes the backlog.

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

  • Managing Change Requests in Scrum

    Tracking change requests in Agile is often associated with being at odds with the Agile principle of "Responding to change over following a plan". However, in certain situations it might be necessary to track change requests. An interesting discussion on the Lean Agile Scrum group tries to look deeper into the 'Why' and 'How' of tracking change requests.

  • Scrum of Scrums - Issues and Value

    The Scrum of Scrums meeting "is an important technique in scaling Scrum to large project teams. These meetings allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration." Allan Shalloway asked for people's experience "on Scrum-of-Scrums for coordinating teams vs scaling Scrum to the enterprise" he sees problems in with large groups (350 people).

  • Presentation: Principles and Practices of Lean-Agile Software Development

    In this presentation held during Agile 2008, Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.

  • Kanban as Alternative Agile Implementation

    Kanban systems for software, derived from the Toyota Production System, are an iterationless approach for scheduling work. Instead of using a time boxed iteration and planning meeting, the pulls stories from the backlog only when it has completed its previous work. Dave Nicolette thinks that its important to expand our repertoire beyond the basics become familiar with other tools like Kanban.

  • Agile Games for Learning

    At Agile 2008, Don McGreal and Michael McCullough ran a session that showed how to use games and exercises to help improve our understanding of Agile principles and practices. After the conference they created the Tasty Cupcakes as a repository for all Agile games.

  • Questioning Servant Leadership

    Is the role of an agile manager only that of servant leader? Should they ever use traditional command and control tools? Should the agile manager ever wield authority and make demands of the team? Should they ever make changes in the membership?

  • Fowler: Agile Vs. Lean Misses the Point

    In a recent blog post, Martin Fowler explains how the question "Should I use Lean software development instead of Agile?" is based on a false premise. Agile and lean are so deeply interwoven that if you are doing agile you are doing lean, and vice-versa. Those considering process change will likely find the description of the interrelatedness interesting and enlightening.

  • Presentation: Future Directions for Agile

    In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.

  • Scrum-ban Paper Adds Kanban to Scrum

    Corey Ladas has written an interesting paper titled "Scrum-ban" in which he describes how a Scrum team might introduce the lean practice of kanban. He goes on to describe an evolutionary process, which if taken far enough, replaces most of Scrum. Even for those who don't want to scrap Scrum and go lean, the paper provides a useful view into what kanban is and how it can augment Scrum.

  • Death of Hybrid Camry Chief Engineer is Ruled Overwork

    Last month the Japanese labor board ruled that the death of the Chief Engineer on the Camry Hybrid project was ‘karoshi’ (death by over work). This story raised a number of interesting issues about what we can learn from Toyota, sustainable effort and why we develop software.

  • An Introduction to Lean Thinking

    Lean software development, which we hear a lot about these days, may be still a bit of a mystery for people who come to Agile via Scrum or XP. Earlier this year, at an Open Party was sponsored by InfoQ China, Ning Lu of ThoughtWorks China offered an introduction to Lean thinking, and said the biggest obstacle to Lean thinking can be the manufacturing mindset.

  • Traceability Matrix in an Agile Project

    The relevance of a traceability matrix is to easily perform impact analysis to a changed requirement.However, does a traceability matrix have a place in an Agile project? The post looks at various view points across blogs and mail groups to find a solution.

BT