Agreed! I know User Stories come from XP but the one anti-pattern that I cannot stand is analysis, design, development and QA user stories.
Starting as soon as possible on sprint 1 like you say Troy is key! In my opinion, time and again I have seen these agile anti-patterns don’t give us the full benefit of whatever framework we intend to adopt.
If the prep work to start our sprint is more than the length of the Sprint itself, why call it a Sprint 0? Ultimately, we are looking for value at the end of the sprint.
I would rather learn from a failed sprint than experiment it with a sprint 0.
And in my opinion Zero doesn’t have any value