InfoQ Homepage Agile Content on InfoQ

Articles

RSS Feed

Newer Older

Tracking Schedule Progress in Agile

The challenge of knowing whether we are on track to deliver haunts projectmanagers and developmentmanagers at various levels as their organizations take on agile approaches to product and project development. Driving towards smaller work items and lower work in process brings the benefits of both better project risk management as well as more effective agile execution and learning.

Yuval Yeret
on Jan 01, 2014
I’d Rather Be Coding – Writing Things Down

For lots of reasons, most developers hate writing down anything that isn’t code. The Agile Manifesto deemphasizes documentation, but there are times on a project when a little documentation can go a long way. In this article, we will explore why collaboration over comprehensive documentation shouldn’t mean “NO” documentation – and when you should stop coding and start writing things down.

Nate McKie
on Dec 31, 2013
Monty Taylor and Jim Blair on CI and Test Automation at OpenStack

Monty Taylor and James Blair talk about the build and test challenges they face at OpenStack, and how they managed to tackle them. Managing hundreds of VMs on public clouds, integrating up to 400 commits a day and running thousands of test jobs on them are some of the challenges described.

Sai Yang
on Dec 29, 2013
Retrospectives Applied as “PROspectives"

We can view situations in our work as opportunities from which to learn how to better handle similar situations in future, by looking back and asking “How will I deal with future situations like this to improve my results?” PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements.

Hans-Peter Korn
on Dec 28, 2013
Book Review and Author Q&A - Explore It! by Elisabeth Hendrickson

Elisabeth Hendrickson has released a book on the practices, techniques and mindset of exploratory testing. Sharon Robson reviewed the book and raised some questions with the author.

Sharon Robson
on Dec 24, 2013
Architecture and Agility: Married, Divorced, or Just Good Friends?

This article describes the relationship between architecture and process of software development and how architecture can responds to a set of needs, such as functional requirements, operational characteristics, and developer habitability. It also talks about the role of pragmatic architects when working with developers and stakeholders.

Kevlin Henney Frank Buschmann
on Dec 21, 2013
The Gentle Art of Running a Lean Startup

Yiannis relates the practices and approach of running a Lean Startup organisation with the skills and disciplines needed in the martial arts through his practice of Brazilian Jiu-Jitsu. He shows how the underlying practices of both are very similar and how understanding the martial arts approach can assist in conserving energy and maximising outcomes in a lean startup organisation.

Yiannis Mavraganis
on Dec 20, 2013
Spreading CMMI Practices among Agile Teams in Big Organizations

Agile methodologies have become mainstream because they provide a better fit to the modern, changing software world. CMMI is a cross-organizational approach which has proven successful in terms of quality assurance and cost when executed properly. Big organizations with self-organized agile teams can achieve technical maturity levels, by using a common metalanguage and a good-practices catalog.

Nicolás Afonso Alonso
on Dec 16, 2013
Meet Elaine: A Persona- Driven Approach to Exploring Architecturally Significant Requirements

Often, requirements elicited from stakeholders describe a system’s functionality but fail to address qualities such as performance, reliability, & availability. Documenting these requirements is often overlooked because there are implicit assumptions that the system will perform to expected levels. This article describes a process developed on the idea of persona sketches to address this problem.

Jane Cleland-Huang
on Dec 15, 2013
Agile Walls

BVCs, TOWs and POWs are very important tools in the agile world but what exactly are they? BVCs are Big Visible Charts, TOWs are Things on Walls and POWs are Plain Old Whiteboards – information radiators all. Using the right wallware and the information they provide can make or break an agile team.

Sharon Robson
on Dec 14, 2013
DevOps @ large investment bank

This article is part of the “DevOps War Stories” series. In each issue we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. This time a very personal story on introducing a DevOps mindset at a large bank. In particular how the automation of configuration and release management processes enabled collaboration.

Niek Bartholomeus
on Dec 11, 2013
Applying Lean Thinking to Software Development

Lean’s major concept is about reducing waste, meaning anything in your production cycle that is not adding value to the customer is considered waste and should therefore be removed from the process. Steven Peeters explains how you can apply Lean principles in an IT environment.

Steven Peeters
on Dec 05, 2013

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles