BT

InfoQ Homepage Delivering Value Content on InfoQ

  • Q&A on the Book Team Topologies

    The book Team Topologies by Matthew Skelton and Manuel Pais shows how to arrange teams within an organization to enable effective software delivery. It describes four fundamental team types and three team interaction patterns, and dives into the responsibility boundaries of teams and how teams can communicate or interact with other teams.

  • Q&A on the Book Managing Technical Debt

    The book Managing Technical Debt by Philippe Kruchten, Robert Nord, and Ipek Ozkaya provides principles and practices that help you gain control of technical debt throughout the software development process and life of the software product.

  • Q&A on The Manager‘s Path with Camille Fournier

    In the book The Manager’s Path, Camille Fournier explores managing engineers and what it takes to be a technical manager. She describes the different roles which form the path from mentors and tech leads to senior engineering management, discusses the challenges of technical leadership and provides advice on how to deal with them.

  • Predictable Agile Delivery: The Executive Challenge

    As agile grows-out of its years of self-obsession and teenage petulance into a post-agile state, ‘Predictable Agile Delivery’ feels like a realistic goal that advantages both the business sponsor and their development stakeholders. This article shares some ‘good, bad and ugly’ examples of practices that often work and some that always fail at improving large organizations.

  • Q&A on the Scrum Field Guide - 2nd Edition

    The Scrum Field Guide - 2nd Edition by Mitch Lacey is a "what to expect" book for organizations transitioning to agile, which aims to help teams to deal with issues that occur and fine-tune their own implementation. An interview about the essentials of Scrum, sprint length, full time Scrum masters, making time available for solving defects, preventing bad hires, and increasing benefits from Scrum.

  • Q&A on The Agile Mind-Set

    Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set. The book provides ideas, examples, and anecdotes that organizations can use to make a shift to agile.

  • Q&A on Kanban Change Leadership

    In the book Kanban Change Leadership Klaus Leopold and Sigi Kaltenecker explore how Kanban can be deployed to get change done in organizations and to build a culture of continuous improvement. An interview on doing change in small steps, solving problems, using WIP limits, priorities and classes of service in Kanban, using the Theory of Constraints with Kanban, and getting results with Kanban.

  • Author Q&A on Agile Value Delivery - Beyond the Numbers

    Larry Cooper and Jen Stone have written a book which provides advice and techniques for blending agile practices with portfolio, program and project management, taking a value focused approach to managing the outcomes of initiatives rather than focusing on the activities and practices which are the center of many methodologies. They spoke to InfoQ about the book and the ideas behind it.

  • Probabilistic Project Planning Using Little’s Law

    When working on projects, it is most of the time necessary to forecast the project delivery time up front. Little’s Law can help any team that uses user stories for planning and tracking project execution no matter what development process it uses. We use a project buffer to manage the inherent uncertainty associated with planning and executing a fixed-bid project and protect its delivery date.

  • Using Experiments and Data to Innovate and Build Products Customers Actually Use

    An interview with Jan Bosch, professor of software engineering and director of the Software Center at Chalmers University of Technology, about the benefits that companies can get from increasing delivery speed, the next steps that organisations can take after adopting Agile and DevOps, using experiments to innovate, practices for experimentation and how organisations can become more innovative.

  • Evo: The Agile Value Delivery Process, Where ‘Done’ Means Real Value Delivered; Not Code

    Current agile practices are far too narrowly focused on delivering code to users and customers. There is no systems-wide view of other stakeholders, of databases, and anything else except the code. This article describes what ‘Evo’ is at core, and how it is different from other Agile practices, and why ‘done’ should mean ‘value delivered to stakeholders’.

  • #NoEstimates Project Planning Using Monte Carlo Simulation

    Customers come to us with a new product idea and they always ask the questions - how long will it take and how much will it cost us to deliver? Reality is uncertain, yet we as software developers are expected to deliver new products with certainty. This article shows how to do planning using reference class forecasting with the #NoEstimates paradigm which promises more accuracy in forecasts.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.