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

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

  • What Makes a Good Stand Up Meeting?

    One of the most simple and yet most talked-about agile practices is the Daily Stand Up Meeting (a.k.a. Scrum). The most recent round of discussions around the subject is occurring right now on the scrumdevelopment Yahoo! group. This discussion has resulted in suggestions about what is important about a Daily Stand Up, how to perform one correctly, and several links to articles on the subject.

  • How Long Should You Sprint For?

    What factors influence the length of your sprint? When you're trying to pick a length, between two days and six weeks, what factors should you take into consideration? One coach has taken a stab at identifying shortening and lengthening factors.

  • Don't Worry About Scaling Scrum

    Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.

  • Interview with Joseph Pelrine: Agile Works. But HOW?

    Joseph Pelrine has come full circle: from university studies in Psychology, journeying through SmallTalk, XP and Scrum, and now back to broader questions: Why and how does Agile work? In this interview, Joseph talked about Complexity Science, and how story-telling, "sense-making," network analysis and speed-dating's gut-feel approach may prove more useful than our old toolkits for managing teams.

  • Agile Project Management ScrumWorks Pro 3.0 released

    Danube Technologies has just released the 3.0 Release of ScrumWorks Pro, last mentioned in August 07. ScrumWorks Pro is an Agile Project Management tool that help track team(s) progress through individual iterations and whole releases. In this release changes focused on two areas: usability improvements and the use of MySQL as the backend database.

  • Is the ScrumMaster-as-Blocker a Pattern to Follow or a Smell to Avoid?

    So, you are on a development team that is adopting Agile or thinking of going in that direction. If you are adopting Agile by starting small, you probably are working against-the-grain in your organization. You may have heard that there should be a role that protects the team from the rest of the non-Agile world that might be useful

  • Are Iterations/Sprints Waste or Value to Agile Teams?

    Although many people consider iteration to be a key characteristic of agile software development, some question whether or not they're important, and add value to an agile method, or if they're superfluous, or even wasteful. InfoQ has assembled a roundup of arguments on the subject, to help agile teams decide if iterations are important for them.

BT