BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Culture & Methods Content on InfoQ

  • Lessons From A DevOps Journey

    Matt Callanan has been pushing the boundaries of Agile software development for over six years and most recently he extended that journey to DevOps. He recently shared his experiences in a talk at the Agile Development Practices West conference entitled "Lessons From A DevOps Journey". InfoQ caught up with Matt prior to the conference to find out more about his experiences in DevOps.

  • My 10 things for making your Agile adoption successful

    In response to the large percentage of unsuccessful organizational change efforts consultant Allan Kelly offers his advice and guidelines for successful agile adoption in the form of a top-ten list of things managers and teams can do to increase their likelihood of success.

  • An Interview with Rebecca Parsons - Thoughtworks CTO

    Dr Rebecca Parsons is the Chief Technology Officer for Thoughtworks, and a Director of the Agile Alliance. At the Agile Australia conference in Melbourne she discussed the trends in database technology around NoSQL databases, the linking of continuous design with continuous delivery and the impact of the mainstream adoption of agile practices on the Agile Alliance.

  • DevOps:Evolving to Handle Disruption

    With continued concerns regarding IT’s ability to meet the demands of the business in light of disruptive influences and a changing economic landscape DevOps might hold an answer.

  • The Agile Project Manager — Voilà: The Great Reveal

    Certified Scrum Master training tells us we must conduct Reviews (aka Demo's) at the end of every Sprint. Rarely do we get guidance on how to have a great Sprint Review. Bob Galen has experienced the bad "Demos" that were only Powerpoint and helped coach them to the level where stakeholders clamoured to attend.

  • Managing Security Requirements in Agile Projects

    Managing security requirements from early phases of software development is critical. Most security requirements fall under the scope of Non-Functional Requirements (NFRs). In this article, author Rohit Sethi discusses how to map NFRs to feature-driven user stories and also how to make security requirements more visible to the stakeholders.

  • Interview with Simon Baker, Author of No Bull

    InfoQ has interviewed Simon Baker, cofounder of Energized Work and the 2009 recipient of the Agile Alliance Gordon Pask Award, author of the "No bull" publication on the past 12 years of Agile.

  • An Implementer’s View of Cloud Computing Readiness Assessments

    Are Cloud Computing Readiness Assessments a red herring or a valuable tool to help management decide if the organization is ready to adopt?

  • Distributed Version Control Systems in the Enterprise

    Every major Open Source project worldwide has already embraced Distributed Version Control Systems (DVCS), will enterprises be next?

  • Swarming Across Distance

    "Swarming" is a technique whereby many members of a team work together to deliver a User Story, taking advantage of the skills of many team members working together at the same time. It is recognised as a powerful approach to delivering high quality stories quickly. Johanna addresses how to achieve the same results when your team is geographically distributed?

  • Net-Map - A Toolkit to Understand and Visualise Stakeholder Influence

    Net-Map is a tool developed by Eva Schiffer that allows you through interviews to visualise and analyse how different people and groups influence a particular situation. It is of interest to Agile teams as it can help you understand who your stakeholders are, how they are connected and the level of influence they have. InfoQ recently caught up with Eva and asked her a few questions.

  • The Developer-Tester Divide

    The evolution of the software industry has created two separate roles: The developer and the tester. Traditional software development put these two at odds. Now, agile practices are bringing them together again in order to meet the original business goal: working software.

BT