Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Sprint Content on InfoQ


RSS Feed
  • Shift in Sprint Review Mindset: from Reporting to Inclusive Ideation

    Sprint Reviews should foster a dynamic environment of creativity, exploration, and continual refinement, where important product and overall business decisions are taken. In this article, we will explore the substantial mindset shift and routine change from a typical reporting-focused to interactive data-driven culture of Sprint Reviews.

  • Resetting a Struggling Scrum Team Using Sprint 0

    Sprint 0 can be a great mechanism in Agile transformations to reset existing teams which are not delivering value, exhibiting a lack of accountability, or struggling with direct collaboration with customers. This article shares the experiences from doing a Sprint 0 with an existing team which was struggling to deliver, helping them to align to a new product vision and become a stronger team.

  • Go, See & Do. A Guide to Running a Gemba Sprint

    This article is a guide to organizing a Gemba sprint; a sprint where teams, leadership, and management work together with the ultimate goal of coming together as an organization. Ahmad Fahmy explores what is needed to set up a Gemba sprint, how to organize and run one and provides some dos and don'ts to make a Gemba sprint effective.

  • Product Goals, not Sprint Goals

    There is a myth that Sprint Goals are a way to focus Scrum teams towards a common purpose, and without Sprint Goals, teams would end up building a disparate list of Product Backlog Items, every Sprint. This is in fact not only untrue, the reality is the exact opposite, that Sprint Goals are in fact a distraction and would only deliver parts of Product Goals.

  • Burn-Down or Burn-Out? How to Beat the Red-Sprint Agile Anti-Pattern

    There are ways to obtain sustainable pace beyond scrum that can help stem the increasing number of failing scrum projects. Because executing sprints as small projects often does not lead to the desired results, it is more effective to apply a backlog-item-oriented workflow and to treat sprints as iterations.

  • The Limits of Agile

    The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.