Videos and Webinars 3100 Views 0 Comments 1 Likes Are you still "gathering requirements"? In this world of agile software development where requirements have been absorbed and marginalized by user stories, epics, product backlogs, and direct conversation between the business stakeholders and the solution team, "gathering requirements" seems to be a thing of the past. Especially since requirements themselves seem to be the source of all the bad things that happen in software development. It seems that all failures in software development can be laid at the feet of the requirements. The truth is that as business analysts, we shouldn't be "gathering requirements" in the first place. So what is it that we are supposed to be doing if not "gathering requirements"? This webinar answers that question in a way that is applicable to the agile software development approaches, the traditional software development lifecycles, and even when, as a business analyst, you aren't involved with developing software at all. In addition to answering the question the webinar will provide tips, techniques, and practices you can use to improve your solution definition expertise: How to relate the business needs to the solution team in an agile approach Assist management in business decision making Define requirements for any solution Follow a simple process that turns business needs and objectives into solution requirements ** Eligible for PDUs, CDUs. ** Featured Speakers Steve Blais, PMP, PMI-PBA Author, Consultant, Teacher and Coach , EssenceOfTheBA.com Featured Video Download Slides Download Video Related Content Requirements Glossary from A to Z How to Categorize Customer Requirements Agile vs FuSa (Functional Safety) Did you like this article? 1 Upvote agile requirements requirements elicitation 2020-09-27 Requirements.com All about Requirements 2020-09-27 Requirements.com Staff Webinar: Stop Gathering Requirements Comments / Discussions Please login or register to post comments.