What It's Really Like to Be a Business Analyst on a Real Client Project
What It's Really Like to Be a Business Analyst on a Real Client Project
When I joined my IT Project Management course, I expected a typical academic group project. What I didn't expect was that it would turn into a real client project with actual production requirements, real stakeholders, and real deadlines.
I was assigned as the Business Analyst (BA-001) for our team's Digital Sign Application — a document digital signing platform built for a real client. Here's what that journey actually looked like.
What Does a BA Actually Do?
A lot of people think a Business Analyst just "writes documents." But in practice, it's much more than that. As a BA, I was responsible for:
- Gathering requirements from the stakeholder through interviews and discussions
- Writing the BRD (Business Requirements Document) — a formal document that defines what the system must do
- Designing the ERD (Entity Relationship Diagram) — working closely with developers to ensure the database structure matched the business logic
- Validating functional requirements — making sure every feature built by the developers actually solved the right problem
The Hardest Part
The hardest part wasn't writing the documents — it was making sure everyone was on the same page. Developers think in terms of code and logic. Stakeholders think in terms of outcomes and business value. A BA sits right in the middle, translating between both worlds.
There were moments where a requirement I wrote was interpreted differently by the developer. That taught me the importance of being precise, specific, and always open to iteration.
What I Learned
- Requirements are never final on the first draft embrace the iteration
- Communication is a technical skill, not just a soft one
- Documentation isn't busywork it's the foundation that keeps a project from falling apart
- Understanding the technical side (ERD, API, database) makes you a significantly better BA
Final Thoughts
Being a BA on a real client project as a student was one of the most challenging and rewarding experiences I've had. It pushed me to think beyond code, beyond features, and toward actual business impact.
If you're an IT student wondering whether to try the BA role do it. You'll come out with a completely different perspective on how software is actually built.

