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

Context:  Intro Change Request Definition Reasons for CRs Adaptive, predictive and mixed projects Flow of processing change requests Change Management Workflow Tools and Techniques 1. Intro  The World will never stop changing, as well as human needs and desires. The business environment evolves continually. An or...
For many people, a career in business systems analysis can be an ideal opportunity to use their skills in technology and business. Business systems analysts bring together the best of both worlds – technical know-how and business acumen – to help organizations become more efficient and effective. Here are some of the key benefits of pur...
There is no doubt in my mind that curiosity nurtures the mind when it comes to T shaped skills.  T shaped professional are specialist in something(the vertical line) and also have a wide range of skills and knowledge in a broad range of subjects(the horizontal line) and are are highly sought after in the workplace.  I’ve recently...

 






 

Copyright 2006-2023 by Modern Analyst Media LLC