Thank you for this work through. I presumed that the Agile user story/ acceptance criteria syntaxes could be used in a Waterfall environment as well, is it ok to do it this way?
Generally in the waterfall we write requirements from system capability standpoint and not the user centric approach used in agile. With that said, companies define the approach in which requirements need to be documents so follow the approach your company had adopted
@InDemandBAandScrumMaster thank you 😊. Just so I understand clearly, in Waterfall, requirements are documented as per system functional requirements, no? Can you kindly give an example of how a requirement is written in Waterfall pls? Thank you.
@@lerrylee8711 yes of course - let's say we want to ability to give someone the option to register with email. You would writing a functional requirement using this format: The system shall provide customers the ability to register on x using their personal email address (gmail, yahoo, hotmail).
@InDemandBAandScrumMaster gotcha! Thanks a lot..similar to, for example "The system must be able update customer status". Thanks so much. I appreciate you responding 😊
@@lerrylee8711 we need to add more detail than just update status e.g. status of what? What are the different statuses? How do the different statuses mean or represent in the system?
You are very good at this ...
I appreciate the effort you put into making your videos high-quality and entertaining.
Thank you for this work through.
I presumed that the Agile user story/ acceptance criteria syntaxes could be used in a Waterfall environment as well, is it ok to do it this way?
Generally in the waterfall we write requirements from system capability standpoint and not the user centric approach used in agile. With that said, companies define the approach in which requirements need to be documents so follow the approach your company had adopted
@InDemandBAandScrumMaster thank you 😊. Just so I understand clearly, in Waterfall, requirements are documented as per system functional requirements, no? Can you kindly give an example of how a requirement is written in Waterfall pls? Thank you.
@@lerrylee8711 yes of course - let's say we want to ability to give someone the option to register with email. You would writing a functional requirement using this format: The system shall provide customers the ability to register on x using their personal email address (gmail, yahoo, hotmail).
@InDemandBAandScrumMaster gotcha! Thanks a lot..similar to, for example "The system must be able update customer status".
Thanks so much. I appreciate you responding 😊
@@lerrylee8711 we need to add more detail than just update status e.g. status of what? What are the different statuses? How do the different statuses mean or represent in the system?
Hi Sarabjit,
In the integration does BA need to do the Post ,get, etc function in postman as well ?
Replay