Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  First Project... What's Next
Previous Previous
 
Next Next
New Post 1/24/2018 6:53 AM
User is offline Wavies
1 posts
No Ranking


First Project... What's Next 

Hi,

Recently I've taken on more responsibility within the Business Analysis with managing requirements realm as a way to help transition into a more agile environment. This is a little difficult as I zero formal training in BA (I've been in QA for about 6 years now).

 

My Sr. BA has provided me with Change Requests, Requirements, Derived Requirements, and the workflow for how they initially see it working but I'm still unsure of what to do next. I have visited: http://www.bridging-the-gap.com/business-analysis-process/ with hopes of shedding a little light on what's next but I'm still stuck.

I'm compiling a list of questions to ask my Sr. to better help me understand the objectives/scope/etc.

But what's next?

What do I use to formulate the business plan?

 

 
New Post 1/31/2018 9:21 AM
User is offline Nik J
1 posts
No Ranking


Re: First Project... What's Next 

Hi there,

So as I understand it, it seems like is the organization is shifting from a Waterfall to Agile methodology and your role is being transitioned to be a BA, reporting to a Sr. BA.  I have had to transition a few teams into Agile environments and it isn't always the simplest process, especially since people are generally used to doing things a certain way.  

Here's what you'll need to think about: 

1) Look up agile methodology online in case you need more info on what it's all about: https://en.wikipedia.org/wiki/Agile_software_development

2) Figure out what web tools you'll be using for the Agile environment:  JIRA (epics/stories) / Confluence (document repository) combo is very strong,popular platform. or something else?

3) You'll need to plan out and configure the workflow for epic, story, and bug tickets in a tool like JIRA.  This will involve understanding how your organization's SDLC process flows, and converting this into transitions (shifting from one status to another) and statuses.   Here is a reference:  https://confluence.atlassian.com/adminjiraserver071/working-with-workflows-802592661.html 

A common workflow I have used is:  Open > In Analysis > Ready for Dev > In Development > Ready for Code Review > In Code Review > Ready for QA > In QA > REady for Staging > In Staging > Ready for Merge > In Production/Complete

 

4) After all of this is done, you'll need to convert existing /new requirements into features that will become user stories in your Agile tool.  Typically a project will be an 'epic' and your feature would be a 'story' with associated use cases.  



 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  First Project... What's Next

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC