Quality Starts with Requirements (Feb 2012, Patrick Martin)
-
Upload
iiba-rochester-ny -
Category
Business
-
view
926 -
download
2
description
Transcript of Quality Starts with Requirements (Feb 2012, Patrick Martin)
© International Institute of Business Analysis™
Quality Starts With Requirements
Speaker: Patrick Martin
February 8, 2012
Agenda
§ Board of Directors Introductions § Announcements & Upcoming Events § Call for Volunteers § Program
Quality Starts With Requirements
2 Copyright International Institute of Business Analysis™
3
The 2011-2012 Board
§ President - Michelle Walter § Executive Vice President - Chris Gangai § VP of Finance - Ted Husted § VP of Membership - Carol Larsen § VP of Technology - Darlene Erhardt § VP of Professional Development - Denette Mitchell-Perez
4 © International Institute of Business Analysis™
Announcements § Study Group
• April / May timeframe • Sign-up at back table!
5 © International Institute of Business Analysis™
§ March 7 – Video Conference: “Increasing the
perceived value of business analysis activities” Laura Brandenburg (Clear Spring Business Analysis, CO & host of Bridging the Gap)
§ April 4 – “Introducing Business Analysis to Your Organization” Francine Wolfe (Senior BA, Cushman & Wakefield, NYC)
Upcoming Events
6
We Need Your Help! § Have an idea you’d like implemented? § Have some time to help us out? § See Michelle!
7 © International Institute of Business Analysis™
Event Sponsors
Patrick Martin February 8th, 2012
Quality Starts with Requirements
� If Quality means conformation to requirements and the requirements are in error, have we delivered quality?
� Do we conform to requirement errors? � Do we conform to totally new requirements?
Requirement Defects � Defects in requirements are the hardest to find, prevent and
repair as well as the most pervasive and severe. � Requirements contain 15% of all software errors � Requirements defect often outnumber code defects � Requirements often grow throughout the PMLC lifecycle � Defect Removal Efficacy from Requirements Inspection is
between 20% - 50%
Customer Delight - Context � Stakeholder Points of View
� Financial & Strategic � Customer & Market � Team & Workforce � Operational Core Practices � Operation Support Practices � Technology
� Story Telling – Emotional Context � Inquiring � Listening
Customer Delight - HGTV � Stakeholder Points of View - HGTV
� Financial – Father & Production Company � Customer – Daughter & Mother � Team & Workforce – Production Company � Operational Core Practices – Mother & Family � Operation Support Practices – Mother & Family � Technology – Production Company
� Story Telling – Emotional Context � Inquiring � Listening
Scope Creep � Desire - Compass � Delivered – South Pointing
Chariot
Scope Creep – Control � Locking in Scope
� Stakeholder Consensus on Context � Iterative Agreements on Detail
� The Bradley Tank
Customer Delight – Clear & Concise US Army Signal Corp Specification 486 � Established the requirements for the first military aircraft.
Aircraft must be able to: � Carry 2 persons � Reach speed of 40 mph � Carry sufficient fuel for 125 mile nonstop flight � Be controllable in flight in any direction � Fly at least one hour � Land at take-off point, without damage � Be taken apart and reassembled in one hour � No Military Operational Requirements Specified
Who Says Penguins Can’t Fly
Executive Sponsors (aka The Ones with Parachutes)
Customers (aka Freaks)
Project Manager & Project Team (aka The Penguins)
� If Quality means conformation to requirements and the requirements are in error, have we delivered quality?
� Do we conform to requirement errors? � Do we conform to totally new requirements?