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

  • Is Your Application Ready?

    We mostly ship software by date, squeezing all development and testing efforts toward that deadline. We prioritize what we think is important, and once our application passes a certain quality level, we’re ready to go live. But even when we do ship, can we tell the readiness status of our application?

  • Learning and Liminality in Agile Adoptions

    In this 4th article in the series about Open Agile Adoption Dan Mezick presents an approach to take advantage of the natural stress that come about when making change in organisations to help achieve sustainable agile transitions.

  • Interview with Simon Brown about Sustainable Competence

    Why are some teams successful while others are less than stellar? Can teams use processes to do their work? How can managers help teams to become better? And do we need incentives to improve the quality of software? InfoQ did an interview with Simon Brown about sustainable competence for continuous improvement, balancing people and processes, and software quality and architecture.

  • Agile Fluency: Finding Agile That's Fit-for-Purpose

    The Agile Fluency model is a way of thinking about and planning investments to create the conditions of Agile that best fit your development effort, business need, and customer value. James Shore and Diana Larsen described it in the 2012 article "Your Path through Agile Fluency". This article by Diana aims to helps you to use the Agile Fluency model effectively.

  • An interview with Vasco Duarte and Jason Little on Lean Change Management by Happy Melly Express

    Change agents need a “constant stream of high-quality content to support their work” as Vasco Duarte from Happy Melly states. InfoQ did an interview with him on a new publishing business that aims to connect authors with their audience in a sustainable way, and with Jason Little, an author that will be publishing about Lean Change Management.

  • Scrum Master: Position or Role?

    Scrum common wisdom says a Scrum delivery team needs a dedicated Scrum Master (SM). For new teams, this make sense. But as teams mature, do they still need a dedicated SM? Can an SM have multiple teams? Can the team assume the role within themselves? This article proposes that for mature teams, a dedicated SM is no longer needed.

  • The Integration of Agile and the Project Management Office

    Agile and the Project Management Office (PMO) are no longer considered diametrically opposed phenomena. With an ever-changing business landscape, organizations are required to adopt more nimble approaches. In many cases, Agile is more suitable within the PMO than people think.

  • Deploying it right with AppVeyor CI and PowerShell

    Deploying real applications is hard. Questions arise when there are configuration settings in the Registry, custom folders structure, or you have to deploy to a web cluster. In this article we look at setting up continuous delivery for a solution consisting of ASP.NET web application and Windows service to a staging and production environments using PowerShell remoting and AppVeyor CI.

  • What Do You Look For In a Servant Leader?

    In this article, let’s discuss the kind of qualities, preferences, and non-technical skills you might need in a servant leader, your potential Scrum Master, agile project manager, potential account manager, or whatever role you need filled.

  • El-Habya'a” or The Technical Debt

    Technical Debt is not always a bad thing but it needs to be carefully managed especially as it increases with time at a geometric rate. Technical debt also deserves a special attention in Agile projects. This article suggests that technical debt is a risk and it can be managed using standard risk management process and presents an outline of this process in the context of Agile projects.

  • Open Agile Adoption in Theory

    In this 3rd article in the series about Open Agile Adoption Dan Mezick presents the theoretical background to the approach and explains why the techniques described in the other articles work to help achieve sustainable agile transitions.

  • DevOps - Pivoting Beyond Pockets

    Traditional Infrastructure Operations roles are no longer scaleable. The traditional system admin or the network engineer or the engineering roles such as storage engineers are rapidly changing. The difference between a developer and operations engineer are becoming more and more invisible and will eventually dissolve. This is part of a massive shift in the IT Infrastructure Industry.

BT