BA Life

🌟 BA Tip of the Week – Business Analysis Techniques – User Stories🌟 🎯Purpose: The purpose of a user story is to clearly define a functionality/define a specific requirement from the end user’s perspective which is needed to deliver value 📚According to BABOK V3: User stories simply document a stakeholder's needs and the associated value in a concise and straightforward manner. They provide a foundation for identifying needs, prioritizing tasks, planning solutions, as a metric for measuring delivery of value, units for tracing related requirements and as units of project management and reporting. Generally, a user story is a brief statement describing the individual with the need, their intended goal, and the value it provides. Additional critical information that enhances the understanding of the story's scope can be included as supporting details. Focusing on stakeholder value, user stories promote further dialogue with stakeholders and group functional requirements for delivery. Approaches: 1️⃣ Title (this is optional) Describes an activity the stakeholder wants to carry out with the system 2️⃣ Statement of value: There is a commonly used format to define the statement of value which goes with ‘who’, ‘what’ and ‘why’ aspects of the functionality/activity/requirement "As a <who>, I need to <what>, so that <why>." 3️⃣ Conversation Usually a user story helps a team understand a feature and its value to the stakeholder. While the story outlines the need, additional details are developed as the story is worked on. 4️⃣ Acceptance criteria: A user story may be underpinned by detailed acceptance criteria, which define its boundaries and help the team understand what the solution must deliver to provide value to stakeholders. These criteria can be further supplemented with additional analysis models if necessary.Acceptance criteria are provided as statements that can be verified as true or false, typically through user acceptance testing (UAT) #iiba #IIBAColombo #IIBASriLanka #businessanalysis #srilanka #babok

I started Inside Business Analysis this time last year 😳 I picked up the mic and started the podcast because: 🎙 I'm a student of the game and want to keep learning from others and hope that the listeners can learn with me too. 🎙 I switched careers to become a BA so I understand those who want to know how to get inside the world of business analysis. Hopefully, the discussions will help them on their journey. 🎙 A lot of interesting things happen inside the world of business analysis, and I want to help shine a light on them. Three things that I've learned in the past 12 months: 🔸 I've interviewed guests from 10 different countries so far. Despite living thousands of miles apart and working in different cultures and environments, we all share the same joys and pains of Business Analysis. 🔸 Focus on the value of business analysis. Multiple guests have shared this sentiment and expressed that business analysis is not about creating artefacts but helping organisations solve meaningful problems and embedding positive change. This is the ROI of business analysis. 🔸 The number one thing that will help you succeed as a Business Analyst is passion. A strong passion for the work we do, the value we bring and for the profession at large. I don't know what the next 12 months will look like but I'm excited for the road ahead 😆! If you'd like to stay connected and keep hearing inspiring stories about Business Analysis make sure to join the Insiders newsletter: https://lnkd.in/eYxF7F9k P.S. Shout out to Karen Newnham, she was the first person to say yes to come on the podcast and kickstart this journey 😄

TL;DR: Please tell me what you think are the best (or worst) idioms business analysts use regularly? 🥺💬 And here's the (personal) backstory to the question ... 👇 I'm now getting better at identifying precisely when my partner has stopped listening to me when I'm talking about some business analysis thing. It has practically become a game. I win if I identify it as soon as it happens. My partner wins when manages to hide it. He's got better at maintaining eye contact and I've got better at spotting when they've glazed over. 👀 To be fair, I can go on and on (and on). 😅 The other day, during an (admittedly long-winded) description of something, he remarked "you do know that this is EXTREMELY boring." And when I protested, he clarified that he wasn't telling me to stop explaining, he just thought that it was important that I knew!!! 💀 This managed to halt my (allegedly boring) recount because I had completely lost my place by the time we had stopped laughing. 🤭😂🤣 But the exchange also got me thinking about the words we use. 💬 Specifically all the words we business analysts use that are complicated, pretentious, or just plain obscure. I think Robert Snyder calls it "verb sprawl." The sprawl part is spot on! We use a ton of words and phrases in very particular ways. They all have distinct meaning and connotations like it is our own little BA language. And I'm interested in exploring it, maybe via another series of posts ... Which is why I want to know \what words or phrases you use or hear that you think are good examples of our BA language. I want both good words and phrases that we should keep using, and unhelpful words or phrases that are contributing to the sprawl! Or put another way: I want both idioms and idiotics! Now I know I'll probably just end up with business words but I'm not sure it matters – I think there's a BA take in there somewhere still. Please help me with your examples!👇 #BusinessAnalysis #Idioms Please note: Am potentially butchering Robert's Verb Sprawl concept!! But I thought Sprawl was such a good descriptor and I couldn't steal it without credit!

Do you know the difference between a Professional Business Analyst and a Business Analysis Professional? 🤔 In this article, I use a detective metaphor 🕵♂️ to distinguish #role and #job concepts. That may help you to communicate what you do and the skills you use to do it. 😉 Key idea: "Every professional should be a business analysis professional." Tagline: #analysiseverywhere #businessanalysis #businessanalyst #thebrazilianba

What are perfect requirements? Unfortunately, they don't exist 😁. That's right, there's no such thing as perfect requirements 🫨. What does exist? 🙌🏻 Drawing out the right information from the right people 🙌🏻 Working with the right business people to define what's needed (goals, expectations, success criteria, priorities, risks, assumptions, dependencies) 🙌🏻 Collaborating with the right technical people to brainstorm solutions to meet customer and/or user goals, expectations, and needs 🙌🏻 Using the right techniques to model the right information 🙌🏻 Clarifying ambiguity 🙌🏻 Communicating information clearly and simply Requirements are a team effort 👌🏻. #requirements #collaboration #communication #businessanalysis #analysis #techniques #simplicity #community #engagement

Hello there 👋 New Monday - new video from the Passionate Business Analyst 😎 Today, we will discuss the Interview technique. In the video, I will cover the basics of the technique, its importance, and some PRO tips from me that I learned from my career. Enjoy and share this with those who need to learn it! https://lnkd.in/dA9tdizE #stakeholders #interview #technique #techniques #elicitation