May 2018
Beginner to intermediate
240 pages
6h 6m
English
In early 2000, I worked as a business analyst. We were following the waterfall methodology, and I used to maintain huge 500-page requirements documents. Waterfall methodology assumes that software development happens in stages. The first phase is to understand business requirements. It is followed by designing and architecting the solution. Solution development starts only after the architecture is signed off testing begins only after development is complete, and so on.
Interactions with business stakeholders happened primarily at the requirements gathering phase. When building a large solution, that phase could run into months. There wasn't much interaction with businesses, or customers, after this phase. In my case, most ...