Welcome to my Corner of the Internet

This is an entry in my series of post about techniques that are useful to Business Analysts. I am using the IIBA’s BABOK V3 (2015) as my source for what a user story it. It is worth keeping in mind that I come at this a as a IT Business Analyst from a consultancy that works on ERP systems A user story is one or two sentences that captures what is needed out of a solution. They take a the view of what a user would be trying accomplish when they use the functionality.Users stories are used to define what features should be included in a solution. They are not intended to be complete requirements which makes them more useful when trying to scope a project rather then an explicit list of what needs to be built. User stories are suppose to be short and focused on a single activity. Having them focused is very useful as it allows them to be used as a checklist to confirm that the solution meets the needs of the users. I have found this useful as if they are too broad then there are times where they can be half met which makes it difficult to communicate progress to stakeholders. User stories are not something that works for every project. When the project is strictly integrating data between two systems there are no real “users” of what is being developed making user stories not useful. They are useful any time a business process or product is user facing. ...

Projet write ups in progress