This is a serious problem. Your project exists to serve somebody, and your success is directly proportional to understanding what they want, so that you can build it. You need as much communication bandwidth between the programmers and those people as possible.
Read the rest of this entry »
“Lazy YAGNI”
You Aren’t Gonna Need It can lead to some silly situations if you interpret it too pessimistically. The pessimistic (and wrong) interpretation is that you should pretend that the user story you’re implementing is the only one you know about. This equates to doing zero up-front design, because you’re only concerned with whether the design satisfies the user story you’re currently implementing. The price of making this mistake is design churn: each new requirement may incur a large rewrite of existing code. This is obviously not a recipe for productivity.
Read the rest of this entry »
Do The Simplest Thing That Could Possibly Work
This does not mean “do the least work possible”. Doing the least possible is not XP, it is hackery, which is the methodology that leads to a Big Ball of Mud.
Read the rest of this entry »
Extreme Programming Experiences: Introduction
Over the last six months I’ve had the privilege of working in a software development team that was practicing the closest thing to a full implmentation of XP that I’ve ever seen.
Read the rest of this entry »
(1)
(8)
(14)
(10)
(3)
(5)
(4)
(16)
(2)
(2)
(3)
(1)
(7)
(5)
(1)
(13)
(2)
(5)
(27)
(15)
(5)
(5)
(1)
(2)
(2)
(2)
(2)
(1)
(2)
(5)
(2)
(7)
(3)
(4)
(14)
(19)
(3)
(4)
(34)
(36)
(3)
(1)
(19)
(11)
(6)
(3)
(18)
(1)
(22)
(15)
(9)
(6)
(2)
(2)
(5)
(2)
(1)
