InfoQ Homepage Software Craftsmanship Content on InfoQ
-
Interview and Book Review: Specification by Example
Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.
-
Agile Strategy Manifesto
A successful business strategy starts with unique value creation. But for an organization to realize the full benefit of it’s business strategies it must develop and maintain them using an Agile approach. An Agile mindset and careful application of feedback provided by an iterative implementation will help retain value and turn good business strategies into great business strategies.
-
QoS for Applications: A Resource Management Framework for Runtimes
This article draws an analogy between QoS for networks and for applications, resulting in a mapping guide between the two and introducing a production solution for Java, (J)Ruby, and (J)Python apps.
-
Agile Architecture Interactions
James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.
-
Bridging Internal and External Software Quality with Sonar and JaCoCo
In this article, author Olivier Gaudin discusses the differences between internal and external software quality and how to perform the software quality assessment using tools like Sonar and its new extension JaCoCo.
-
Implementation Decision Rationales – Program Comprehension in Agile
Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.
-
Agile Finance: Story Point Cost
This article ties a rather abstract and developer centered concept (story points) to the real world of business (spreadsheets and ledgers). Making this connection is essential for management.
-
Ars Magna: the revolution is overdue
This essay is an intentionally provocative and controversial call for a real revolution in how we conceive of and practice software development. The intent is to stimulate discussion.
-
Who Moved my Product Value?
At the outset, it seems like agile is all about short-term focus and a product life cycle is typically the polar opposite – it runs the total gamut in the spectrum that is the life of the product, starting from incubation to end-of-life. So, how does one attribute the relationship between the two? This is where product value comes in.
-
Agile Team Meets a Fixed Price Contract
Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.
-
Are You a Software Architect?
The line between development and architecture is tricky. Some say it's fake, that architecture is an extension of the design process undertaken by developers; others say it's a chasm that can only be crossed by lofty developers who believe you must abstract your abstractions and not worry about implementation details. There's a balance in the middle, but how do you move from one to the other?
-
Agile Lessons from a Management Guru
Deming was one of a select group of thought leaders who have shaped modern management over the last century. He is best known for the impact he had on Japanese businesses with his teachings on design, manufacturing, sales and quality. The first three of Deming's fourteen points are examined in detail in the context of Agile software development.