Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering requirements for enhancement project when no previous documentation exists
Previous Previous
 
Next Next
New Post 5/23/2018 2:29 PM
User is offline MarinaS
1 posts
No Ranking


Gathering requirements for enhancement project when no previous documentation exists 

I was asked to document requirements for an enhancement project (new job) and now I realize there is no documentation for the existing part. Also, It seems that the knowledge level is very different across the involved stakeholders and there is no real common ground to rely on. Obviously, it's ideal to go back and document the entire process from scratch, but there is a real life here and the timelines I have do not allow making this S-M size project a XXL one (by trying to map it all). I'm looking for a real-life best practice advice and ideas on how to approach this best.
TIA!

 
New Post 6/3/2018 7:11 AM
User is offline Kimbo
438 posts
5th Level Poster


Re: Gathering requirements for enhancement project when no previous documentation exists 

Hi Marina,

You need to do at least some As-Is work, otherwise how will you know whether your requirements are enhancements or not? You need a baseline.

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering requirements for enhancement project when no previous documentation exists

Community Blog - Latest Posts

Ekaterina Barabash
Ekaterina Barabash
I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important.  And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...
1 Responses
Dan Tasker
Dan Tasker
I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...
2 Responses
Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses




Latest Articles

Adding Value as an Agile Business Analyst
Dec 09, 2018
0 Comments
As more organizations move toward agility, development and project management teams still struggling to define a common language and standard regardin...
Featured Digital Library Resources 
Copyright 2006-2018 by Modern Analyst Media LLC