<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nataliia Trester on Medium]]></title>
        <description><![CDATA[Stories by Nataliia Trester on Medium]]></description>
        <link>https://medium.com/@trester.nv?source=rss-41e13534f4c4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*GLjV8ERwSi9Z_UQG.</url>
            <title>Stories by Nataliia Trester on Medium</title>
            <link>https://medium.com/@trester.nv?source=rss-41e13534f4c4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:49:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@trester.nv/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Requirements Made Simple: A Practical Guide Using BABOK]]></title>
            <link>https://medium.com/@trester.nv/requirements-made-simple-a-practical-guide-using-babok-e9799cf46ef7?source=rss-41e13534f4c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9799cf46ef7</guid>
            <category><![CDATA[babok]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[Nataliia Trester]]></dc:creator>
            <pubDate>Wed, 01 Oct 2025 10:11:59 GMT</pubDate>
            <atom:updated>2025-10-01T10:11:59.956Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing I have learned from applying BABOK in a real project is that it doesn’t prescribe a strict step-by-step process. The guide lists tasks along with their inputs and outputs, but it never insists that you follow the chapters in order, which can be a bit confusing at first.</p><p>As the BABOK® Guide puts it:</p><blockquote>“The BABOK® Guide defines a list of business analysis tasks… Tasks are grouped into knowledge areas. Business analysts perform tasks from all knowledge areas sequentially, iteratively, or simultaneously. The BABOK® Guide does not prescribe a process or an order in which tasks are performed. Tasks may be performed in any order, as long as the necessary inputs to a task are present.”</blockquote><p>In practice, you can start working on requirements at almost any point in the project. Sometimes I start by clarifying business goals, and sometimes, during the first interview, I simply sketch out a rough process plan in an Activity diagram and see where it leads. That’s the beauty of BABOK®: it’s a framework, not a recipe. In this article, I’ll share how I’ve seen requirements-related activities from BABOK® unfold in real projects, how they often overlap, and how they connect in practice.</p><h3>Requirements classification schema</h3><blockquote><em>“A requirement is a usable representation of a need. Requirements focus on understanding what kind of value could be delivered.”</em> — BABOK® Guide</blockquote><p>In my experience, requirements in real projects don’t come in a single format. The key thing is that they clearly capture the need and can actually be used by both stakeholders and the solution team.</p><p>To make sense of all the different requirements, BABOK® suggests a simple classification with four main categories:</p><ul><li><strong>Business Requirements</strong> — these describe the problems, opportunities, or constraints that the future solution should address. They answer the question, “Why are we doing this?”. You can take them as the output of the <em>Analyse Current State</em> task.</li><li><strong>Stakeholder Requirements</strong> — these capture what stakeholders need and expect, linking their objectives to the solution. Basically, they answer, “What do different groups really need?”</li><li><strong>Solution Requirements</strong> — these define what the solution must provide, both in terms of capabilities and qualities. They break down into: <strong>Functional requirements</strong> — what the solution must do. <strong>Non-functional requirements</strong> — how well it should perform, like security, performance, or usability.</li><li><strong>Transition Requirements</strong> — temporary capabilities needed to move from the current state to the future state. This could include things like data migration, training, or deployment support.</li></ul><p>I find this classification really useful because it prevents mixing up strategic goals with detailed solution features. It gives everyone a shared language, so it’s easier to see whether a requirement is about the <em>why</em>, the <em>who</em>, the <em>what</em>, or the <em>how</em>. And in real projects, having this clarity saves a lot of back-and-forth later on.</p><h3><strong>Specify and Model Requirements</strong></h3><p>You’ve probably come across the term <strong><em>Requirements Elicitation</em></strong> in many sources. In BABOK®, the focus is a bit different: we first elicit information, and then we specify and model requirements based on what we’ve learned.</p><p>In your initiative, you don’t have to wait for everything to be perfectly defined — you can start specifying and modeling requirements in parallel with other activities, even at the very beginning of a change initiative.</p><p>There isn’t a single “best” way to model requirements — it really depends on who you’re talking to and what you want to achieve. BABOK® provides a bunch of techniques, but the most effective business analysts adapt them to their audience.</p><p>From my experience, some of the most useful techniques from BABOK® are actually the ones people don’t talk about as often. They may not sound as exciting as user stories or prototypes, but when applied at the right time, they can save a project from serious trouble. A few examples:</p><p>• <strong>Non-Functional Requirements Analysis</strong> — teams often underestimate it. Everyone loves to talk about features, but things like performance, scalability, and usability are just as critical. I’ve seen projects where functional requirements were met perfectly, but poor performance ruined the user experience. This analysis helps prevent that.</p><p>• <strong>Glossary — </strong>it sounds simple, almost boring, but having a shared glossary of terms avoids endless misunderstandings. Especially in large organizations, I’ve learned that even basic terms like “customer” or “account” can mean very different things to different teams.</p><p>• <strong>Roles and Permissions Matrix — </strong>security and access rules are often treated as an afterthought. In practice, a clear matrix of who can do what helps not only IT but also business stakeholders see whether the planned access aligns with real responsibilities.</p><p>• <strong>Concept Modelling</strong> — when I first used it, it felt like overkill. But it quickly turned out to be a powerful way of aligning business and technical perspectives. Mapping out the core concepts and their relationships often reveals hidden assumptions and conflicting viewpoints.</p><p>The key thing to remember is that the technique itself isn’t the point — it’s whether it improves understanding. A UML diagram might be perfect for a dev team, but for end users, a wireframe works much better. I’ve often found that starting simple and iterating is far more effective than trying to get everything “perfect” on the first try.</p><h3><strong>Verify and Validate Requirements</strong></h3><p>One of the common challenges in working with requirements is distinguishing between <strong>verification</strong> and <strong>validation</strong>. BABOK® makes this distinction clear:</p><ul><li><strong>Verification</strong> ensures that requirements are expressed correctly, consistently, and unambiguously. It answers the question: <em>Did we define the requirements right?</em></li><li><strong>Validation</strong> ensures that requirements reflect the true business needs and that they will deliver value once implemented. It answers the question: <em>Did we define the right requirements?</em></li></ul><p>Both steps are essential: verified requirements that are not validated may be perfectly written but completely irrelevant, while validated requirements that are not verified may be valuable but impossible to implement correctly.</p><h3><strong>Requirements Architecture</strong></h3><p>As the number of requirements grows, it quickly becomes difficult to see the bigger picture. <em>Requirements Architecture</em> helps solve this problem. Its main purpose is to ensure that requirements, taken together, form a single coherent whole that supports business objectives and delivers real value to stakeholders.</p><p>One of the most practical tools here is the use of <strong>viewpoints</strong> and <strong>views</strong>.</p><ul><li>A <strong>viewpoint</strong> is like a template that defines how requirements will be represented for a certain group of stakeholders. For example, process diagrams for operations teams, data models for architects, or use cases for business users. Each viewpoint has its strengths, so no single viewpoint can cover everything.</li><li>A <strong>view</strong> is the actual set of requirements and designs built using a viewpoint. When you bring different views together, you get the full requirements architecture.</li></ul><p>In practice, I’ve seen that requirements architecture is not about “tidying up documentation.” It’s about creating a living structure where different viewpoints align, stakeholders understand their role, and the team can spot risks and gaps before they become expensive. Without it, requirements are just a flat list. With it, they tell a story that connects strategy, design, and delivery.</p><h3><strong>Connection with BA Planning and Monitoring</strong></h3><p>One of the points BABOK stresses is that requirement management is not something you “figure out on the fly” once the project is underway. The way requirements are traced, prioritized, approved, and changed is decided in advance, during the <strong>Business Analysis Planning and Monitoring</strong> stage.</p><p>In practice, this means that many of the activities we use later in the <strong>Requirements Life Cycle Management</strong> area are actually prepared earlier.</p><p>The relationship looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pAXbzLaw7xCtk7FDCdVucA.jpeg" /></figure><p>In other words, Planning and Monitoring are where the rules of the game are set. Life Cycle Management is where those rules are applied in practice.</p><h3><strong>Requirements Life Cycle Management</strong></h3><p>You can’t really manage requirements until they’re captured in some usable form. Once you have them, the <strong>Requirements Life Cycle Management</strong> area in BABOK describes how requirements are governed, traced, prioritized, and maintained throughout the project.</p><p><strong>A few tricky points to watch out for:</strong></p><ul><li><strong>Approval requires quality first.</strong> The <em>Approve Requirements</em> task only works with verified requirements. That means they should already be clear, consistent, and feasible before formal approval.</li><li><strong>Other tasks can start earlier.</strong> For activities like tracing, maintaining, prioritizing, or assessing changes, you don’t need a perfect level of detail upfront. You can start managing requirements while they’re still being refined.</li><li><strong>Trace, maintain, and prioritize only after consensus.</strong> It’s best to wait until requirements are approved (or at least agreed on by stakeholders) before you invest effort in tracing and prioritizing them. Otherwise, you risk spending time on items that might be rejected later.</li><li><strong>Requirements drive risk assessment.</strong> Prioritized requirements feed directly into the <em>Assess Risks</em> task in Strategy Analysis. Their priority helps determine which risks are most important to identify and manage during solution implementation.</li><li>Be sure you understand the difference:</li></ul><blockquote>“Requirements architecture: The requirements of an initiative and the interrelationships between these requirements.” — BABOK® Guide</blockquote><blockquote>“Requirements traceability: The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known.” — BABOK® Guide</blockquote><h3><strong>Conclusion</strong></h3><p>Working with requirements is never just about writing documents or filling in templates. As BABOK® shows, it’s a structured approach that balances flexibility with discipline. From eliciting and modeling requirements to verifying, validating, and managing them throughout their life cycle, every step is designed to ensure that requirements remain clear, relevant, and aligned with business objectives.</p><p>In practice, the most effective business analysts don’t just follow the guide — they adapt techniques to the project context, choose the right viewpoints for different stakeholders, and maintain a living architecture that connects strategy, needs, and solution design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9799cf46ef7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>