Last time, we talked about the sad situations where our user stories aren't detailed enough.
And we learned some of the reasons why this happens and what to do when this happens.
But sometimes, we have to act agile in imperfectly agile environments. And when I say "sometimes," I mean usually).
In this follow-up Tutorial Tuesday, we'll dive deeper. We'll cover:
- The special case where a remote development team needs more detailed requirements
- Artifacts you can use to help them fill in the blanks
- Practices that can you help you spur the collective team toward greater agility