Requirement Management and Product Quality

8/6/2019 Requirement Management and Product Quality

1/29

Requirement Management & Product Quality

in the context of managing development projects

Grace Shi, MBA, PMP

Sr. Project Manager

VanQ Society, BCIT Campus, Thurs Feb 22 nd , 2007

ACS


2/29

Applied Concept Solutions Inc. 2

http://www.flickr.com/photos/osilla/80500328/


3/29


Real Need?Right

reqts?

right design?Same need?

Problematic??


4/29


ACS


5/29


Agenda

To discuss about requirement management What is it? Why is it important? Relation to product quality, i.e. QA as is - Where we are at? to be - Where we should go?

Key words Requirement management

Product quality

ACSO bjective


6/29


Agenda

1. W hat is requirement management?2 . W hy do we need requirement management?3. Why requirement management can impact product quality? and how?

4. What is the current status?5. What is the desired future state?6. Workshop and open discussion

ACS Agenda


7/29


Business wants IT as a supporting organization to do something to help Increase resources productivity lower cost Increase production efficiency lower cost

Assist delivery new products/services competitive edge Provide better services to the customers sustain market share Improve (automate, streamline) the business processes lower cost

Examples New product innovation

A feature what is needed is clearly defined (e.g. add a FAQ to anonline order system.)

Process improvement only the outcome is defined, but may not bequantitatively (e.g. website performance should be faster)

ACS

1 . What is requirement management?

Business definition


8/29


In software engineering, a requirement is a description of what asystem should do. Systems may have from dozens to thousands of requirements. http://en.wikipedia.org/wiki/requirements

ACS

System XYZ

A

B

C

In great details: What the following should do:

XYZ output and input C omponents A, B, C

Interfaces between A, B, C

When to do what

Under what circumstances (Why and with Whom)

For large systems, the sum canbe hundreds thousands


System definition


9/29


H ere come the challenges :

H ow to translate the business need to system requirements precisely sothat they both work in their own contexts systematically (the business

need makes sense to business people and it is also aligned to thecorporate goal and it is doable; the system requirements make sense toIT people and the impacts are manageable and it is feasible toimplement technically)

H ow to break down the system requirements to an appropriate level atwhich the business need can be validated.

ACS


C hallenges!


10/29


Agenda

1. W hat is requirement management?2 . W hy do we need requirement management?3. Why requirement management can impact product quality? and how?

4. What is the current status?5. What is the desired future state?6. Workshop and open discussion

ACS Agenda


11/29


System requirements characteristics C orrect C omplete Testable

UnambiguousBusiness needs characteristics There is no right or wrong Descriptive Drive is not mentioned nor obvious

Big picture behind Multiple contexts Sometime the real need is not what is described

ACS2. Why requirement management?

A C hasm!


12/29


C hanges are inevitable! Market C ompetitor Technology

C lient initiated Mistaken requirements discovered later To simply lock up the requirements is not in the best interest of business

C hanges may occur any time in the lifecycle


C hanges!


13/29


L ifecycle requirement management C oncept Gathered analyzed negotiated modeled verified defined

documented - signed-off L inked

C hanged, tested, released C ontrolled, traced, and managed


L ifecycle C oncept!


14/29


Management offers a means of tracking monitoring, Updating

C ontrollingTo ensure First time right, remember the chasm? C hanges over lifecycle C omplexity and interdependency between phases and deliverables

The conclusion: We need requirement management!


The C onclusion


15/29


Techniques to make first time rightTechniques to manage requirement changesTechniques to manage requirements in the project lifecycle

Use tools to manage requirementsWho owns of requirement management?Who is accountable for requirement management?What does a project manager need to do in requirement management?The qualifications of a competent Business Analyst

R equirement management and product quality H ow requirement management can impact project on time delivery H ow requirement management can impact project on budget delivery


Areas of Discussions


16/29


Agenda

1. W hat is requirement management?2 . W hy do we need requirement management?3 . W hy requirement management can impact product quality? and

how?4. What is the current status?5. What is the desired future state?6. Workshop and open discussion

ACS Agenda


17/29


C ustomers perception C ustomers expectation against their own experiences of

O f a known brand O f the same brand but different product

O ver competitors similar offeringsWithin the development picture Quality is the degree to which the pre-defined requirements are met Defect is used as a measurement

ACS3. Requirement Management & Product Quality

What is quality?


18/29


D efects

The GOAL is to Decrease the # of defects Find as many defects as early as possible in work products while running

scenarios before the product is shipped out of the door

ACS

Defects found by thereal users

shipment/release date

Fix or Defer

Defects found by QA

Release

R eworkCostly!

NegativeImpactW orse!

3. Requirement Management & Product Quality

Product Quality


19/29


D efects breakdown: R equirements management 62 .5% Design 11 .3% C oding 1 0% Environment 4.9% Test data or test scripts or execution errors 11 .3%

