Agile software development is an iterative, evolutionary practice based on a set of values that prize individuals and interactions, working software, customer collaboration, and responding to change.

Unintelligent design – the abuse of ‘inspect and adapt’ in Agile practice

Our weekly rhythm (iterations)

Establishing a rhythm to our weeks and days has provided our team a sustainable pattern for predictably delivering work with quality. Our performance is an outcome of executing within this pattern repeatedly over time. I learned the concept of a team rhythm from Jeff Sutherland and ours is a scrum and has the shape of a game: a short time frame (one week), an achievable goal that constitutes “winning”, alternating periods of focused team work with opportunities to regroup, strategize … Read More

Hyperproductive? I don’t know but I’ll take it.

annotated burn up

I’ve written about how our agile practice, particularly continuous improvement, has re-organized our product and development group into one, high performing team. How this has resulted in less code, less waste, higher quality and more value. Jeff Sutherland talks about mature, agile teams achieving what he calls hyperproductivity. At this point, the team output accelerates and they outpace the organization around them. Performing beyond even our own expectations allows us slack to help our product team and our sponsors define … Read More

Continuous Process Improvement — Deliver Less Code at Better Quality to Achieve More

Spiral Starecase

In my last post I claimed we rebuilt our website properties with with half to one third the developers and with “about half 65%” the resulting code. All to justify my claim that “You accomplish more by doing less.” Now, I’ll back that claim with some metrics. Lines of code There are a number of tools for measuring ruby code size and complexity. The metric_fu gem does a good job a aggregating them. But because our retired rails application is … Read More

Continuous Process Improvement – Doing Less

I’m wary of the cliche’, “doing more with less.” When I started in my current role, my team consisted a development manager, a product manager, a business analyst, three developers, an outsource/offshore arrangement of 6-18 developers with its own full-time relationship manager and me, a non-individual contributor tech executive. We worked with a product team of three. We built our main US and six other variations over the course of 12-16 months – which was a great success in the … Read More