Getting On Top Of Your User Stories & Requirements (with Richard Awe, founder @ Requstory)

An interview with Richard Awe. Richard is a Senior Business Analyst with the European Central Bank who got bored writing all those requirements documents & user stories, and decided to build a tool to help him do that at scale. He's now here with Requstory, a platform that aims to help people write user stories fast. A day in the life of a business analyst at the European Central Bank, the sorts of projects he's working on, and whether banks can ever be truly agile How he moved from training as a scientist and wannabe process engineer to business analyst because he loved being close to the users & engineers What a business analyst actually does and how similar it is or isn't to being a product manager or product owner on an agile team How working on a big project & having to write loads of user stories led him to build a no-code tool to help him do that quicker.. and how interest from friends & colleagues made him decide to make it ready for primetime How he's managing the user feedback and trying to keep focused on delivering real value rather than any niche feature that comes up Some of the characteristics of a good or bad user story and how the ultimate point is always to be something that starts off a discussion When user stories might not work for you, the different types of stories you can use, what some of the alternatives might be & whether they're really just interchangeable And much more! Contact Richard You can reach out to Richard on Twitter or check out Requstory.