Creating Requirements During times of constant change
As business analysts, we are known for being experts at identifying and managing business requirements. But, how should our most notable skills be adapted as the world around us is going through constant change? The remote BA cannot depend upon “hallway” networking and face-to-face interpersonal skills. A completely remote or hybrid environment can block the flow of communication with our stakeholders. Furthermore, as the financial markets fluctuate, business priorities are encountering unexpected shifts. There is a need for the BA to have a sense of personal agility, whether their workplace culture is agile or not. And although always important, requirements traceability is now more important than ever. Amid business disruption, the BA needs to track requirements changes using the best practices and tools at their disposal. So, how can a BA, whether remote or not, continue to deliver the value expected in requirements creation and maintenance amid this constant change? Join us and learn the answers.
- How to overcome remote communication blockers
- How to manage stakeholders in a remote environment
- How to incorporate personal agility into requirements elicitation and management
- How to use best practices and tools to maintain requirements traceability
Pamela Paterson, MS, CBAP, is a senior business analyst with over 20 years of experience as a consultant on enterprise IT projects. As a former college instructor, Pamela helps her clients make the complex into the simple, whether that is with requirements elicitation, project management, documentation management, or stakeholder communications. Pamela has written several books, including two international best-sellers. Her most recent book is Creating Requirements for Software Projects: A Business Analyst’s Guide to Requirements Management (2020), which became a best-seller on Amazon. She can be reached at pamelapaterson.com.