Skip to main content
Welcome back, future business analysis superstars! In the last page, we got a bird’s-eye view of what business analysis is all about. Now, it’s time to zoom in and examine the key concepts that form the foundation of BA work. Think of these concepts as the LEGO blocks of business analysis – master these, and you’ll be building impressive BA structures in no time!

​
Stakeholders: The Cast of Characters in Your BA Drama

Imagine you’re directing a play. Your stakeholders are all the people involved in making that play a success – from the lead actors to the person who sweeps the stage after the show. In business analysis, stakeholders are individuals or groups who have an interest in, or are affected by, the project you’re working on.

​
Types of Stakeholders

  1. The Big Cheese: These are your executive stakeholders. They’re the ones with the power to greenlight projects and sign checks.
  2. The End Users: The folks who will actually use whatever solution you come up with. Ignore them at your peril!
  3. The Tech Wizards: Your IT team, developers, and other technical experts who will bring the solution to life.
  4. The Money Managers: Finance teams who keep an eye on the budget and ROI.
  5. The Regulation Rockstars: Legal and compliance teams who ensure everything stays above board.
Try This: Think about a project at your workplace (or your last big purchase if you’re not working). Who were all the stakeholders involved? You might be surprised at how many you can identify!

​
Stakeholder Management: Herding Cats with Diplomacy

Managing stakeholders is often like herding cats – if the cats all had different opinions and the power to derail your project. Here are some tips from BA veterans:
“Communication is key,” says Krzysztof from sunscrapers.com, an experienced IT Project Manager and Product Owner. “Each stakeholder may prefer different communication methods, such as email, video calls, or in-person meetings. A successful plan customizes both the medium and the frequency of communication based on stakeholder needs. This ensures timely updates and builds trust by keeping everyone informed at an appropriate level​”
  1. Identify: Figure out who your stakeholders are early in the project.
  2. Analyze: Understand their interests, influence, and potential impact on the project.
  3. Plan: Develop strategies to engage each stakeholder effectively.
  4. Engage: Keep stakeholders informed and involved throughout the project.
Remember: Not all stakeholders are created equal. Some will need more of your time and attention than others. Prioritize based on their influence and interest in the project.

​
Requirements: The North Star of Your Project

If stakeholders are the characters in your BA drama, requirements are the script. They define what needs to be done to achieve the project’s objectives.

​
Types of Requirements

  1. Business Requirements: The big picture stuff. What does the organization want to achieve?
  2. User Requirements: What do the end-users need to do their jobs effectively?
  3. Functional Requirements: The nitty-gritty of what the solution needs to do.
  4. Non-Functional Requirements: How the system should behave (e.g., performance, security).
Tech Talk: You might hear people talk about “user stories” in Agile projects. These are just a specific way of framing user requirements, typically in the format: “As a [type of user], I want [goal] so that [reason].”

​
The Art of Requirements Elicitation

Gathering requirements is part science, part art. You need to be part detective, part therapist, and part fortune-teller.
  1. Interviews: One-on-one or group discussions with stakeholders.
  2. Workshops: Collaborative sessions to brainstorm and refine requirements.
  3. Observation: Sometimes called “job shadowing” - watch how people actually work.
  4. Surveys: Useful for gathering data from a large number of stakeholders.
  5. Document Analysis: Review existing documentation to uncover requirements.
“My favorite technique is the ‘Five Whys’,” from the Toyota Production System. “When a stakeholder states a requirement, I ask ‘why’ five times. It helps dig down to the root of what they really need, not just what they think they want.”
Remember: Requirements aren’t set in stone. They often evolve as the project progresses and stakeholders gain a better understanding of what’s possible.

​
Scope Management: Drawing Lines in the Sand

Scope management is all about defining the boundaries of your project. It’s like drawing a line in the sand and saying, “We’ll do everything inside this line, but anything outside is for another day.”

​
The Scope Statement: Your Project’s Contract

The scope statement is a crucial document that outlines:
  • What’s included in the project
  • What’s explicitly excluded
  • Any assumptions or constraints
Try This: Next time you’re planning a vacation, try writing a scope statement. Include what you’ll do, what you won’t do, and any assumptions (like “assuming the weather is good”). It’s great practice for project scope management!

​
The Dreaded Scope Creep

Scope creep is what happens when your project starts to expand beyond its original boundaries. It’s like planning to build a doghouse and ending up with a three-story mansion. Tips to Manage Scope Creep:
  1. Clear Documentation: Make sure your scope statement is crystal clear.
  2. Change Control Process: Establish a formal process for approving changes to the scope.
  3. Educate Stakeholders: Help them understand the impact of scope changes on time and budget.
  4. Learn to Say No: Sometimes, the most important skill is knowing when to push back on new requests.
“I once had a project where the scope grew by 50% in the first month. We had to call a timeout, revisit the original objectives, and reset expectations with all stakeholders. It was tough, but it saved the project in the long run.”

​
Putting It All Together: The BA Toolbelt

Now that we’ve unpacked these key concepts, let’s look at how they all fit together:
  1. Stakeholders help you understand the context and objectives of your project.
  2. Requirements define what needs to be done to meet those objectives.
  3. Scope Management ensures you stay focused on what’s important and achievable.
Think of these concepts as tools in your BA toolbelt. Like any good craftsperson, you’ll need to practice using these tools to become proficient. But with time and experience, you’ll know exactly which tool to reach for in any given situation.

​
The Bottom Line

Understanding stakeholders, requirements, and scope management is crucial for any business analyst. These concepts form the foundation upon which all your BA work will be built. Master these, and you’ll be well on your way to BA stardom! In the next page, we’ll explore some of the key techniques and methodologies BAs use to put these concepts into practice. Get ready to add some serious skills to your growing BA repertoire!
Remember: Business analysis is as much an art as it is a science. While these concepts provide a solid framework, don’t be afraid to get creative in how you apply them. The best BAs are those who can adapt these principles to fit the unique needs of each project and organization.