This first article in the series on the Kanban “nine values, three agendas” model, explores the sustainability agenda: a common approach to Kanban adoption at the level of individuals and teams, often motivated by the need for relief from unsustainable practices and workloads. This sustainability agenda draws on the Kanban values transparency, balance, and collaboration.
Maintaining a legacy application can make you feel like mice in a maze. In this article Ping Chen shares her experiences on how to pragmatically maintain a large legacy application. "Pragmatic” is the operative word; since a legacy application can have lots of technical debt, one has to be strategic in choosing the right battles.
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.
Developers hate writing down anything that isn’t code. But there are times on a project when a little documentation can go a long way. In this article, we discuss when and why to write things down. 5
PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements. 12
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. 1
This article describes the relationship between architecture and process of software development and how architecture can respond to functional requirements and developer habitability. 1
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 2
Agile and CMMI complement each other well. Big organizations with self-organized teams can achieve technical maturity levels, by using a common metalanguage and a good-practices catalog. 1
The concept of walls as information radiators and communication tools is central to the agile mind-set. Using the right wallware and the information they provide can make or break an agile team. 1
Software can take inordinate amounts of time to develop and test. With the cloud, achieving hyper-agile software development is feasible with these key principles for building a next-gen dev/test lab.
This article summarizes the key takeaways and highlights from QCon San Francisco 2013 as blogged and tweeted by attendees.