Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Agile Requirements Mystery
Previous Previous
 
Next Next
New Post 6/26/2023 12:37 PM
User is offline MadiMo
31 posts
9th Level Poster


Agile Requirements Mystery  

Dear Experts.

I'm new to the Agile approach, I only had one small project using agile. I started to look into materials but I got confused by one fact and I hope if someone can help.

It says the requirements approach during agie is that you only care for the what you need for each sprint and you define the requirements for that sprint, which is fine. But for the development phase, we all know that user stories are not enough, so for you to "Define Requirements" for that sprint you basically will have no time to break down the user story into detailed functional requirement because to do this you need to go back to your stakeholders to define what they need exactly from that requirement, for both functional or nonfunctional.. 

The question here how will you find time to do those requirements definitions sessions when you are actually heading into a sprint? especially when you don't need to do requirements catalouge before the development in Agile like what you do in Waterfall.

I appreciate your opinions.

 

Madi

 
New Post 7/9/2023 6:07 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: Agile Requirements Mystery  

Hi Madi,

Great question!  Agile teams or scrum teams generally have two special roles: Srum Master and Product Owner.

It is the responsibility of the product owner to represent the customer/stakeholders.  the PO will connect with the customer to understand the requirements and needs and, at the same time, supports the agile team to deliver value. When grooming stories and the next level of requirements detail is needed, the product owner provides those details based on their understanding of the customers and stakeholders by interacting with the customers and stakeholders.

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 7/16/2023 1:52 PM
User is offline Meta BA
19 posts
9th Level Poster


Re: Agile Requirements Mystery  

The user stories are the unit of work, but they exist in the context of systems and processes. If those processes and systems are relevant to the work, it is really up to the members of the team to request that level of definition. On the teams I manage, the definitely of ready (meaning the story is suitable to be worked on during a sprint), there are two points that must be followed.

  • All user stories must have defined Acceptance Criteria using Gherkin Syntax (GIVEN, WHEN, THEN). This helps satisfy the "Testable" portion of the user story
  • Any artifacts necessary for the full understanding of a user story (which can be decided by anybody on the team) must be included before it is considered ready. This means process flows, data models, prototypes, decision tables, etc.

If your team doesn't do these things now, they usually become easy to implement via quality team retrospectives. If the team identifies a problem and that problem comes from not doing any of the above (or other productive actions you've learned about), you simply recommend implementing them.

If you are concerned that you aren't delivering on your value as a business analyst then BA Roles & Responsibilities [Video] gives good clarity on what you should focus on, regardless of methodology or exact deliverables.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Agile Requirements Mystery

Community Blog - Latest Posts

Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...
I recently had the pleasure of chatting with Wolfgang Goebl, a visionary in the field of business architecture and enterprise design. His unique approach, which he refers to as "architectural thinking," and his work with the EDGY framework, offer valuable insights into the future of organizational structure and design. This tool covers th...
Our next speaker in our Blueprints for Success series is none other than Roger Burlton, a prominent leader in business architecture. As founder of Process Renewal Group, Roger has spent over three decades helping businesses worldwide translate strategy into execution. “Intention is everything.” – Roger Burlton Known for his ...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC