Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Requirements through User Journey - correct approach?
Previous Previous
Next Next
New Post 10/16/2012 5:21 AM
User is offline V
1 posts
No Ranking

Requirements through User Journey - correct approach? 


Working as the main business/requirments analyst for our organisation, I have been in charge of collecting the requirements and sending them over to people who do the implementation.

These requirements revolve primarily around introducing changes to our website. These changes are documented as a user journey in form of screenshots (done by the design team) and text explaining how the expected behaviour would be. This is all generally derived from higher level requirements which are documented first and then broken down into smaller requirements and verified with business heads. This documentation is then sent over to the development team who come back with any queries and finally develop code for the website based on the document.

What is the opinion of the people on these forums regarding such an approach? I am not sure if these is a very widely used approach and was curious about what people think of this....appreciate your feedback and comments....Thanks

New Post 10/16/2012 1:32 PM
User is offline dldelancey
61 posts
8th Level Poster

Re: Requirements through User Journey - correct approach? 

Do the various members of the team (BA, dev, QA, tech writers, etc) have what they need to do their jobs?  Are you delivering working software that meets the real needs of the stakeholders and has business value?  In other words, does the approach work?

If the answers are yes, yes, and yes, then it doesn't really matter what anyone here thinks.

New Post 10/16/2012 2:17 PM
User is offline Tony Markos
493 posts
5th Level Poster

Re: Requirements through User Journey - correct approach? 


At the more detail level, using screen shots is fine.    But remember that the real challenge is not so much documenting stand alone requirements, but, documenting the essential interrelationships between requirements.    With this in mind, what do your higher level requirements look like?    Do they focus on interrelationships between stand alone behavioral requirements?


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements through User Journey - correct approach?

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...


Upcoming Live Webinars


Copyright 2006-2022 by Modern Analyst Media LLC