Analyst’s corner digest #19
Top stories published in November — December 2023
Hi there!
Christmas is around the corner and the festive season is upon us. What a year it has been! Thank you to all of our authors and readers, who made this publication possible ;) I hope you enjoy some time off (if you are taking any) and I wish you a fruitful and successful year ahead.
Reflecting on the previous year, I’ve noticed a few strong trends in our articles. People are naturally curious about the AI (can you imagine how much this field has progressed recently!) and how it is going to affect the BA profession. The good news, it doesn’t seem likely AI will replace BAs. The realistic news, the BAs who know how to use AI will replace the BAs who do not.
There is also a strong focus on using and interpreting data, making data-driven and evidence based decisions and recommendation — but not in isolation from the stakeholders. The two worlds, the world of cold hard data and the world of vibrant and diverse humans, have to co-exist in harmony for great solutions to emerge.
In this issue of Analyst’s corner digest we’ve got the articles about:
- Requirements elicitation: building partnerships and committing to good requirements, asking the right questions and an intriguing: Why do we ask the most important question — “Why?”
- Strategy analysis: working with KPIs (and why you are doing it wrong), creating business case for IT projects, surveys, and a template for IT strategy
- Agile & SDLC: the Rock crusher method to manage the backlog, making the best out of stand ups, the role of BA in SDLC, and a case study for using MoSCoW prioritisation — for buying a car
- Career development: skills for a data analyst in 2024, and the business analysis accent (everyone has one!)
- Tech: integrated knowledge bases, machine learning tips, and a guide to git for a business analyst.
Enjoy the reading!
— yours, Igor
https://www.analystscorner.org/
Requirements elicitation
1) Forging a Collaborative Customer–Development Partnership
by Karl Wiegers
Excellent software products are based on excellent requirements. Excellent requirements result from effective collaboration between developers and customers, and in particular, actual users: a partnership. A collaborative effort can work only when all parties involved understand what both they and their collaborators need to be successful. The business analyst (BA) typically is the point person who has to forge this collaborative partnership.
2) Is your organization committed to better requirements?
by Karl Wiegers
Ten signs that management doesn’t merely “support” requirements process improvements.
Software organizations that want to improve how they develop and manage their requirements face several challenges. When the organization changes its requirements processes, the interactions it has with other stakeholder communities change as well. People don’t like to be forced out of their comfort zone, so you can expect some resistance to proposed process changes. It’s helpful to understand the origins of the resistance so you can both respect it and defuse it.
3) Involving the Right Stakeholders in Business Requirements Gathering
by Nelson M.
In project management, successful outcomes hinge on thorough and accurate requirements gathering.
One key factor in this process is the involvement of the right stakeholders — individuals or groups with a vested interest in the project’s success.
From top-level executives to end-users, each stakeholder plays a unique role in shaping the project’s direction.
4) Ask Open-Ended Questions to Elicit Open-Minded Responses
by Karl Wiegers
“What do you want?” is hardly the most useful question a business analyst (BA) can ask during a requirements elicitation discussion. Sure, you’ll get some answers, but they’ll likely just skim the surface. Many online resources suggest other useful questions to ask when eliciting requirements, such as an extensive list from Laura Brandenburg.
Open-ended questions that don’t solicit a brief, fixed answer are valuable during both requirements discussions and any other type of interview or conversation, as well. They invite the participants to expand their reply, explain their thought process, and broaden the dialogue’s scope into fresh areas
5) Why Ask Why?
by Karl Wiegers
During a software reengineering project, a business analyst (BA) named Dawn asked one of the developers why a utility company fee calculation was being performed a certain way in the existing system. “A government statute dictates how we have to calculate those fees,” was the reply. Upon investigation, Dawn discovered that in fact, the current system had not implemented the computation correctly according to that statute. The system had calculated these utility fees incorrectly for an embarrassingly long time. This discrepancy never would have come to light had Dawn simply accepted the stated need for the current formula.
6) The Significance of a Software Requirement Specification (SRS) Document
by Nelson M.
In software development, a Software Requirement Specification, abbreviated as SRS, stands as a fundamental cornerstone that bridges the barrier between the client’s envisioned software and the developer’s technical implementation.
It is a comprehensive document that meticulously outlines what the software will accomplish and how it will perform, thus serving as a guiding beacon throughout the software development process.
Strategy analysis
1) You Have Been Working with KPIs Wrongly — This is Why
by Nelson M.
Key performance indicators (KPIs) are the backbone of analytics, offering simple values with a complex background that communicates essential information.
However, the love-hate relationship with KPIs stems from their potential pitfalls — looking at the wrong data, susceptibility to manipulation, or focusing on irrelevant information.
2) How to Create Business Cases for Your Strategic IT Projects
by Shashi Sastry
All IT projects must advance business, not IT. Advancement firstly means financial success. So, if you are an Enterprise Architect or work in IT, you need to show how your solution will make or save money for the company and that it will take only a little while to do so. This is its Business Case.
It is a case for the solution as a business, not a case made to the business for the solution.
3) Surveys and Questionnaires for Strategic Decision Making
by Nelson M.
In every business organization, understanding the needs and expectations of customers and stakeholders is paramount. One effective method to gather these requirements is through the strategic use of surveys and questionnaires.
These tools not only facilitate efficient data collection but also offer valuable insights that can guide informed decision-making for the growth and success of a business.
4) A Standard Template to Define Your EA & Technology Strategy
by Shashi Sastry
Constant, well-managed change is the lifeblood of enterprise success. So, everything in the EA Practice leads to this — the Enterprise’s Architecture and Technology Strategy and Plan, the EATSP.
(Although this template is tailored for commercial businesses, it can be easily used for government and non-profit organisations by changing the inputs to be the motivations and plans of such organisations.)
The actual artefact is a Microsoft Word document, but I’ve extracted its contents here so you can study it directly.
Agile & SDLC
1) Managing backlog flow with the “Rock Crusher” method
by Nuno Santos
Managing the backlog is not always easy, given its importance. One can’t forget that the backlog is the only source of requirements for a product. Yet, it may have needs or requests from various stakeholders.
The backlog is valuable in dealing with unpredictability and uncertainty. But it can also disrupt progress and the flow of value, leading to significant setbacks.
IIBA’s new publication caught the attention of participants and social media during the last Building Business Capability (BBC) Conference. We talk about the book “The Rock Crusher: A Model for Flow-Based Backlog Management”.
2) Make daily stand-ups more Agile
by Karthick TVM
Have you ever felt daily standup as,
- a waste of time
- not getting any insights on progress towards the goal
- status meeting where every team member updates what they are working on
then, there is a high chance that the organisation or the team assumed that a set of rituals can make them agile.
3) Business Analyst Perspective in Software Development Lifecycle
by Nelson M.
As a business analyst, your role unfolds across the seven distinct phases that characterize a typical project.
In this article, I will take you through the key responsibilities and contributions you as a business analyst makes at each stage of the software development process.
4) Buying a Car Using MoSCoW
by Sergiu Pocan
Some friends of mine were recently looking to buy a used car. And they couldn’t agree on what to buy. When they mentioned that I realized they had a prioritization problem. And MoSCoW might help them find what they are looking for.
Career development
1) Data Analyst in 2024: Skills, Education, and Career Pathways Unveiled
by Nilimesh Halder, PhD
In the ever-evolving world of technology and business, data analysts have become crucial for translating numbers into actionable insights. As we step into 2024, the pathway to becoming a data analyst encompasses a blend of education, skill development, and understanding of emerging trends in data analytics.
2) What is the accent of Business Analysis?
by Fabrício Laguna — The Brazilian BA
Just like me, business analysis also carries a sound that reveals its origin. This communication accent should not limit its scope. I have consistently strived to improve my English in presentations, conferences, meetings, and classes. However, despite my intense dedication, my Brazilian accent persists. I was born and raised in Brazil, and Portuguese is my native language. Anyone listening to me speak English immediately recognizes that I come from a different background. Similarly, business analysis carries its distinct roots.
AI & Tech
- Mastering Machine Learning: A Deep Dive into Parametric and Nonparametric Algorithms by Nilimesh Halder, PhD
Machine Learning (ML) has evolved remarkably, offering two primary branches of algorithms: Parametric and Nonparametric. Understanding these helps in selecting the appropriate algorithm for specific data analysis tasks. This article explores the key differences between these types, offering insights into their applications, and concludes with a coding example to illustrate these concepts. - Getting Up to Speed with Git as a Business Analyst, by Gabriel Botsie
The post describes Git and its usage on development projects. Supported by curated content, it further outlines key terms, platforms and tools. A summary and recommended actions follow. - Pioneering AI Frontier: Integrated Knowledge Bases, By Fabricio Laguna
In this second article in the series, I will explore a possible path for AI advancement that must have a profound impact on our society: access to integrated knowledge bases. - Exploring Iris Data Visualization with Seaborn’s Violin Plot in Python, by Nilimesh Halder, PhD
Data visualization is an essential skill for anyone who wants to explore and understand large datasets. One of the most popular libraries for data visualization in Python is Seaborn. In this article, we will focus on understanding how to use Seaborn’s violin plots to visualize the Iris dataset. By the end of this article, you’ll not only understand what a violin plot is but also know how to create one yourself using Python and Seaborn.
Sponsored section
Our IIBA endorsed CBAP preparation course has just been published on Coursera. It covers the entirety of BABOK Guide, and qualifies for 35 PDUs.
https://www.coursera.org/specializations/certified-business-analysis-professional-cbap
Visit our website for online training courses on business analysis and agile: https://www.analystscorner.org/ or if you want to read our book — Information Technology Essentials for business analysts and project managers.
Get in touch via editor.analysts.corner@gmail.com if you want your content featured. This keeps our publication going ;)
Thanks folks!
