A well-written User Story facilitates effective work for developers, testers, business analysts, product owners, and everyone interested in the project. But writing a User Story that will satisfy all the parties is a difficult task. Or is it?
There are a lot of good stories on Medium that talk about what a User Story is, and what it is not. I don’t think I need to reinvent the wheel, so let’s just see my favorite definition of User Story:
The stakeholders are defined as people who are invested in the project and who will be affected by your project at any point along the way, and their input can directly impact the outcome (wrike.com). That basically means everyone who will affect, or will be affected by the project.
There will be probably a lot of them in your project. Since they are crucial to your project, it’s vital for you to manage them well. …
Being a business analyst can be challenging. On your daily basis, you try to understand the needs of stakeholders, manage the requirements, and deal with UX details.
I guess that you already know the basics — how to work in Jira, what the Scrum is, maybe you have even read the BABOK Guide. With that said, I will share with you some more unobvious tips on how to become a better business analyst.
What landed me my first job as a business analyst?
During my career as a Business Analyst, I have seen a lot of confusing status flows. Sometimes it is about too many statuses and incomprehensible transitions between them. And sometimes it is that nobody in the project even remembers when and how the statuses’ changes are triggered. And sometimes it can be both.
If you struggle with understanding how the status flow works in this big application you were thrown into, or you are trying to document a flow that is getting more and more complicated every day — it’s high time to embrace it!
The first task is to…
Business Analyst by day, Board Game Player by night.