BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • Frugal Innovation: Doing More with Less

    Frugal innovation provides ways to do more and better with less. It helps us to solve problems with limited resources in a sustainable way and to address inequality and empower billions of people at the bottom of the pyramid. Agile and frugal support each other; both aim to solve the problem at hand and nothing more, getting products into the hands of the users early and learning from that use.

  • Q&A on the Book "Agile People"

    Pia-Maria Thorén has written a book titled Agile People, in which she challenges the role of Human Resources in organisations, identifies where the current approaches are not working and why they need to change to support modern organisational thinking.

  • Q&A with Eberhard Wolff On the Book “A Practical Guide to Continuous Delivery”

    Eberhard Wolff speaks with InfoQ about his work "Continuous Delivery: A Practical Guide", where we detail some of the major concepts behind successful CD adoption and the ripple-effect it can have on developer productivity and quality of service.

  • What Does Company-Wide Agility Imply?

    Self-organization, transparency, constant customer focus, and continuous learning: these are the four values that drive company-wide agility. InfoQ interviewed Jutta Eckstein and John Buck about how to apply a combination of Beyond Budgeting, Open Space, and Sociocracy to support these agile values, and what benefits this approach can bring.

  • Relearning to Learn

    For my 30 plus years in tech, I've been reading and listening to tech mostly wrong. After in depth investigation into learning strategies, I've restructured my knowledge acquisition process. Find out how I've taken control of my learning queue, how I now perform active reading while taking creative notes, and hear how to use reflection and quizzing to lock knowledge in.

  • Soft Skill Patterns for Software Developers: The “Learning from Unintended Failures” Pattern

    Soft Skill Patterns describe human behaviours that effectively solve recurring problems. The "Learning from Unintended Failures" pattern helps us improve the resilience of a system after a failure. The pattern follows 4 steps: identify a failure, quickly resolve any immediate impact, analyse root cause and system behaviour during the failure, and finally generate and implement improvement ideas.

  • Customize Your Agile Approach: What Kinds of Leadership Does Your Project Need?

    This is the fourth in a series of articles that will help you think about how you might want to customize your agile approach for your context. This article is about the kind of leadership your project might need and who might provide it. Teams new to agile or new to an organization need facilitation so they can create their own agile approach that works.

  • Q&A on the Book "A Seat at the Table"

    In the book A Seat at the Table Mark Schwartz explains how the traditional role of the CIO conflicts with an agile approach for software development. He explores what IT leadership looks like in an agile environment, advising CIOs to set a vision for IT and take accountability for business outcomes.

  • Scaling Agile - Master Planning Together

    The first article in the series about making scaled agile work shared a true scaling agile story; the second article described the importance and the how-to’s of slicing your requirements into potential releasable epics. So now we’re ready to build on top of those slices and that common understanding; we’re ready to do the master planning together.

  • How Self-Organization Happens

    There isn't one specific pattern that emerges from self-organization. The processes are so deep and fundamental to human interactions that you cannot enforce any specific hierarchical or non-hierarchical pattern with rules. Trust between people is an outcome of allowing people to freely self-organize. Complex networks of trust emerge and change as people continuously negotiate their relationships.

  • Customize Your Agile Approach: What Do You Need for Estimation?

    This is the third in a series of articles that will help you think about how you might want to customize your agile approach for your context. Many agile approaches assume teams will estimate with story points, which leads to a project velocity measure. Instead of velocity, consider counting stories or using cycle time for estimation. You might not need to measure velocity at all.

  • Q&A on the Book "Create Your Successful Agile Project"

    The book Create Your Successful Agile Project helps people understand agile approaches and select what could work for them.Too often, teams adopt a framework without understanding the context in which that framework is useful. This book shows how you can use your team’s unique product, context, and people to define a suitable agile approach for your project.

BT