Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Documentation in an Agile Way: Whats the best aproach?
Previous Previous
 
Next Next
New Post 9/6/2016 5:59 PM
User is offline Jayman21
28 posts
9th Level Poster


Documentation in an Agile Way: Whats the best aproach? 

Hello All,

What documentations would you consider important to produce / develop as a business analyst from end to end if running an Agile project for example development and implementation of a problem management system into an organisation?

Thanks

Jay

 
New Post 9/7/2016 10:05 PM
User is offline *FJC
12 posts
10th Level Poster


Re: Documentation in an Agile Way: Whats the best aproach? 

Hi,

    When it is agile, following documents are must.

1. Business Requirement Document (What is agreed on client and company is assured)

2. Kick off MOM (What is to be start with is verified)

3. Detailed Project Plan (Take a sign on the plan that is approved so that deliveries of sprints are clear)

4. Functional Requirement Document (Defines the technical aspect of BRD and Use Cases), etc.

   According to me these are must to make the scope clear. 

Thanks,

*FJC  

 
New Post 12/18/2016 6:01 PM
User is offline Jayman21
28 posts
9th Level Poster


Re: Documentation in an Agile Way: Whats the best aproach? 

Thanks FJC. Most believe the development and maintenance of Business Requirement Documents, detailed project plan, functional requirement document is not Agile. And the reason is that these documents do not easily adapt to changing situation plus they take time to development plus maintain hence taking take from development and feedback cycle. I am keen to hear the thoughts of others.

Thanks

 

  

 
New Post 1/19/2017 9:32 PM
User is offline amitabhkishore
1 posts
No Ranking


Re: Documentation in an Agile Way: Whats the best aproach? 

As per my view, level of documentation needed in Agile is limited to the level of documentation requirement of the development team. If the team can understand functionality through one page document, no need to write a long and beautiful document just to make it formal. In Agile, we use stories (requirements) and flesh out stories with acceptance criteria. The acceptance criteria provides enough details (functional requirements, non-functional requirements, functionality flow, business rules, validations, and error messages etc.) to the dev team to consume and build the feature. If even after this, the dev team requires clarification on points, conversation plays important role to clear doubts and that is also quick and less time taking than clarifying through document. We may choose to create Business Requirement Document as it defines the scope, but other documents can be dispensed with for sake of stories and acceptance criteria. 

 
New Post 2/28/2017 2:27 AM
User is offline sutnarcha
7 posts
10th Level Poster


Re: Documentation in an Agile Way: Whats the best aproach? 

Hi;

It is best recommended Not to spend a lot of time in creating word / excel / power point documents in Agile Scrum projects. Any Agile project uses a tool like Jira to manage projects. BAs are recommended to use Jira for tractability of requirements. Jira can be used for defining requirements, documenting solutions and approaches considered to meet requirements, groom user stories, identify development tasks, track progress, track bugs, issues, impediments, and overall delivery.

So, since the rest of Development team uses Jira, it is best recommended to use Jira for BA documentation as well. We do this in our projects, and it works very well from an overall requirement tractability perspective.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Documentation in an Agile Way: Whats the best aproach?

Community Blog - Latest Posts

Peter
Peter
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses
Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
2 Responses




Latest Articles

The Goal Is to Solve the Problem
Oct 15, 2017
0 Comments
A requirement is “a condition or capability needed by a user to solve a problem or to achieve an objective” (AKA a goal). Thinking in term...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC