Ask yourself these questions: Do these users in your user stories exist and have you ever spoken to them? How are these features helping your customers achieve their goals? Are these benefits based on any quantitative or qualitative data? — The Product Owner’s Dilemma | Scrumology Read more →
EppsNet Archive: Extreme Programming
Software Development is Capable of Much, Much More
If there is one message I would like to communicate, whatever your job title and however your work is touched by software development, it is this: software development is capable of much, much more than it is currently delivering. — Kent Beck, Extreme Programming Explained Read more →
The Word “Requirement” is Just Plain Wrong
Software development has been steered wrong by the word “requirement,” defined in the dictionary as “something mandatory or obligatory.” The word carries a connotation of absolutism and permanence, inhibitors to embracing change. And the word “requirement” is just plain wrong. Out of one thousand pages of “requirements,” if you deploy a system with the right 20% or 10% or even 5%, you will likely realize all of the business benefit envisioned for the whole system. So what were the other 80%? Not “requirements”; they weren’t really mandatory or obligatory. — Kent Beck, Extreme Programming Explained Read more →
The Simplest Thing That Could Possibly Work
I ask people to think about the question, “What is the simplest thing that could possibly work?” I’m not asking you to think about what is too simple to work, just to bias your thinking toward eliminating wasted complexity. — Kent Beck, Extreme Programming Explained Read more →
Change Isn’t the Problem
Everything in software changes. The requirements change. The design changes. The business changes. The technology changes. The team changes. The team members change. The problem isn’t change, because change is going to happen; the problem, rather, is our inability to cope with change. — Kent Beck, Extreme Programming Explained Read more →