The Two Faces Of The Agile Manifesto

agile coding scrum

Will Faught

1 minute

Robin Message on the mismatch between the parts of the agile manifesto concerned with technical craft and those concerned with project management:

So, to summarise, almost every method and technique that was represented at the Agile manifesto was concerned with technical craft. XP is a methodology for software development, and as such, seven of the twelve practices are about how the software is written (pair programming, TDD, continuous integration, refactoring, simple design, system metaphor, coding standards). The craft/Pragmatic contingent weren’t designing a methodology for a team per se; they were concerned with how the software was written. But Scrum? Go read the Scrum Guide. It’s not long, I’ll wait. […]

It’s not a software methodology. Or even a technical methodology. It’s aimed at project managers who have this amorphous “development team” that they are trying to make develop what they want, faster. Scrum could be used to design HelloFresh menus (it isn’t, to my knowledge) or apparently to prepare a ship for war. If you search for the word software in the guide, that quote above contains the only two mentions!

π