Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Documentation after release.
Previous Previous
 
Next Next
New Post 7/10/2013 1:21 AM
User is offline Carl Oellermann
6 posts
10th Level Poster


Documentation after release. 

Hi, I am still new to the Scrum process and have been taking responsibility to write stories with the product owner. Since the software was released, there were no further documentation done on the how the released software works. The user stories and QA test scripts have the detail. Since I have been asked to produce documentation so that any person(Developer or non-technical person) can have access to documentation on how the system works, I am in a bit of a struggle on what to produce.

At the moment I am thinking of:

- UML diagram to show the overall context. Each use case links to a user story.

- Since the software contains UI, a website map.

- List of user stories and their link to the actual detail(We are using JIRA / Greenhopper)

- List of business rules related to features and link to user stories.

- Data dictionary which includes field name sizes and rules.

 

Question here is whether the documentation is too heavyweight ?The idea is to create a baseline of the software and when changes are required, we will then review the 'As is' and then determine what needs to change i.e.. Start another list of user stories indicating the change. During / after sprints I will update the documents based on what has been agreed / implemented.

Any advise on how you document after delivery will be appreciated.

 

Thanks,

Carl Oellermann

Business Analyst

 
New Post 7/12/2013 5:31 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Documentation after release. 

When moving from As-Is to To-Be, the primary need is to understand how the parts of your system interrelate.  Unfortunately, none of the items you listed address such.  Also knowing field sizes and rules tells little about logically how your data entities interrelate.   Think interrelationships.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Documentation after release.

Community Blog - Latest Posts

Samuel02
Samuel02
With the advent of modern-day cloud infrastructure, many business-critical applications like databases, ERPs, Marketing applications have all moved to the cloud. With this, most of the business-critical data now reside in the cloud. Now that all the business data resides on the cloud, companies need a data warehouse that can seamlessly store the da...
2 Responses
BPM_online
BPM_online
Bpm'online, a global business software company leading in the space of low-code, process automation, and CRM, will be soon announcing their new company name. The new name will be launched in the sky via a breathtaking skydiving performance involving 160 bpm’online employees, including the CEO. The new name of bpm’online is to be fo...
0 Responses
Heta Raval
Heta Raval
In a current scenario, when you are eliciting software service-based requirements then, you may be able to derive requirements in certain varieties. In the beginning, they can be just functional or non-functional requirements. But when you come across many other requirements as time goes, you can conclude requirements into several categories and wi...
0 Responses




Latest Articles

What’s Missing from Agile?
Oct 20, 2019
0 Comments
John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information te...
Copyright 2006-2019 by Modern Analyst Media LLC