This event is history, please check out the List of Upcoming Seminars, or send us an email
Check out our related in-house workshops:
Why do we organize this seminar ?
FREE BOOK with your seminar participation: |
|
The first session of this seminar was sold out in no time. There is a second chance to register for this seminar, because we repeat this seminar on October 4th, 2006.
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 seminar 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 seminar 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 seminar ?
During this seminar, you will learn how to:
Who should attend this seminar ?
This seminar 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.
|
Increases in organizational and technological complexity have raised awareness of the need for clear, understandable, unambiguous requirements. But how do we find these requirements and how do we communicate and manage them? This presentation addresses these questions by looking at:
The main intent of this presentation is to outline a typology/classification of requirements with different capturing techniques, and to illustrate this by a case study. The case study is taken from a major offshore development project with an Indian company, because 'requirements management' is even more critical in an offshoring context.
During this customer testimonial, Erwin Raeds will explain how requirements management is performed at Philips Brugge:
To illustrate how tools can support the requirements gathering and management process, we have selected a speaker from one of the leading tools for requirements management, who will give a non-commercial overview of how tools like this can help and support you:
Eric Callebaut is independent IT consultant and member of Inno.com.
For more than 15 years now, Eric has been helping organizations to improve their software project management and software development processes in order to build software faster, cheaper and better.
Eric contributed as process coach and trainer to various international corporations and leading-edge projects. Clients include: ING, Toyota Europe, De Post, IBM US, BP UK, Patni (India), Euroclear, IBS, British Steel.
His experience is focused on management and IT-consulting with special emphasis on IT organisation & processes, IT offshore development, requirements management- and project estimation methodologies.
Eric holds a master degree in economic science and computer science from the Catholic University of Leuven and has also studied International Management at the Boston University.
Questions about this ? Interested but you can't attend ? Send us an email !