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

  • Q&A with Ken Schwaber and Jeff Sutherland about Scrum Guide Updates

    The Scrum guide has been updated to better reflect what Scrum is and clear up misconceptions. Scrum can be used for building software products, and it can be applied to many other areas outside of software as well. Scrum is a framework based on empiricism for continuous improvement. Having a potentially shippable product increment at least every sprint or more often is a key element of Scrum.

  • Tackling Awesome Superproblems with Collaborative Games

    Awesome superproblems are large, complex and enduring problems which can only be solved through collaboration. The key to making collaboration work is serious games, where participants voluntarily agree to follow the rules of the game to create a better and more durable result.

  • First Annual Retrospective Report Published

    The First Annual Retrospective Report provides a deeper understanding of how retrospectives are used in the real world. The results indicate that retrospectives lead to improved team communication and productivity and help to create an environment of trust. Major challenges are that topics discussed cannot be solved by the team and people do not feel comfortable speaking up.

  • Improving Work Life with Organizational Hacks

    Visualize everything, pair up, open Friday, and no training budget; these are some of the "work hacks" that have improved work life at Sipgate, a telephone provider using Scrum.

  • Learning to Become Agile

    The agile paradigm adapts processes to human nature, in contrast to the classical management approach which obliges team members to adjust to a particular development process. Bateson's learning model can help us to go from doing agile - following an agile method - to being agile - having your own agile identity and vision.

  • Increase Learning with 10% Autonomy Time

    Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.

  • Continuous Improvement Beyond Retrospectives

    If you want continuous improvement you can start with retrospectives, but you must go far beyond that with change management, culture change, and innovation. The most important thing in order to make change happen in organizations is creating new habits and changing your culture.

  • How GlobalLogic Used a Bottom-up Approach to Become More Agile

    Yuriy Koziy, delivery manager at GlobalLogic, argued at the Agile Eastern Europe 2016 conference that organizational change should start at the team level rather than in senior management. He formed a group of like-minded engineering managers and agile coaches who act as change agents, transforming the organization bottom-up from the inside.

  • How Testability Can Help Teams to Go Faster

    At the Agile Practitioners 2016 conference Huib Schoots talked about testability. He stated that low testability, anything that makes our software hard to test, slows teams down, and explored how testability can be increased.

  • Developing a Solar Car with Scrum

    At the Lean Kanban Benelux 2015 conference Jeroen Molenaar shared his experiences working as an agile coach with the Dutch solar car team that has won the world solar challenge in Australia.

  • Leadership Principles for Agile Organizations

    Selena Delesie gave a keynote at the Agile Testing Days 2015 about leadership principles that she sees in successful agile companies. InfoQ interviewed her about how leadership principles from Sir Richard Branson are related to the foundations of agile and asked her which principles are giving companies a competitive edge and how companies can deploy agile to become more competitive.

  • Role of Autonomy in Agility

    Autonomy is one of the core guiding principles at Spotify. It enables employees to make decisions as close to the works that is being done as possible. At the Agile Greece Summit 2015 Kristian Lindwall and Cliff Hazell from Spotify explained why autonomy is at the heart of agility.

  • Agile and Lean Adoption in Greece

    Small and medium sized companies have adopted the agile way of working in Greece and there are few examples of agile in larger organizations, interest in agile from the local industry is growing. Among the topic discussed in agile meetups are whether companies should implement Scrum or Kanban, Scrum for startups, dealing with fixed price and scope contracts, productivity, and happiness in teams.

  • How to Facilitate an Agile Retrospective Using "Rory Story Cubes"

    How to use Rory Story Cubes for sprint retrospective.

  • Anti-patterns for Handling Failure

    Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.

BT