BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Measurement Content on InfoQ

  • Q&A with Mayank Prakash: DevOps in UK's Largest Government Department

    Mayank Prakash, Director General, CDO and CIO of UK’s Department for Work and Pensions told the DevOps Enterprise Summit London audience how the largest UK’s government department is moving away “from an organisation based on traditional vendor outsourcing, traditional structures and service delivery models to one with digital in its DNA”. InfoQ had the opportunity to do a Q&A with Mr. Prakash.

  • Q&A With Robert Scherrer: DevOps on the Backbone of the Swiss Financial Center

    Starting with a small core team, and a DevOps approach around 5 + 1 dimensions - skills, organization, process, infrastructure, architecture + mindset & attitude - SIX has been transforming how IT and the business work together to break the silos and align themselves along value streams. InfoQ took the opportunity to talk with Robert Scherrer, head of software dev at SIX, about this journey.

  • DevOps and the Key to High Performance: Nicole Forsgren at the DevOps Enterprise Summit London

    In preparation for the upcoming DevOps Enterprise Summit in London, InfoQ sat down with Dr Nicole Forsgren, CEO and chief scientist at DORA, and discussed the fundamentals of DevOps, the challenges of specifying organisational goals, and how to measure high performance.

  • Benefits of Agile Transformation at Barclays

    Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.

  • Leadership Fit for the 21st Century: Challenges in an Agile Environment

    This first post in the series on leadership fit for the 21st century covers the talk given by Hendrik Pothof from ING and Michael Bres from Axis into Management about leadership challenges in an agile environment.

  • Measure and Improve Code Quality

    InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.

  • Measuring in Agile Teams

    At the Agile Tour London 2015 Doug Talbot gave a talk titled "Do you know how fast you're going?". InfoQ interviewed him about difficulties with estimation and planning, the measurements that agile teams use, objectively measuring productivity, his view on the #NoEstimates movement, and asked him for ideas that can help teams to make measurement more meaningfully.

  • Key Takeaways from DevOps Days Ljubljana 2015

    DevOps Days Ljubljana 2015 took place on the 3rd and 4th April and talks covered the full CAMS spectrum: Culture, Automation, Measurement and Sharing.

  • Evidence-Based Managing of Software Development

    If organizations want to make informed management decisions to maximize the delivered value they will need to gather evidence about value says Gunther Verheyen. InfoQ interviewed Gunther about evidence based software management and finding evidence, how Scrum relates to evidence-based managing, challenges in scaling agile, and advice for enterprises that want to adopt Scrum.

  • Getting People to Limit Their Work In Progress

    Kanban talks about limiting work in progress (WIP) as a way to manage workflow. “Limiting WIP is hard enough, but selling it can be nearly impossible” said Jim Benson. At the Lean Kanban Central Europe 2014 Conference he talked about how to convince others to limit WIP.

  • Using Complexity Measurements to Improve Software Quality

    Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.

  • Getting your Quality Management System Used

    Creating and maintaining a Quality Management System (QMS) can be difficult, certainly when organizations have multiple product lines where different regulations and standards are applicable. InfoQ interviewed Willem van den Biggelaar about the benefits of having a QMS, dealing with multiple regulations, assuring adherence, how a QMS can support agility and deploying a QMS in an agile way.

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

  • Measuring the Value of Agile Adoption

    When defining a business case for adopting agile, the question can arise how you can measure the business value that can be delivered using agile software development.

  • Working with Investors as a Lean Startup

    Entrepreneurs using lean startup can work with investors to raise capital for their business. Business plans from lean startups often differ from traditional startups and lean startup encourages learning from failure and to pivot, which might scare off investors. Can entrepreneurs and investors together use the lean startup approach to do fundraising?

BT