When technical teams gather requirements, it can be a mystifying experience for the managers and users involved. How can someone on the business side understand early in the process whether the requirements analyst is doing a good job? One purpose of this talk is to demystify the process and help answer this question.
A second goal is to describe some practical things that requirements analysts can do to make their work go faster and more smoothly.
The talk will cover:
- How to think about requirements (and why they are like maps),
- What to do before capturing requirements,
- What kinds of requirements you can capture
- What kinds of requirements you should capture
- Different methods for capturing requirements and when to use them,
- Do’s and Don’ts for leading and participating in facilitated requirements workshops,
- Capturing requirements for Agile projects, and
- Questions clients should ask of their requirements analyst.
Note to attendees: If you have a topic or question that you would like Dave to address in his talk, email him at d7greene(at)gmail(dot)com and he will do his best to fit it in.
David Greene is a consultant, speaker, technical writer and trainer with over 15 years of experience in business/systems analysis and policy analysis. He has led over 100 software requirements workshops in the US and abroad dealing with: sales force automation (in a wide array of industries); operations & admin (for an HMO, hospitals, a jet engine manufacturer, a waste treatment plant and many banks); and maintenance/logistics for the US military.
Dave has managed teams of business/systems analysts for an online grocery vendor and a systems integrator. He has also worked multi-year stints as an energy/environmental policy analyst in Washington DC and internal management consultant for a Fortune 500 computer vendor.
Lunch and Networking from 1130 until 1200.
Program from 1200-1300.