Getting Into the Requirements Meeting
No matter what software development process your organization follows, it’s almost a sure thing that it has requirements meetings. They might even be called “requirements meetings.” Sometimes they’re called “design meetings.” If your organization practices a variation on Agile, they might be called “user story workshops.” Whatever these meetings are called, they’re where key stakeholders meet to establish a shared understanding about the features to be implemented.
If you are not already part of these meetings for the software you’re working on, you need to be. You need to hear the conversation firsthand, and your team needs the exploratory mindset that you can bring to the table. Spending a few minutes ...
Get Explore It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
