When software products are late to launch, a practical solution is to drop features from a release while still delivering a product your customers will love. If part of your process is to tie business objectives to product features, you'll have at hand the information needed to decide how to proceed-as well as a guide to prioritize development efforts throughout the project. Joy Beatty explains how to elicit measurable business objectives from stakeholders. She demonstrates how to write statements that describe how a feature contributes to business objectives and ways to assign a business value to each feature. Armed with this data, stakeholders can compare features quantitatively, taking emotion out of scoping decisions. As a reminder of the techniques discussed, Joy shares a Business Objectives Model quick reference for you to take home and use in your requirements elicitation sessions.
Using Business Objectives to Design Better Products
1.
BW2
Concurrent Session
11/7/2012 10:15 AM
"Using Business Objectives to Design
Better Products"
Presented by:
Joy Beatty
Blue Ocean Services at Seilevel, Inc.
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888‐268‐8770 ∙ 904‐278‐0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Joy Beatty
Seilevel
Joy Beatty is vice president R&D at Seilevel, a professional services company helping customers redefine
how they create requirements to ensure only the most valuable features get built. Joy drives new
methodologies that improve elicitation, requirements modeling, and business analysis COEs. She developed
Seilevel’s BA training curriculum and provided training to more than 600 BAs through seminars, industry
conferences, and Seilevel classes. She has authored several papers in refereed journals, is currently working
on the IIBA® BABOK v3, and writes about Seilevel methodologies on seilevel.com, on the blog, and in a
new book Visual Software Requirements.