I'm working on a project which runs as a process, on a regular basis. The results of the projects daily run are used by other projects. This brings me to question how our team writes stories.The normal format, As a [role] I want [goal/desire] so that [reason] does not seem to apply, but at the same time I'm doubting that.This is what we do now: The system shall execute after process ABC has finished successfully.Should we be using the other projects (that utilize the data from our process) as the role portion of the stories? What we do now just seems too much like requirements..
How to write stories for internal projects
agile;stories
The key of the As-a-So-That-I-want story template is simply to remind you that you need to know WHO, WHAT and most importantly WHY of your user story. You can pretty much use any format you like as long as you can capture those elements.For internal project, if all of your WHO is the same person for whatever reason, it might be silly to just keep writing the same thing over and over so if I were you I will just omit it.However, the typical system-shall-do-this format mostly capture WHAT and not WHY. Make sure you do not omit that.