Thoughts and views on Software Development and Stoicism.
As a Business Analyst, one of the key features of a requirement is the priority. I guess it’s important to state up front that all requirements are important. If they weren’t, we wouldn’t even bother documenting them, thus removing the need to even assign a priority. But having a priority is useful to help deliver …
User stories are a great way to manage requirements, they are small, light, to the point and make the benefit of any requirement explicit. However, just like traditional requirements, there is a skill required to ‘get them right’. Below is a quick hash up of some user story mistakes. The Acceptance Criteria The acceptance criteria …
As a Business Analyst, user stories a big part of my day to day job. They set the baseline for the whole software delivery lifecyle. If the user stories are wrong, the software that gets delivered will be wrong. That’s a fact. Even though user stories are fundamentally the same thing as traditional requirements, they …