R equirement management defects breakdown : R equirement Completeness 37 .5% Requirement Presentation 34.7% Requirement C hanges 11 .2% Requirement Incorrect 8.7%

R equirement Completeness defects breakdown : Incomplete Requirements 73.4% Missing requirements 11 .2% O verly generalized requirements 4.6%

-- Defect Prevention Techniques for H igh Quality and Reduced C ycle Timehttp://www.iscn.ie/select_newspaper/measurement/motorola2.html


Defect O rigins


20/29


ACS

Defect Origins BreakdownRequirementCompleteness

RequirementPresentation

RequirementChanges

RequirementIncorrect

3. Requirement Management & Pro duct Qualit y

De f ect O rigins Brea kd owns


21/29


H ave we found all the defects ? All requirements tested? If not, why not all? All changed requirements and affected requirements tested? H ow to make the tradeoff when required? What are the factors?

H ave we fixed all the found the defects? What to defer and what to fix? What are the factors (business, blocking issues)? H ow do we know the fixes are real? H ave we retested all the fixed? H ow do we know the fixes dont break something else? H ave we

regression-tested all the fixed? H ow to make the tradeoff when required? What are the factors? H ave we implemented all the fixes ? In which releases ? H idden defects?!


The C orrelation


22/29


A sub-project that contains all the components Plan and analysis Design and build Test and integration

Mostly derived from defects

Missing requirements Incomplete requirements Incorrect requirementsNew requirements

C hanged requirements and affected requirementsMake the changes and integrate the changes into the system

H ow to plan testing test coverage, regression test, scenario design


C hange Requests


23/29



Systematic Approach

Test Execution

Reqt Mgmt Change Mgmt

D efect Mgmt Test Planning

R elease MgmtR eqt repository C R repository

Scripts repositoryD efect repository

D efect fixing Team


24/29


Agenda

1. W hat is requirement management2 . W hy do we need requirement management?3. Why requirement management can impact product quality? and how?

4 . W hat is the current status?5. W hat is the desired future state ?6. Workshop and open discussion

ACS Agenda


25/29


ACTIVITIES AS IS"

requirement gathering be told or be supplied with a list

requirement analyzing business impact, technology feasibility, time/cost constraints

requirement modelling very rare (needs analytical skill and IT knowledge)

requirement negotiating very rare (needs thorough understanding and real care)

change tracking some change requests are managed in some companies.

change tracing Rare

lifecycle linkage Rare

use of tools Word, Excel, occasionally Visio

documentation some do, mostly don't, no documentation management

accountability seems like no one is accountable?

ownership Business Analyst?

accessibility in different places, not everyone has access

QA manager not involved until later phases

Product manager mostly only involved at beginning, then hands-off.

The Client mostly only involved at beginning, then hands-off.

Business Analysts new profession; individual's capability varies greatly


26/29


ACTIVITIES TO BE"

requirement gathering interactive, partnering with the client

requirement analyzing business impact, technology feasibility, time/cost constraints

requirement modelling prototype, storyboard, prove of concept, test of the design

requirement negotiating consultant mentality, honest about what is the best

change tracking change management, change control board

change tracing horizontally across the system, through phases

lifecycle linkage through phases

use of tools utilize the most compelling technology that suits the nature

documentation everything is documented and managed completely

accountability Every stakeholder

ownership Every stakeholder

accessibility Every stakeholder

QA manager Completely involved, end to end.

Product manager Completely involved, end to end.

The Client Completely involved, end to end.

Business Analysts a discipline; capable and competent


27/29


Agenda

To discuss requirement management What is it? first time right, lifecycle concept, manage change Why is it important? project success

as is - Where we are at? not managed Impact on QA high # of bugs, design change, change requests Impact on project delay (then over budget) to be - Where we should go? fully managed

Key words Requirement Management Product Quality

ACSReview


28/29


29/29


Agenda

The project:The project My H omeDVD is to deliver a simple web-based movie librarymanagement application for the family members who can browse their own recordsincluding the movies borrowed and the due dates for the borrowed movies.The project status:The coding phase is completed and the integration test is done. Based on the pre-

defined test cases, 2 defects are found. After a thorough investigation,1

of the 2defects is not valid the defect is caused by a missing requirement (e.g. forgot theLogoff button). After negotiating with the key stakeholders, it is agreed that it iscritical to implement the missing requirement. As a result, C R1 01 is raised.The question:If you take over the project right at this moment, what are those key things that youwould like to do?

Your action items:

Please discuss this with your group to come up with a summary. Then each grouppresents the summary to the audience.Hints:Focus on requirement change management, think of the requirement repository,affected requirements, test plan and test cases.

ACSWorkshop Scenario # 1

Documents

Requirement Management and Product Quality