Project Requirements vs. Stories
Some ideas or concepts are by nature perfect. Look at the wheel; it has remained the same for thousands of years. Wired to think in terms of stories, humans are natural storytellers. When we hear stories, we can’t help but imagine ourselves being inside them. Like the wheel, it has always been this way. It’s not often that things stay the same in the technology ecosystem. This video was shot eight years ago and is still just as relevant in 2022.
This short video discusses Project Requirements vs. Stories and their role in the ops and application environment. Sometimes, frustrating discussions can take place around the concept of requirements. There are many players on the contract bringing about different requirements. Everyone wants to understand the deep requirements, but putting them front and centre can create a problem. Players are constantly looking to put a check in the numerous requirement boxes once they’ve been met. The trouble in this comes when you have a mass amount of data to break down. There can be a lot going on in the ops and application space and far too many moving pieces to meet just the requirements. We don’t instinctively think in terms of requirements. They are there, and they are essential, but it is the operational story that matters.
It’s all about the stories.
Also published on Medium.