-
When we are prioritizing work, we tend to ignore the team knowledge about the work to be done What seems easy at first, it might cause the whole team to stop to learn about that part of the system Then, it comes as a surprise why it took us that much and the other stuff delayedOn twitter.com
❤️ 3 Favorites Mood -2 🙁
-
The work to be done wasn't much, but the amount of time required to: - Understand what's done - The code and tests - The Use Case Flow - Be sure you don't break anything Doing it isn't relevant compared with the time required to learn about what needs to be donePermalink On twitter.com