> the problem stated is often not the problem faced. 100% true! So many times I was assigned to the task in issue tracker, where requirements was written, esti

> the problem stated is often not the problem faced. 100% true! So many times I was assigned to the task in issue tracker, where requirements was written, estimation was made, but after I sat and tried to solve given problem, it turned out that 80% of issue description was false - real problem was totally different than it was written in task. What seemed right on planning meeting, turned out to be quite false in the process. But quite often managers/product owners etc. don't understand this. They often believe 100% in planning ahead and issue tracker/backlog descriptions... And when something is going off the track (like it sometimes does - when problem needs extra time for thinking through) they aren't so glad because thinking and design process was not budgeted in issue tracker (even if it could lead to the better design on the long run).