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 3:21 AM
User is offline V
1 posts
No Ranking


Requirements through User Journey - correct approach? 

Hi,

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 11:32 AM
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 12:17 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Requirements through User Journey - correct approach? 

Hi:

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?

Tony

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

Community Blog - Latest Posts

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...
Now, I know, I don’t know what kind of new intro BPO may require, but at least I can promise you upfront that I have something different to say about Business Process Outsourcing or simply BPO. What is it? This hasn't been a call center job or a sales job as we all think. It is a mammoth profile, and firms are grappling to ge...
Leveraging Blockchain Technology for Enhanced Data Security in Business Operations
In an age where data breaches and cyberattacks are becoming more frequent and sophisticated, businesses are searching for robust solutions to safeguard their data. Blockchain technology has emerged as a promising tool in this quest, offering a way to secure data with unparalleled reliability. Although initially known for powering cryptocurrencies l...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC