On Jul 16, 2013, at 4:40 PM, Ahmed Hammad <ahm507@...
IMHO, I would rather name it technical task or just task and keep the word "story" for valuable functionality to product owner.
If some development effort has no value to the Product Owner, it should not be done.
If it does have value to the Product Owner, it can be expressed in those terms, and should be.
"Technical tasks" are a sign of Scrum immaturity, IMO.
Everything that needs to be said has already been said.
But since no one was listening, everything must be said again. -- Andre Gide