In the book Kanban Change Leadership Klaus Leopold and Sigi Kaltenecker explore how Kanban can be deployed to get change done in organizations and to build a culture of continuous improvement. An interview on doing change in small steps, solving problems, using WIP limits, priorities and classes of service in Kanban, using the Theory of Constraints with Kanban, and getting results with Kanban.
Technical debt quantification tools attempt to quantify the existing technical debt in a software product. However, the present set of quantification tools suffers from various limitations such as limited or no support for quantification of all technical debt dimensions, generalized absolutization, and missing interest component. Hence, quantified cost and effort must be interpreted with caution.
Larry Cooper and Jen Stone have written a book which provides advice and techniques for blending agile practices with portfolio, program and project management, taking a value focused approach to managing the outcomes of initiatives rather than focusing on the activities and practices which are the center of many methodologies. They spoke to InfoQ about the book and the ideas behind it.
Projects can be categorized as failures because of cost overruns, late deliveries or poor quality, but the right estimation processes can increase the likelihood of project success 16
The book Fifty Quick Ideas to Improve Your Tests provides suggestions that cross functional teams that are doing iterative delivery can use to manage and improve their testing activities.
Little’s Law helps teams that use user stories for planning and tracking project execution, with a project buffer to manage inherent uncertainty of a fixed-bid project and protect its delivery date. 4
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.
An interview with Jan Bosch about getting benefits from increasing delivery speed, steps after adopting Agile and DevOps, using experiments to innovate, and practices for experimentation.
The book The Software Craftsman contains stories, examples and practical advice for software developers and other project professionals to achieve technical excellence and customer satisfaction. 1
Software developers spend time and energy on building the best possible products looking at web frameworks, using a NoSQL or SQL database, etc. There's another equally important aspect: culture. 1
Developers across the globe attend coderetreats to learn from each other and refine their software design skills, but how do they work? What do people say about them? How can we make them even better? 3
At then recent Agile Singapore conference James Grenning presented two technically focused talks - one on the importance of technical excellence and the other teaching test driven development. 3