BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Scrum Content on InfoQ

  • Martin Fowler on Avoiding Common Scrum Pitfalls

    Jacky Li of InfoQ China spoke with Martin Fowler during ThoughtWorks' AgileChina conference. In this print interview, Martin Fowler talked about Scrum certification and the future of Agile.

  • Interview: Joshua Kerievsky about Industrial XP

    In this interview taken by Sadek Drobi of InfoQ, Joshua Kerievsky, founder of Industrial Logic, talks about Industrial Extreme Programming which extends XP by including practices dealing with management, customers and developers.

  • Presentation: Agile and Beyond - The Power of Aspirational Teams

    In this presentation filmed during Agile 2008, Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away. Tim has a personal perspective on Agile practices and shares from his own experience.

  • Presentation: 10 Ways to Screw Up with Scrum and XP

    In this presentation filmed during Agile 2008, Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is, or they don't hold retrospectives.

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

  • Prioritizing (the Backlog) For Profit

    Having difficulty prioritizing the backlog? Luke Hohmann has described a method to make quantitative decisions about which backlog items should be considered first. In addition to the usual attributes such as implementation effort, Luke suggested adding attributes to measure stakeholders needs, strategic alignment and to ask whether the item is driving profit.

  • Presentation: Succeeding With Agile: A Guide To Transitioning

    In this presentation filmed during Agile 2007, Mike Cohn talks about the transitioning process towards an agile organization, why the process is inherently difficult, and what it takes to see self-organization emerging in a previously tightly controlled environment.

  • Software Development: A Traffic Jam Waiting To Happen

    Software development is Hard. One of the main reasons is that it is a complex adaptive system. Agile - when done right - seems to do a very good job of providing stabilizing feedback. We take a look at what it means for something to be a 'complex adaptive system' and what particular practices in Agile help us out.

  • Managing Risk with Scrum

    Risk management deals with reducing the probability and impact of adverse events on a project. Members of the Agile community discuss whether explicit risk management is required or it is addressed implicitly as a part of Scrum.

  • InfoQ Book Review: Agile Adoption Patterns

    Ryan Cooper picked up Agile Adoption Patterns: A Roadmap to Organizational Success by InfoQ's own Amr Elssamadisy and gives this book a positive: This book belongs on the bookshelf on anyone who is interested in helping a traditional software organization make an effective transition to a more agile way of working.

  • Presentation: Heartbeat Retrospectives to Amplify Team Effectiveness

    In this presentation filmed during QCon London 2007, Boris Gloger speaks about retrospectives. Agile development teams learn and improve by inspecting and adapting. High performing teams inspect and adapt not only their code and tests, but also their methods and interactions.

  • Presentation: Agile Project Management: Lessons Learned at Google

    In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum. He tells how Google started with no engineering management, then gradually introduced Scrum without spoiling the development culture formed over the years.

  • Agile Smells: Don't Let This Happen To You!

    Mark Levison wrote an interesting blog summarizing some of the work that has been done to catalog Agile smells. We summarize some of those smells and point to other intersting work that documents the Agile community's experience in adoption.

  • Interview: Rachel Davies on Generic Agile

    In this interview taken during Agile 2007, Rachel Davies, director of Agile Alliance, talks about Generic Agile, about the necessity to understand what is the essence of a development process.

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

BT