One of the major issues plaguing information technology projects is that the solution that gets built does not actually solve the business problem or opportunity. This is often because the software requirements are too high […]
Software Requirements: Get Business and Technology on the Same Page
System migration projects are one of the most common and most complex project types a business analyst will encounter. Whether your organization is consolidating tools, upgrading to a more robust platform, or finally moving off
A Business Analyst’s Approach to a System Migration Project
To be successful as a business analyst, you need a toolbox and a framework. 🎯 A TOOLBOX of techniques that you can pick and choose from, based on the needs of your project and team.
The Business Analyst Blueprint® Framework
As a business analyst, you need to have the ability to showcase how data seamlessly flows between information systems, ensuring smooth operations, and avoiding the headaches of data inconsistencies and mapping issues. With data mapping,
Imagine using a simple wireframe to create a visual representation of a screen in just a matter of minutes. No, you don’t have to be a UX designer to even aspire to be one. In
Looking to master the art of clarifying project scope in a flash? Say hello to the System Context Diagram, your secret solution to project scope! In today’s world, projects are only becoming more and more
How to Create a System Context Diagram to Model Data Flows
One of the most frustrating challenges on a project is when the developers build a solution that everyone thought the business signed off on only to have significant changes surface during testing or even after
How to Get Meaningful Sign-Off on Requirements
Strong business analysts know use a variety of techniques and craft specifications for specific project and stakeholder needs. Find the options you have for packaging requirements.
5 Types of Requirements Documents Business Analysts Create
Did you know that using visual models can improve communication, reduce misunderstandings, and facilitate collaboration in business analysis projects? If you’re not using some type of diagramming tool in your business analysis job, you may
5 Effective Diagramming Tools You Can Afford
Today we’re going to answer a question that comes up quite often, and that’s what technical skills a business analyst needs to be well-positioned in the job market and to be able to have detailed
These Are the Top Technical Skills that Business Analysts Really Need to Know
As a business analyst, it’s your role to analyze the To Be Business Process and help your stakeholders define how work will flow once the new solution is in place. In this short video, you’ll
How to Analyze a “To Be” Business Process
As a business analyst, it’s your job to analyze the As Is Business Process in your organization to help everyone get on the same page. If customers are getting frustrated with your organization’s level of
How to Analyze an “As Is” Business Process
User stories are a way of capturing requirements that are commonly used on agile software development teams. The cornerstone of a user story is a single statement in the following syntax: “As a [user], I
A process map is a visual model that shows how a collection of activities are sequenced together to accomplish work in an organization. One of the great things about process mapping is that they are
With the vast majority of projects being delivered using pre-built solutions, it is important to understand how to specify requirements for COTS (commercial-off-the-shelf) software and SaaS (software-as-a-service) projects. In this video, I am going to
What Requirements to Specify for COTS and SaaS Projects
A requirements review or walk-through is a meeting where you gather all of your stakeholders together and walk-through the requirements documentation, page-by-page, line-by-line, to ensure that the document represents everyone’s complete understanding of what is
How to Conduct a Requirements Review
An Entity Relationship Diagram (ERD) is a data model describing how entities (or concepts or things) relate to one another. When created by business analysts or business users, ERDs can be used to understand the
How to Create an Entity Relationship Diagram (ERD)
A use case is a powerful tool to both analyze and communication the software requirements. If you have a business background, a use case will help you define what the software needs to do, even
How to Write a Use Case: Template + Tutorial
When you are trying to figure out what problem to actually solve before you dive deep into the software requirements, you’ll want to analyze the business process. And to do that, you create both a
How to Analyze a Business Process – with a Process Template
Today we’re going to go through 22 different models BAs use in their work. You may not be aware of all 22 of them, so even if you’re familiar with a few, keep your eyes
22 Visual Models Used by Business Analysts
Do you create a traditional Business Requirements Document to capture your business and/or functional requirements? Adding a few diagrams to your BRD can make it more impactful and easier to understand. In this video, I
3 Diagrams to Add to Your Business Requirements Document
If you are on an agile team, do you write user stories, use cases, or both? My take is that until you know how to think in use cases, you need to write them to
If you find yourself in a business analyst role on an IT project, it’s likely that at some point you’ll need to create a functional specification – and these can take many different forms depending
What Goes Into a Functional Specification?
Clarity is one of the most fundamental attributes of writing good requirements. Clear requirements are less likely to be misunderstood by business stakeholders and technical implementers. Clear requirements require fewer review cycles to confirm and
3 Ways to Write Clearer Requirements
If you’re writing software or functional requirements and you are not leveraging use case thinking skills then you are missing requirements. And missed requirements cause unnecessary rework on software development projects. While use cases aren’t
3 Situations that are Absolutely Perfect for Use Cases!
As more organizations are working on cloud implementation projects, or leveraging software available in a SaaS (Software as a Service) environment, like Salesforce.com or ServiceNow, many business analysts feel that it isn’t necessary to capture
Cloud Implementations: 3 Essential Types of Requirements
The business analyst’s toolbox is chock full of dozens of business analysis techniques. Here is a list of 65 business analysis techniques that are useful to know about. Not that you would use every technique
65 Business Analysis Techniques
Do you find your developers have one follow-up question after another about how the system is really supposed to work, even though you documented the functionality in a use case? Worse yet, did your development team
7 Mistakes Even the Best Make When Writing Use Cases
When an organization is planning to move data from one system to another, planning the data migration is an important aspect of the project to ensure that the right data ends up in the right
How to Approach a Data Migration Project
If you come from a technical background, you might be wondering if you can skip data modeling and go right to designing and implementing the database. While you could theoretically bypass any of the data
3 Reasons to Data Model (Even If You Can Design Databases)
In today’s information-rich world, we are seeing more and more data-related analysis skills in business analysis jobs. We’ve been asked several times whether business intelligence and business analysis roles are really different roles, and how
The Difference Between Data Analysis and Data Modeling
As a business analyst, it would be rare for you to complete a data dictionary on its own. Rather, it’s likely that you’ll be analyzing data requirements in combination with other business analysis techniques. In this
How to Blend a Data Dictionary with Use Cases, Wireframes, and Workflow Diagrams
Here are 10 articles to help you get started with data modeling. These are perfect if you want to brush up on data modeling or get fresh ideas to improve your business analyst work.
Getting Started with Data Modeling (10-Part Series)
Are you ready to get started with data modeling, but wondering what software tools you’ll need? Have you seen some of the more complicated-looking models and wonder how you can create these with your business
What Software Tools Business Analysts Use for Data Modeling
You might be wondering if you need both a data dictionary and a data mapping, or you might want to make these two deliverables part of one simultaneous analysis activity. Data mapping is a special kind
When it Works to Create a Data Map and a Data Dictionary at the Same Time
Part of the value the business analyst provides is selecting techniques to ensure the requirements for a project are fully analyzed and understood. Data modeling can be a significant part of the project requirements to rightfully non-existent, even
How Data Modeling Fits Into the Business Analysis Process
Although data modeling techniques can look technical, you don’t need to know database programming to complete useful versions of the models from a business-facing perspective. Instead, business analysts create data models that describe the what (of
How to Data Model Without Getting Too Technical (or the what and the how)
Business analysts solve tricky, icky, sticky project challenges using data modeling techniques. There are 4 data modeling techniques you should get to know as a business analyst, so they can become part of your BA
4 Data Modeling Techniques that Solve Tricky Project Challenges
A Glossary is a deliverable that documents terms that are unique to the business or technical domain. A glossary is used to ensure that all stakeholders (business and technical) understand what is meant by the terminology,
The Glossary: A Gateway to Clear Requirements and Communication
A Data Dictionary, also called a Data Definition Matrix, provides detailed information about the business data, such as standard definitions of data elements, their meanings, and allowable values. While a conceptual or logical Entity Relationship
Author: Adriana Beal Participants who complete Crafting Better Requirements may have very different educational and professional backgrounds, but they all have one thing in common: they leave the course with a unique set of strategies
How to Use Feedback to Become an Expert in Requirements Documentation
Business Process Modeling Notation (BPMN) is a standardized notation for creating visual models of business or organizational processes. Those new to BPMN understandably find it overwhelming. There are flow objects, connecting objects, swim lanes, and artifacts.
3 (and only 3) Reasons to Use BPMN (Business Process Modeling Notation)
With all the craze about use cases lately, you’d think that no collection of requirements documentation would be complete without at least one, and perhaps several, use cases. The reality is that while use cases
3 Signs You Shouldn’t Be Writing a Use Case
Many business analysts mistakenly believe that adding a visual model to a specification – or preparing one specifically for a requirements meeting – means significant extra work. But in reality, using the right visual modeling
How to Make the Requirements Process Faster With Visual Models
Picture me: young, fresh, and disciplined…leading a very boring requirements meeting where we’re poring over a very laborious requirements document. This was way back when I was too new, too green, to know better. I
How to Put Some Spunk Into Your Requirements
Would you be interested in learning more about how to visually represent your requirements, even if you have little to no technology skills? Have you been seeing the terms “wireframe”, “mock-up”, and “prototype” in BA
What’s the Difference Between a Wireframe, Mock-Up, and Prototype?
I have to admit that I have a rather eclectic music collection, with tracks covering almost every conceivable genre. Every time I hit the “Shuffle” button on my MP3 player, there’s a tense moment of
Make Your Requirements Atomic!
While I find that wireframes help me elicit the right requirements and shorten requirements review cycles by giving my stakeholders a visual point of reference, many business analysts resist creating wireframes because they take can
3 Shortcuts to Create Wireframes in Record Time
Many new business analysts are confident in their communication and problem-solving skills but feel held back because they’ve only ever created informal documentation to serve a specific audience or project need. Are you confident in
Like writers complain of “writers block,” modelers often find themselves in “analysis paralysis.” When modeling a business process, analysis paralysis occurs when we get stuck on a model and are not able to finish it,
5 Ways to End Analysis Paralysis on Your Next Business Process Model
Did you know that requirements can be perfectly well documented and verified, but completely useless? This is why business analysts not only verify requirements, but also validation them. In the BABOK Guide, the purpose of Requirements
How to Validate Requirements (BABOK 6.6)
Requirements verification ensures the intrinsic quality of the requirements. Although it would be a significant waste of time outside academic circles, I could verify requirements for a solution that had zero business value and that
How Do Business Analysts Verify Requirements? (BABOK 6.5)
Do you think that you as the business analyst should be involved in figuring out how the solution is put together, even though you are not responsible for designing it or implementing it? Do you
Oh Where, Oh Where Does This Requirement Belong? (BABOK 7.2)
There is a distinction between the project requirements and the requirements package.Requirements can be organized, sliced and diced, torn apart, allocated, put back together, assigned attributes, etc. Packages are finely wrapped presentations of requirements in
Good Things Come in Nice Packages (BABOK 4.4)
As BAs we very easily get wrapped up in our requirements. That is the bulk of our work – business requirements, stakeholder requirements, solution requirements, etc. Everywhere we look, requirements, requirements, requirements! However, in the
It’s Not “All Requirements” – Assumptions and Constraints Matter Too! (BABOK 6.4)
We have two readers ask similar questions of our Help A BA! staff concerning extracting business rules from legacy systems; so let’s help them both out. Reader 1: As rules are mostly hardcoded and code
How Do I Extract Business Rules from Legacy Systems?
We ask the questions that people having been avoiding for years while they were trying to look smart. I read an article today from our respected colleague, Yaaqub Mohamed about the importance of data analysis
Author: Adriana Beal If you are a BA working on the IT space, you may be responsible for creating multiple deliverables, many of them intermediate documents such as meeting minutes and as-is/to be business models.
Why Writing a Software Requirements Specification is a Valuable Analyst Skill
Reader Question: The organization I work for is expanding its Business Intelligence capabilities, introducing a new Enterprise Data Warehouse for management reporting. This is based on the concept of OLAP Data Cubes – permitting greater
How Do I Approach Requirements for a Business Intelligence Project?
I am sure that any business analyst who has written user acceptance scripting can confirm that script writing is super detailed, critically important and mind numbingly boring. But is it important – yes it is.
6 Tips to Keep Writing UAT Scripts Fun
Reader question: “How do people go about collecting report requirements from clients and trying their best to reduce overheads whilst still fulfilling the data needs? I know there has been a big drive recently for
How Do You Collect Requirements for a Reporting System?
Some recent posts across the blatherverse have highlighted some considerations that we as good business analysts must employ when developing and delivering our documentation and deliverables. These got me to thinking about my own very
I’m Letting Go of the Big Thick Requirements Document. Are You?
Let me share one of my more humbling experiences as a business analyst. To be perfectly blunt, the developers did not like my requirements specifications. It was hard to realize that I had failed to
Akk! The Developers Won’t Use My Requirements Specs!
Can you really have a love affair with a document? Don’t tell my husband, but the answer is “yes”. For me, the love of my business analysis professional life has been use cases. In what
Use Cases: A Personal History (and a bit of a love affair)
Do you demand that your documentation serve double duty as a technical specification and a system document? While in the past I’ve done exactly that, my recent forays into more agile practices forced me to
Technical Specifications and System Documentation Can Take Different Forms
While you may have a formalized processes and sets of documentation requirements for your software projects (this can be helpful or hurtful), you might be starting with no process or set way of specifying requirements.
Requirements Templates: What To Do When You Must Start From Scratch
We’ve all heard that a “picture is worth a thousand words”. It’s absolutely true when it comes to building good software requirements. In the case of building a software application, even the most rudimentary prototypes
Using Wireframes or Prototypes to Elicit, Analyze, and Validate Software Requirements
A long, long time ago while working on a web-based product, a colleague of mine came up with this idea of writing a user interface or screen specification. The purpose of this requirements specification is
How to Create a User Interface Specification
Agile teams typically differentiate between “epics” and “user stories.” As an agile business analyst, epics is a key technique to be aware of, as they are one way to look at the bigger picture before
Epics in Agile – A Template to Scope a New Feature
When you reach that point of the project where your head simply hurts from how hard you are thinking, you’ve spent hours in meetings rehashing the same concepts, and yet you and your team members
How to Create a Business Domain Model
So, you’ve met with your stakeholders and elicited information about their business processes, business needs, or how the system works today. How do you actually turn this into requirements documentation? In what follows, I’ll share
How to Prepare a Requirements Document in 4 Steps
Based on my experience analyzing requirements in user stories, I’m convinced that a fundamental challenge for the agile business analyst or product owner is to maintain and communicate the “big picture” while also detailing out requirements in
How to Keep a Big Picture Perspective on an Agile Project
In today’s climate of content exchanges and web APIs, it’s often necessary for someone with both business and technical knowledge to participate in data modeling activities or building data specifications. Dumping data into your organization’s
Data Feed Requirements – A Template
The product backlog is really the core deliverable that maintains and evolves the requirements in an agile environment. Ownership by the agile business analyst (or a product owner with BA responsibilities) is critical. A product
How to Create a Product Backlog: An Agile Experience
I have asked this question in nearly every business analyst job interview I’ve conducted and rarely heard the answer I was looking for. The most common (and wrong) answer is “never”. Let’s just be clear
When are you “done” with requirements?
