PROCESS: USER STORIES
After the mind map drawing up, we then moved to the user stories writing.
The user story has these three clauses.
As a persona, I want to do something, so I can derive a reward.
This part of the process was quite facilitated since the user was us, talent managers, so we could quickly identify with our humanized user.
We created these stories to anchor our view of what’s valuable in a nice, testable narrative about what we wanted to get, and we had a prior discussion about these as a product team with our designer Giuseppe and project manager, Jānis.
This is the experienced gained by Jānis in this step:
“I was strongly involved in planning and development process so that I could gain a valuable and useful experience and I feel that I am now able to pick up a lot of good things for the future. For me this was the first project as a project manager. I learned something new every day and grew a lot.”
After the planning phase, the user stories were sent to him and to his development team where these stories were taken and sorted into a backlog for the actual execution of software.
So, together with them and with our designer, we took care of sorting them, in order of priority, and then Jānis and his team cut them off at the amount of work they thought they could do in a single iteration.
And these iterations are usually two to four weeks, sometimes a little bit longer.