Team Writing Own Sprint Stories: Execution Engine

I started an initiative in 2021 was to have the team start writing their own sprint stories - the series starts here

There’s a coding parallel between writing own stories and tests for code.

With this parallel, the transition to having the team writing own stories would be easy, right??

There’s inherit resistance to any change. With the sprint-based waterfall workflow I accidentally instituted, the team is an execution engine:

1. Take story from queue
2. Complete story as directed
3. Deliver results

This workflow requires completing these steps:

1. Figure out problem
2. Break down to stories according to current system
3. Write story
4. Put on queue

Of course, I was doing these steps and found step 2 becoming an issue.

I found out the team needs to build new skill