Online Webinar  – Recorded  August 9th, 2018
Activity Type: Education – Online or Digital Media 1 PDU – Free
Provider:  The Corporate Education Group ( REP 1011 )

Requirements elicitation is the process of seeking, uncovering, acquiring, and elaborating requirements for business systems. It is generally understood that requirements are elicited rather than just captured or collected.

There are discovery, emergence, and development elements to the elicitation process. Requirements elicitation consists of a variety of techniques, approaches, and tools.

This webinar shares 10 steps to effective requirements elicitation, guiding business analysts to deliver successful results.

Requirements elicitation is all about learning and understanding the needs of users and project sponsors with the ultimate aim of communicating these needs to the system developers.

Learning objectives include:

• Understand the application domain
• Identify the sources of requirements and analyze the stakeholders
• Select the techniques, approaches, and tools to use
• Prepare to use the selected elicitation techniques
• Document your approach and create a “strawman” to generate the right conversation
• Send input material to participants in advance with clearly defined objectives for the specific elicitation events
• Elicit the requirements from stakeholders and other sources
• Assign a scribe for note taking and use a whiteboard or a smart screen to document the requirements
• Use a standardized requirements document template
• Continue to re-validate the requirements until they are clear and can be acted upon by those who read them – business stakeholders AND implementers

Presenter: Terrell Smith (LinkedIn profile), MPA, PMP, CBAP With over 25 years of experience in a wide range of project management and business analysis assignments, he brings concepts to life in a practical and easy to apply manner. Terrell has assisted clients in the development of project management methodologies, risk assessments, quality management, agile methods, problem solving, rescuing troubled projects, implementing business analysis best practices, and team building.

Click to register for:
10 Steps To Effective Requirements Elicitation

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.

Live Webinar – June 25th, 2019 10:00 am – 12:00 pm EDT
Activity Type: Education – Course or Training  2 Hour s 2 PDU free
Provider: IAG Consulting (REP 2858)

Note: There is an error on the registration page – In the past this session has ALWAYS been a 2 HOUR 2 PDU session – The page states 2 PDUs but 1 hour duration which is incorrect.Be prepared for a 2 hour session.

Requirements Planning adds incredible value to the requirements process.

More than simply creating another “work breakdown structure” document, this is an opportunity to address risks proactively and gain better stakeholder participation.

This session demonstrates how every component of a requirements plan adds value.

Learning Objectives:

1. Illustrate the pitfalls of traditional approaches to Requirements Planning
2. Deliver guidelines for making Requirements Planning a value-add activity
3. Know what material must be present in a high quality requirements planning document

Click to register for:
5 Things You Must Know About Requirements Planning

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.

Live Webinar June 13th, 2019 1:00 pm – 2:00 pm EDT
Activity Type: Education – Course or Training  1 Hour  1 PDU free
Provider:  Modern Analyst

Many people ask how to measure whether or not they have good requirements, but most of them have the question wrong.

Researchers propose methods to measure quality of requirements, but the end game isn’t about requirements, or even the project deadline.

The real target is the value a project actually delivers to an organization.

Things like increasing revenue by a measurable amount or decreasing operational costs really are the bottom line, and ultimately the measure of success.

Fortunately, people typically do what their performance is measured against, so rallying an entire organization to measure true value increases the potential for that value to be delivered.

To really have a successful project, requirements engineering practices need to start with understanding the desired value of the project.

Then align requirements efforts to elicit and specify only the requirements that will deliver that value.

Then they work with development and test organizations to make sure the whole team maintains a razor sharp focus on delivering the desired value.

In this talk, Joy Beatty will share research findings that show what executives really care about (and it isn’t reducing the number of missed requirements).

Joy will detail experiences measuring value on actual projects and outline the steps you can use to create this kind of change in your organization.

