Knowing the basics of software development can greatly improve the project outcome; however, that alone is not enough to prevent project failures. 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.
An interview with Gojko Adzic, David Evans and Tom Roden on why they wrote this book, how quantifying quality can support testing, balancing trust levels when testing large and complex systems, why automating manual tests is almost always a bad idea, on using production metrics in testing, how to reduce or prevent duplication in test code, and on upcoming books in the fifty quick ideas series.
When working on projects, it is most of the time necessary to forecast the project delivery time up front. Little’s Law can help any team that uses user stories for planning and tracking project execution no matter what development process it uses. We use a project buffer to manage the inherent uncertainty associated with planning and executing a fixed-bid project and protect its delivery date.
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
Frequently developers cause and face regular frustration often due to a lack of consideration for those who come after them. This article explores collective code ownership to address this. 2
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
All teams eventually face technical debt. In this article Jeremy gives see a useful metaphor for understanding technical debt, explaining it to stakeholders, and dealing with it in an efficient way. 4
This article describes what ‘Evo’ is at core, and how it is different from other Agile practices, and why ‘done’ should mean ‘value delivered to stakeholders’. 1