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 2: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 6: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

Jason White
Jason White
With time, we have evolved from oiled lamps to ever-present electricity, printing every page manually to now producing thousands of copies a day and so on. But what is the one thing these distinct things have in common? Yes, technology.One such branch of technology that has crossed leaps and bounds and turned into a  working technology fr...
1 Responses
Digital Business Analysis
Digital Business Analysis
Nowadays, companies like Audi and HSBC, use IT systems in everything they do. Does that make them to be IT companies rather than banks? Most would probably agree that HSBC is a bank, just as Audi is a car manufacturer. But what about digital banks such as Chime or companies offering digital products? In digital companies, most of the employees work...
1 Responses
Digvijaybook
Digvijaybook
IT companies are rapidly looking or adapting modern methodologies, so the business analyst role is increasing day by day. Offline is shifting to online, and this is why today, companies can easily garner important data in any aspect. But, data itself has no meaning hence, organizations look for a business analyst who can analyze the data and draw a...
3 Responses






Latest Articles

An Introduction on Artificial Intelligence and Machine Learning
Feb 23, 2020
0 Comments
After some research, I was taken back with so many machine learning applications already in use: weather forecasting, medical diagnoses, law enforceme...
Copyright 2006-2020 by Modern Analyst Media LLC