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
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. 1.
One of the simplest techniques known to a BA can, in some cases, be the most effective. We call this technique, "The 5 Why's". What Is It The 5 Whys technique is a form of root cause analysis, which originated within Toyota, and is now a fundamental part of many
I read an interesting article recently, that used a restaurant scenario to highlight why the customer shouldn't see the inner workings of how food is created in the kitchen, and a lot of this rings true in the world of the BA too. The Roles Let's explain the roles in