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 Disabled
New Post 9/6/2016 6:59 PM
User is offline Jayman21
24 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 11: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 7:01 PM
User is offline Jayman21
24 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 10: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. 

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

Community Blog - Latest Posts

Edward
Edward
A few weeks ago, one of my colleagues surprised me with a statement he made during our team meeting that the information technology age is coming to an end. I looked at him in complete disbelief. How can the advances that have brought so much convenience to our lives be said to be coming to an end.  I thought he must be mistaken, and just like...
0 Responses
Chileshe Mulenga CBAP PMP
Chileshe Mulenga CBAP PMP
EXECUTIVE SUMMARY The Business Analyst and Project Manager are team players on a project. As is common the Business Analyst and Project Manager sometimes have conflicting approaches during a project. Having frequently taken up dual roles of a project manager and Business analyst during the course of my career, I have gained some insight on the d...
0 Responses
Paul Crosby
Paul Crosby
There are hundreds of traits that make up a good manager, but here are the top 9 skills we recommend for a business analysis leader - or any leader in general. 1. See Design as a Differentiator Anyone can design but not everyone designs well.  Who cares?  Frustrated users care.  Seeing design as important sets you apart from all ot...
2 Responses




Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC