This event is history, please check out the List of Upcoming Seminars, or send us an email
Check out these related open workshops:
Check out our related in-house workshops:
Why do we organize this workshop ?
|FREE BOOK with your seminar participation:|
About this 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.
Why should you attend this workshop ?
During this workshop, you will learn how to:
Who should attend this workshop ?
This workshop is particularly useful for anyone who is involved in delivering the right systems - the ones that get used.
This includes, but is not restricted to business analysts, systems analysts, project leaders or managers, requirements engineers, consultants or similar. It will also be useful for users or software customers who want to ensure the requirements process delivers what they need.
This programme is spread over 3 days, from 10h00 till 18h00, with a dinner around 13h00:
This builds a foundation for the requirements project by establishing its Scope-Stakeholder-Goals. This gives you the precise scope of the business area to be studied; a testable goal for the project; and using stakeholder maps, you can identify all the sources of requirements. Additionally, the blastoff ensures the project is viable and worthwhile.
Trawling for Requirements
At the core of any requirements process is the ability to get people to tell you what they really need, rather than their perceived solution, or what they think you might be able to deliver. We show you how to use apprenticing, use case workshops, interviewing, brainstorming, mind maps and other techniques to discover exactly what the customers need—and want.
Functional requirements are those things the product must do. You discover them by understanding the work the user does, and determining what part of that work the automated product can best do. The resulting interaction between user and product is usually modeled with scenarios, and from these, you can readily derive the functional requirements.
Non-functional requirements are properties the product must have, such as the desired look and feel, usability, performance, cultural aspects and so on. This section discusses the types of non-functional requirements, and shows you how to use the template, and other methods, to find the all-important qualitative requirements for your product.
Managing Your Requirements
Requirements are the lynchpin of any development effort, and so have to be written correctly and managed effectively. This section demonstrates the use of a template to help you write requirements. It looks at requirements management issues like traceability, prioritization and conflicting requirements. We also look at tools to help manage requirements specifications.
James Robertson is a consultant, teacher, author and practitioner of innovation. Het is the co-author of the best-selling book "Mastering the Requirements Process, Second Edition" (Addison-Wesley 2006). This book provides guidance on finding requirements and writing them so that all the stakeholders can understand them. He also co-founded the Volere approach to requirements engineering. His most recent book is "Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior", written with fellow principals of The Atlantic Systems Guild, a London and New York-based think tank known for its research into new systems engineering techniques.
James Robertson has worked on almost every type of information system. His experience has led him to write numerous seminars and papers that are well respected as sources of new software development ideas.
As well as teaching his seminars, he now advises companies on how to adapt modern software development techniques to fit specific projects, and how to effectively transfer the new technologies to the software developers within the organisation. he has formed a solid partnership with his wife Suzanne to consult on numerous large-scale projects in Europe and the United States.
James and Suzanne Robertson are principals and co-founders of The Atlantic Systems Guild.
Questions about this ? Interested but you can't attend ? Send us an email !