BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Retrospectives Content on InfoQ

  • Step by Step Improvement Needs Relative Safety

    At the OOP 2015 conference Colin Hood talked about bridging the gap between requirements engineering process definition and successful iterative roll-out. He presented how the introduction of improvements to requirements engineering can be done better when done step by step, and how relative safety is needed to enable people to take the steps.

  • How To Get a Happier Workforce

    Laughing can help to create a better team climate which can lead to better results. There is compelling evidence that happiness and positivity can lead to success. Here are some suggestions for what you can do when you want to improve happiness in teams.

  • Feedback Cycles in Scrum

    In agile software development feedback plays an important role. Many are aware how feedback supports dealing with changing requirements and adjusting the way of working in teams with retrospectives. But there is more that feedback can do in agile. “An effective feedback cycle in Scrum is more than having sprints and doing retrospectives” says Kris Philippaerts.

  • Q&A with Andreas Schliep on ScALeD – Scaled Agile and Lean Development

    The introduction and integration of agile approaches to an organization should be regarded and treated as an agile project itself says Andreas Schliep. An interview with Andreas about pitfalls when trying to scale agile, on ScALeD and how it compares to Agility Path, LeSS, SAFe and DaD, and on continuous improvement and scaling retrospectives.

  • Why Pair Programming is Hard to Implement

    Pair Programming is good for increasing the software quality and collaboration within team members but it is hard to implement. This news describes the reasons why it is hard and how to figure out good practices of pair programming for your team.

  • Emotion Cards for Agile Teams

    This news describes usage of emotion cards as an effective tool in the toolbox of any scrum master, agile Coach or trainer. Emotion Cards are a set of cards showing common emotions like angry, anxious, confused, happy, sad, surprised, tired and worried.

  • Huge Retrospectives with Online Games

    Agile retrospectives are mostly done at the team level or at a project level. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved.

  • Fail Fast Means Learn Fast

    Failing fast and often is one of the encouraged practices for agile teams. Sander Hoogendoorn, author of the This is Agile book discusses on his blog the importance of having a strategy that helps you on the decision of aborting a project by assuming its failure on an early stage.

  • Alternative Approaches for Implementing Agile

    Top-down implementation of agile is a commonly use approach for agile adoption in organizations. Alternative approaches exist, like implementing agile by stealth, using continuous improvement teams, starting with a quiet phase or taking baby steps by implementing a limited set of agile practices.

  • Active Participation of Product Owners in Sprint Retrospective

    Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.

  • The Power of Anonymous Retrospectives

    Hiren Doshi recently published a post on his blog about Anonymous Retrospectives, a technique suggested for agile teams to maximize the feedback gathered during retrospective meetings.

  • Role of Management in Agile Governance

    How can we manage and govern multiple agile teams? At the Agile Governance conference in Amsterdam Christoph Johann Stettina presented about agile governance and the role of management. He studied 14 large European organizations on how they apply agile project management methods in IT project portfolios.

  • Q&A with Fridtjof Detzner about Scaling and Continuous Improvement at Jimdo

    How can you make a company grow without sacrificing it’s culture? InfoQ talked with Fridtjof Detzner, co-founder of DIY website creator Jimdo, about how Jimdo started and scaled up using agile and why Jimdo uses kaizen and retrospectives to improve continuously.

  • Agile and Lean Service Management for Enterprises

    Agile software development or Scrum is not enough to make your enterprise truly deliver on the Agile promises, says Dave van Herpen. He suggests that IT service management should apply agile and lean practices combined with DevOps to improve collaboration throughout the entire enterprise.

  • Role of Managers in Agile Retrospectives

    Agile teams use retrospectives to reflect upon their way of working. Since it’s the team’s own responsibility to continuously improve themselves they have to decide upon the actions that they will do. What can managers do to support their teams when they are doing agile retrospectives?

BT