Does Doing The Simplest Thing Mean Ignoring User Stories

Suppose we are working on implementing a UserStory. Then we realise that some other UserStory needs something that we don't want to deal with right now. What should we do?

Do we DoTheSimplestThingThatCouldPossiblyWork right now and ignore the future requirement? (Ignoring a documented requirement is not the same as ignoring something you haven't been asked for).

Or should we make allowances for it right now?

-- DavidPlumpton

Implement the current user story. Worry about the other one when you get to it.

If you go off on a tangent and implement part of another story, it is all too easy for that to lead to another tangent, etc. so that the original story doesn't get completed on time. And neither do the others.

~ Richard Rapp

Amen. Try to get the current story finished before you worry about other stories. Sometimes this seems dumb, and sometimes it is, but usually it works out better in the long run. It bugs me when I hear folks clamoring for "reuse" before they even have "use". Once you've done both stories, refactor the common bits if necessary. -- EricHodges