ComplianceOnline

Right-Sizing Requirements Elicitation: Balancing Lean, Sigma, and ''Agile'' Methods

Instructor: Gary Gack 
Product ID: 702108
  • Duration: 90 Min

Training CD

$499.00
One CD is for usage in one location only.
(For multiple locations contact Customer Care)
CD and Ref. material will be shipped within 15 business days

Customer Care

Fax: +1-650-963-2556

Email: customercare@complianceonline.com

Read Frequently Asked Questions

This Software Project Requirements Elicitation training will show how you can use Six Sigma and Lean/Agile methods to reduce missed and misunderstood client requirements for software projects.

Why Should You Attend:

According to software industry benchmarks nearly 20% of all software defects originate in requirements. Invariably these defects are more difficult and costly to fix as they impact the software design and construction – they have a ripple effect – even areas of the software not directly concerned with the flawed requirement must be changed.

Attend this webinar to learn how you can minimize missed and misunderstood requirements by using Software Six Sigma responses and Lean/Agile responses, and thereby determine the right requirements for software projects.

Areas Covered in the Seminar:

  • Requirements Challenge # 1: “That's not what we wanted” vs. “But we met the specs”.
    • Software Six Sigma responses: A family of tools, Disciplined use of language, ”Voice of the business”.
    • Lean/Agile responses: the “product owner”, short iterations, incremental delivery.
  • Requirements Challenge # 2: “Takes too long, costs too much”.
    • Lean/Agile responses: Tacit knowledge, co-located teams.
    • Project Management Body of Knowledge responses: Work breakdown structures, critical path planning, earned value.
  • Right-Sizing Requirements Elicitation.
  • References.

Who Will Benefit:

This webinar will provide value to anyone concerned with requirements determination for software projects. Those that would benefit most include:

  • Business Analysts
  • Requirement Engineers
  • Project managers
  • Quality assurance managers
  • Process improvement specialists
  • Software metrics specialists
  • Software process specialists

Instructor Profile:

Gary Gack, is the founder and President of Process-Fusion.net, a provider of Assessments, Strategy advice, Training, and Coaching relating to integration and deployment of software and IT best practices. Mr. Gack holds an MBA from the Wharton School, is a Lean Six Sigma Black Belt and an ASQ Certified Software Quality Engineer. He has more than 40 years of diverse experience, including more than 20 years focused on process improvement. He is the author of many articles and a book entitled Managing the Black Hole: The Executive's Guide to Software Project Risk.

Topic Background:

According to software industry benchmarks nearly 20% of all software defects originate in requirements. These defects include items that were missed or misunderstood. These sorts of defects are especially serious because requirements are the basis for all subsequent project effort. Missed requirements are typically not recognized until very late – often during acceptance testing and sometimes not until the system is released and being used.

Misunderstood requirements lead to large amounts of wasted effort during design, development, and testing. It is not uncommon to find the test team has interpreted a requirement differently than has the design and construction team. When that happens a large amount of rework is often required and is not recognized until very late in the project schedule. This often leads to delays and budget overruns.

Requirements defects also have largest impact on delivered quality. Industry benchmarks indicate only around 77% of requirements defects are discovered before product release. An amazing 1/3 of all delivered defects have their origin in requirements failures. Invariably these defects are more difficult and costly to fix as they impact the software design and construction – they have a ripple effect – even areas of the software not directly concerned with the flawed requirement must be changed. By analogy, if we make a post-construction change to the requirements for a house we may find we need to move load-bearing walls.

Follow us :
ComplianceOnline Banking Summit 2016 | Risk Management and Data Security - 80390SEM
ComplianceOnline Medical Device Summit 2017

Product Reviews

This product hasn't received any reviews yet. Be the first to review this product! Write review

Best Sellers
You Recently Viewed
    Loading