InfoQ Homepage Agile Content on InfoQ

Articles

RSS Feed

Newer Older

Interview with Capers Jones on Measuring for Agile Adoption

Why would you want to use measurements if you are adopting agile? Because top executives would like to know how projects will turn out before spending money on them, and measuring results helps to improve future predictions. Capers Jones shows how you can measure productivity and quality, and looks at agile practices that have proved to be beneficial for teams.

Ben Linders
on May 30, 2013
Software Development: How the Traditional Contract Model Increases the Risk of Failure

Susan Atkinson and Gabrielle Benefield argue that the standard contract model for software development is based on outdated and flawed assumptions, and that this is contributing to the high rates of failure in IT projects, regardless of whether the IT projects are resourced internally or outsourced to a third party. The contract model is in need of a total overhaul.

Gabrielle Benefield Susan Atkinson
on May 28, 2013
Managing Build Jobs for Continuous Delivery

The number of jobs in a continuous integration tool can range from a few to several thousand, all performing various functions. There is an approach to manage these jobs in a more efficient manner.

Martin Peston
on May 24, 2013
Managing the Unmanageable: Author Q&A

Mickey Mantle and Ron Lichty have written a book about managing and employing programmers. The book examines the characteristics of programmers and programming teams and discusses how to manage them. They provide a variety of tools along with many rules of thumb they’ve collected through the years.

Shane Hastie
on May 13, 2013
InfoQ Interviews David J. Anderson at Lean Kanban 2013 Conference

If they were to carve a new Mt. Everest into the mountains surrounding Silicon Valley, then alongside Dijkstra, Kernighan, The Three Amigos and The Gang of Four they would need to make room for David J. Anderson, father of Kanban in the software development industry. The Lean Kanban Conference took place in downtown Chicago last week, and InfoQ interviewed Anderson.

Victor Grazi
on May 09, 2013
Managing Technical Debt

Technical Debt is widely regarded as a bad thing that should be paid back as soon as possible, however it can be a strategy that helps balance short-term wins and long-term productivity. The article describes different ways that a project could pay back Technical Debt and what factors must be considered when deciding if you should repay, convert debt or just pay the interest.

Eberhard Wolff Sven Johann
on May 06, 2013
Implementing Kanban in Practice

At the Lean Kanban conference, InfoQ asked Dr. Arne Roock how a team can evaluate whether Kanban is the right tool, and how to kick it off. Dr. Roock offers some prescriptive advice.

Victor Grazi
on May 01, 2013
Interview with Jason Little about Agile Transformation

Agile transformation is about focusing on organization change and understanding the complexities that come with it. An interview with Organizational change coach Jason Little about approaches for organizational change, culture, feedback and learning, and using the lean startup approach.

Ben Linders
on Apr 29, 2013
Dialogue Sheets Revisited

Last year Allan Kelly wrote an InfoQ article about a tool for retrospectives - Dialogue Sheets. A year and over 2000 downloads later he looks at how they are being used and ways they have been adapted in the wild.

Allan Kelly
on Apr 22, 2013
DevOps @ Spotify

This article is part of the “DevOps War Stories” series. Each month we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. In this issue we learn how lessons learned from DevOps have permeated engineering management at Spotify. The result is a healthy Potlac with team leader, product owner, agile coach.

Mattias Jansson
on Apr 19, 2013
The Seven Information Smells of Domain Modelling

Domain modelling is a powerful technique that many IT professionals have in their toolkit. Unfortunately a couple of issues with domain modelling have caused it to fall out of favour over the past few years, especially in Agile circles. Two real problems with the approach are that it takes too long, and that it is prone to “analysis paralysis”. This is an approach that addresses these issues.

Kent McDonald Chris Matts
on Apr 18, 2013
Agile Software Architecture Sketches and NoUML

Understanding the software architecture of what you're building can prevent chaos and encourage collective code ownership. In the race for agility though, many teams struggle to do this, particularly since they've abandoned UML in favour of "boxes and lines" sketches. Moving fast requires good communication, but how do you do this without resorting to big design up front and UML?

Simon Brown
on Apr 16, 2013

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles