A few years ago I found an app called Todoist. Before that, I was trying to organise my life using plain old pen and paper. It wasn't working. So I did what any (geek?) would do, and turned to software! I've tried many, many ToDo apps, across all the major
If you've ever spoken to me, you'll probably know that I'm quite addicted to my (android) smartphone. Someone recently asked me a question that got me thinking: "Rachid, what would you do without your smartphone!?" My reply was instant.. "Nothing, I need my smartphone, I simply couldn't survive without it"
User stories are a fantastic tool, we can all agree on that. But it's far too easy to write user stories that are too large. Large stories bring a number of problems, including: The development effort required to deliver a story is hidden. They are written at a higher level,
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
One of the key traits of a Business Analyst is being able to separate the "What" from the "Why". Users of the system (and remember, stakeholder != user) generally have a pretty good idea of what they want to do, but sometimes their explanation doesn't tell the whole story. The line
