During this workshop, James Robertson will teach you to:
Determine the real needs of your client
Uncover the essence of the business
Learn diverse elicitation techniques to uncover the real requirements
Write agile stories that are more effective and accurate
Understand the role of the business analyst in agile projects
Write requirements that are complete, traceable, and testable
Use a story map for more controlled development
Understand the need for (and how to write) both functional and non-functional requirements
Precisely define the scope of the project
Discover all the stakeholders and keep them involved
Use prototypes and sketches to discover hidden needs
Get the requirements quickly, and incrementally
Use state of the art requirements techniques
Discover the right requirements and stories
About this intensive three-day workshop
This three-day workshop is entirely focused on requirements management. Requirements are the most crucial part of systems development, and yet the most misunderstood part of it. Requirements must be correct if the rest of the development effort is to succeed. This workshop presents a complete process for eliciting the real requirements, testing them for correctness, and recording them clearly, comprehensibly and unambiguously.
Software development today is more complex and demanding than ever; and there are fewer resources to meet those demands. Getting the software right - the first time - is the most effective way to succeed under these circumstances. Today's requirements process is incremental with quick cycle times. It uses prototypes and scenarios, and it ensures that your developers know precisely what you - and your customer - mean when you write a fit criterion: a concise test case for the requirement.
This workshop shows you how to precisely define the scope of the business problem, to discover and involve the appropriate stakeholders, to use techniques such as apprenticing and use case workshops to learn what the users really need, to write testable requirements, and to phase the requirements to allow incremental delivery of the product.
Is this workshop for me ?
Yes, if you want to be involved in delivering the right systems: the ones that get used. Your title is probably business analyst, systems analyst, product owner, project leader or manager, requirements engineer, consultant, product or program manager or similar. Team members on agile projects benefit from understanding how requirements are done in agile projects.
Users, software customers and business stakeholders have found that this course equips them to participate more effectively in the requirements process, and so ensure that the end solution matches what they really need.