Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  documenting requirements in agile project
Previous Previous
 
Next Next
New Post 8/4/2013 10:58 AM
User is offline sswapna
2 posts
No Ranking


documenting requirements in agile project 

hi

could anyone guide me in what kind of documentation is required for a agile project.

thanks in advance.

 
New Post 8/5/2013 5:01 PM
User is offline Chris Adams
323 posts
5th Level Poster






Re: documenting requirements in agile project 
Modified By Chris Adams  on 8/5/2013 8:01:51 PM)

Hi Swapna,

If you're not very familiar with Agile methods in general you should take a look at some of the interview questions and answers.  You can do a search for Agile and find quite a few.

Here is one that discusses SCRUM a very popular Agile approach.

Here is another that talks about User Stories which are commonly used to document requirements in an Agile environment.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
New Post 8/6/2013 5:05 AM
User is offline Perry McLeod
70 posts
8th Level Poster




Re: documenting requirements in agile project 

 I would also visit the agile alience's site and read the manifesto.  It is important to remember that agile is a cultural shift and a way of thinking. Yes it does have a process but that process is less important than the spirit of agile.

read this link and determine just how "agile" your environment intends to be.

http://www.agilealliance.org/the-alliance/the-agile-manifesto/

 
New Post 8/7/2013 11:32 AM
User is offline Kay Fudala
2 posts
No Ranking


Re: documenting requirements in agile project 

 sswapna wrote

hi

could anyone guide me in what kind of documentation is required for a agile project.

thanks in advance.

I agree with what Perry says and here is my quick reply: The two most important artifacts in Agile are User stories and the Sprint schedule (you may have a backlog and several other supporting artifacts that are required by the administrative process within your team).

If you are on a Agile team, you could be co-located with your business partners and IT team members. This usually means that you will have some sort of a display of user stories and the schedule. I find this type of dashboard to be very helpful. You can take a lead on setting one up if you team is not already using one. 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  documenting requirements in agile project

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