Requirements Clarification: When a Business Analyst is Not Consulted скачать в хорошем качестве

Requirements Clarification: When a Business Analyst is Not Consulted

📦 BA Quick Start Bundle: https://shop.why-change.com/pages/bun... 📘 Get Yulia's book "Business Analyst: A Profession and a Mindset": https://www.amazon.com/dp/199912202X 💼 BA Portfolio Building course – with Yulia’s feedback 📬 https://shop.why-change.com/en-ca/pro... ⚡️ Subscribe for BA Mindset video library: https://shop.why-change.com/en-ca/pro... 📂 Free/Paid BA templates and downloads — https://shop.why-change.com/en-ca/col... What should a BA do when someone goes over their head for requirements clarification? When business analysts are not consulted, they don't get a chance to clear up the confusion about requirements. In this video, Yulia Kosarenko offers possible explanations and strategies for a BA to change the dynamics of the project team. Watch until the end for actionable advice. 👀 See next: ⏭️ How To Advocate For Your Needs As A Business Analyst (So That You Can Do Your Job Well)    • How To Advocate For Your Needs As A Busine...   ⏭️ What To Do When Stakeholders Disagree on a Value of a User Story?    • What To Do When Stakeholders Disagree on a...   ⏭️ 10 Essential BA Competencies Required Today (Business Analysis Skills in Demand)    • 10 Essential BA Competencies Required Toda...   ⏭️ When No One's in Charge: Untangling Requirement Ownership for Business Analysts    • When No One's in Charge: Untangling Requir...   ⏭️ Time-Saving Tactics: 7 Strategies to Engage Busy Stakeholders    • Time-Saving Tactics: 7 Strategies to Engag...   📌 Navigation: 00:00 Beginning: answering BA questions 00:47 The question: You are not consulted about requirements during the development 02:35 Reason 1: It is assumed that a BA is not needed after requirements sign-off 03:19 Reason 2: BA is not interested in design and development 03:30 Reason 3: BA takes questions personally 05:02 Reason 4: BA does not have a relationship with the business 06:50 Reason 5: The project has not established clear roles & responsibilities 08:00 Reason 6: Lack of relationships with the development and QA team 08:56 Reason 7: BA is lacking in technical acumen 10:38 Where to find more information 🔗 Useful Links: 💭 Website: https://why-change.com 💭 Subscribe to the Why Change channel and hit the bell to receive all the updates:    / @whychange   💭 Connect with Yulia on LinkedIn:   / yulia-kosarenko   💭 Get your copy of the book Business Analyst: A Profession and a Mindset: https://www.amazon.com/dp/199912202X​​ 💭 Courses: https://courses.why-change.com/course... 💭 Training programs: https://why-change.com/corporate-trai... 💭 Why Change blog: https://why-change.com/blog/​​ 💭 Publications: https://why-change.com/publications/​​ 💭 Corporate consulting: https://why-change.com/consulting-ser... 💭 Webinars: https://why-change.com/speaking/​​ 💭 Book me for speaking: consult@why-change.com 💭 About: https://why-change.com/about Hello! I’m Yulia Kosarenko, the owner and principal of Why Change Consulting Inc. Before I tell you more about myself, let me explain where the name “Why Change” comes from. An effective change starts with knowing WHY – your strategy and business objectives. This strategy then needs to be shaped into views that can be communicated to your employees – your target business capabilities and operating model. That, in turn, will drive the changes that you choose to implement to achieve your objectives. Without clear communication of the strategy, how can business requirements accurately reflect your desired target state?