22.03.2013 Views

Establishing the Product Vision and Project Scope

Establishing the Product Vision and Project Scope

Establishing the Product Vision and Project Scope

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

80 Part II Software Requirements Development<br />

Conflicting Business Requirements<br />

Business requirements collected from multiple sources might conflict. Consider<br />

a kiosk containing embedded software, which will be used by a retail store's<br />

customers. The kiosk developer's business objectives include <strong>the</strong> following:<br />

• Generating revenue by Ieasing or selling <strong>the</strong> kiosk to <strong>the</strong> retailer<br />

• Selling consumables through <strong>the</strong> kiosk to <strong>the</strong> customer<br />

• Attracting customers to <strong>the</strong> br<strong>and</strong><br />

• Making a wide variety of products a vailable<br />

The retailer's business interests could indude <strong>the</strong> following:<br />

• Maximizing revenue from <strong>the</strong> available floor space<br />

• Attracting more customers to <strong>the</strong> store<br />

• Increasing sales volume <strong>and</strong> profit margins if <strong>the</strong> kiosk replaces manual<br />

operations<br />

The developer might want to establish a high-tech <strong>and</strong> exciting new direction<br />

for customers. The retailer wants a simple turnkey system, <strong>and</strong> <strong>the</strong> customer<br />

favors convenience <strong>and</strong> features. The tension among <strong>the</strong>se three parties<br />

with <strong>the</strong>ir different goals, constraints, <strong>and</strong> cost factors can lead to inconsistent<br />

business requirements. The project sponsor must resolve <strong>the</strong>se conflicts before<br />

<strong>the</strong> analyst can detail <strong>the</strong> kiosk's system <strong>and</strong> software requirements. The focus<br />

should be on <strong>the</strong> fundamental objectives for <strong>the</strong> product that will deliver <strong>the</strong><br />

maximum business value ("increase sales to new <strong>and</strong> existing custorners"). lt's<br />

easy to be distracted by superficial product characteristics ("innovative user<br />

interface that attracts customers") that don't really state <strong>the</strong> business objective.<br />

lt's also up to <strong>the</strong> project sponsor (or sponsors) to resolve conflicts among<br />

various business stakeholders, ra<strong>the</strong>r than expecting <strong>the</strong> software team to<br />

somehow figure <strong>the</strong>se out. As more Stakeholders are identified <strong>and</strong> more constituencies<br />

with competing interests climb aboard, <strong>the</strong> risk of scope creep<br />

increases. Uncontrolled scope creep in which Stakeholders overstuff <strong>the</strong> new<br />

system in an attempt to satisfy every conceivable interest can cause <strong>the</strong><br />

project to topple under its own weight, never delivering anything of value.<br />

Resolving such issues is often a political <strong>and</strong> power struggle, which lies outside<br />

<strong>the</strong> scope of this book.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!