4 ms·

What designer? The front end guy? The PM? What are you talking about? Have you got an architect making edicts from high? That in itself sounds like it is funda

What designer? The front end guy? The PM? What are you talking about? Have you got an architect making edicts from high? That in itself sounds like it is fundamentally not agile. I'm not especially a fan of TDD, but this comment makes no sense to me, it doesn't marry with my experience creating software. TDD is around individual methods, trying to make them decoupled. It is around unit tests. Changing the design simply means deleting those methods and throwing away those unit tests. Which you would do anyway.

sambeau 13y ago
What designer? Small agile teams don't have a designer and a 'front-end guy' and a 'PM' and an 'architect'. They often only have one and in my case he (I) is also the PM (or PO in our case). Design-led software requires a designer. In large projects you might break this up into lots of different roles with trendy titles but they are all just designers, just as a database programmer and a graphics programmer are just programmers. Changing the design simply means deleting those methods and throwing away those unit tests. Which is wasted work, wasted time and totally dispiriting for a developer.