BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Continuous Improvement Content on InfoQ

  • Using Pairing for Experimenting in Presentations

    In the closing keynote of the Agile Eastern Europe 2015 conference Yves Hanoulle did an experiment together with his son Joppe in pair presenting. InfoQ interviewed Joppe and Yves Hanoulle about doing experiments, checking the safety of the environment and ways to make it safer, learning from failure, and presenting in pairs at conferences.

  • Leadership and Management Approaches from Radical Companies

    Introducing and managing change in organizations can be challenging. InfoQ interviewed Jason Little who is involved in organizing the Spark the Change Canada 2015 conference about the leadership and management approaches that radical companies use, on finding better ways to manage people and about what will happen to management in the near future.

  • How Agile Can Learn from Behavioral Economics

    People often don’t decide and act rationally, according to studies from the area of behavioral economics. Pierre Hervouet describes how our brain takes decisions, talks about experiments on using personas and the IKEA effect and explains what we can learn from these experiments for agile software development.

  • Agile Teams and Managers can Collaborate to Solve Impediments

    Impediments are issues that hinder agile teams. They are problems that teams are facing, which they need to solve. Managers can help agile teams in several ways to solve impediments.

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

  • Deploying Transparency and Self Regulating Management to Get Actions Done

    At the Lean Kanban France 2014 conference Bjarte Bogsnes gave a keynote presentation about beyond budgeting. In his presentation he talked about the problems with traditional management and how transparency and self regulating management comes to the rescue, and the principles and practices of beyond budgeting.

  • Use Your Blockades to Sustainably Improve

    Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.

  • Maturity Model for Continuous Performance Improvement

    Martin Fowler, described Maturity Model as a tool that helps people assess the current effectiveness of a person or group and supports figuring out what capabilities they need to acquire next in order to improve their performance.

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

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

  • Concerns about Measuring Velocity for Team Improvement

    Agile teams measure the velocity of their sprints. It helps them to plan and track their progress and provides insight for product owners to plan product releases. Can teams also use velocity data when they want to improve themselves? Several authors have written about velocity and shared their concerns on measuring velocity to improve the productivity of teams.

  • Having Actions Done from Retrospectives

    Agile retrospectives help teams to find and do actions to improve continuously. There are different ways to do follow up on the actions and to evaluate if actions are leading to better team performance and more value delivered to customers.

  • The Habit of Improving

    Agile is about a mindset and a contiguous improvement of everything said Yves Hanoulle. InfoQ did an interview with him about the habits that people have and what you can do to get into the habit of improving.

  • Supporting Personal Development in a Learning Organization

    Organizations learn through their employees. To enable adoption of agile ways of working, organization have to support the personal development of their employees.

BT