Presenter: Joy Beatty, (LinkedIn profile) Vice President, Research & Development Seilevel, Joy Beatty has 15 years of experience in helping change the way customers create requirements with new requirements methodologies and training courses. She is a contributor to the core team for the new release of the IIBA BABOK^® Guide. She is a co-author of Visual Models for Software Requirements (Best Practices (Microsoft) and Software Requirements, 3rd Edition with Karl Wiegers

Click to register for:
Our Requirements Are Good,
So Why Aren’t We Delivering Value?

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.

Live Webinar – June 12th 2019 10:00 am – 12:00 pm EDT
Activity Type: Education – Course or Training  2 Hour s 2 PDUs free
Provider: IAG Consulting (REP 2858)

This two-hour webinar for project managers and business analysts gets right to the point and covers the essential steps for prioritizing business requirements.

This process is based on industry best practices ranging from QFD, MoSCoW and others —  and employing IAG’s experience and proven techniques for practical requirements prioritization.

This webinar will:

1. Explain why prioritization is important, when it is needed (and when it isn’t,) when it should be done, what different strategies could be used and what techniques work best.
2. Give participants a practical process that is adaptable to various types of projects (from large to small) and a variety of environments from agile to waterfall.
3. Provide Project Managers and Business Analysts with a clear understanding of what they need to know, and what they need to do, to easily and effectively prioritize the product requirements for their next project.

Key Content Covered in this Webinar:

Click to register for:
Requirements Prioritization Best Practices

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.

Live Webinar May 23rd, 2019 1:00 pm – 2:00 pm EDT
Activity Type: Education – Course or Training  1 Hour  1 PDU free
Provider:  Modern Analyst

In the world of software development, requirements engineering has been recognized as an important discipline for the past couple of decades.

Without proper requirements software development was bound to fail. But is this still true in the current Age of Agility?

• Requirements engineering was a natural fit in the waterfall approach.
• It was an upfront activity in the first phase of the project, the analysis phase.
  • In this stage the overall business requirements were:
    • Elicited,
    • Documented and
    • Validated,
      • And served as a contract for the remainder of the project.
• During functional design these business requirements
  • Were supplemented by user requirements and
  • Technical design added the system requirements.

Modern software development often follows agile approaches like Scrum and XP.

The role of requirements engineering is less obvious in these instances. Given that there are no distinct phases, requirements engineering continues throughout the process and may be part of every iteration.

Agile approaches are not very keen on upfront activities (‘Responding to change over Following a plan’) nor documentation (‘Working software over Comprehensive documentation’).

As a consequence, developers tend to neglect requirements engineering in agile projects. They seem to believe that requirements engineering is some old-school thing that doesn’t fit into agility.

Requirements are deemed to be the exclusive responsibility of the Product Owner which the rest of the team takes for granted. They often find out too late that this is a mistake.

Requirements engineering is an essential part of any development endeavor, irrespective of its methodology.

In every approach it should not be confined to an upfront analysis phase, but get attention throughout the lifecycle. In this webinar Hans van Loenhoud will address four common misunderstandings about requirements engineering and agility:

• Upfront is Evil
• User Stories are Enough
• Documentation is Waste
• Only Working Software Counts

Hans will also will talk about the points of engagement where professional requirements engineering fits into an agile iteration and about some techniques that can add value there.

Professional requirements engineering fits perfectly into agile principle #9 ‘Continuous attention to technical excellence and good design enhances agility’. This is a principle we have learned and practiced for a long time.

 It is not Requirements Engineering or Agile,
But Requirements Engineering at Agile!

Presenter:  Hans van Loenhoud MSc (LinkedIn profile) Taraxacum; is a consultant and teacher in the Netherlands. He has been working in software development for more than 35 years, starting as a Cobol programmer and later on specialized in test and quality management. In this role, he has been teaching various ISTQB test courses and has been chair of TestNet, the Dutch association of professional software testers. In recent years, he joined IREB to build a bridge between software testing and requirements engineering.

Click to register for:
The BA’s Friend Or Foe?
How To Fit Requirements Engineering Into Agility

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.

Live Webinar – May 22nd, 2019 10:00 am – 12:00 pm EDT
Activity Type: Education – Course or Training  2 Hour s 2 PDUs free
Provider: IAG Consulting (REP 2858)

This webinar gives an overview of key business intelligence and data warehouse concepts for Project Managers and Business Analysts.

The definition of the business requirements for analytical processing / decision support systems require different techniques than the process and data modeling used for transactional processing systems.

For a BI project, Business Analysts and Project Managers need to identify the business questions, facts, measures, and dimensions needed for the data warehouse.

IAG will provide a simple, easy-to-understand and easy-to-apply process that analyzes and defines the business objectives, usage scenarios, questions and queries that will yield the a conceptual multi-dimension model and form the basis of the business requirements for the data warehouse and business intelligence system requirements of your projects.

Learning Objectives:

1. How to conduct data warehouse business analysis
2. How to elicit requirements for the business intelligence aspects of projects
3. How to define requirements for on-line analytical processing and decision support systems

Click to register for:
Requirements Definition Best Practices
For Business Intelligence Projects

NOTE: For PMI® Audit Purposes – Print Out This Post!  Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.