• No results found

Requirements Change Management

N/A
N/A
Protected

Academic year: 2021

Share "Requirements Change Management"

Copied!
78
0
0

Loading.... (view fulltext now)

Full text

(1)

Requirements Change

Management

Task 2.5 June 14, 2012

(2)

Changing Change.

Develop the Professional. Develop the Profession.

© International Institute of Business Analysis

(3)

( C ) I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

3

Looking for a Career?

• Visit IIBA Career Centre

Search for and apply to local, business analyst positions.  Let employers find you. Market yourself by posting a

resume, professional profile, and portfolio of work.

 Store versions of your resume, cover letters, and contact

information.

 Set-up job alerts to be emailed when new jobs are

posted.

(4)

Vision and Mission

Develop and maintain standards for the practice of business analysis and for the certification of its practitioners

IIBA® is an international not-for-profit professional association for

business analysts.

The world's leading association for Business Analysis professionals

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

(5)

( C ) I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

5

Tom Karasmanis

• IIBA Product Manager

 Tom Karasm anis is a Senior Consult ant w it h 25 y ears'

experience in I nf orm at ion Technology, including roles as a

Business Archit ect , Business/ Sy st em s Analy st , Project Leader,

Technical Archit ect , and Sof t w are Engineer. He has w orked in f inancial serv ices, publishing, healt hcare, public sect or and t elecom m unicat ions.

 Tom serv ed as Chief Archit ect of t he I I BA f rom 2009 t o 2011. He is

current ly I I BA Product M anager of Bei ng a BA: Techni cal Excel l ence and

Vendor Showcase. Tom is a m anagem ent consult ant in business

archit ect ure and business analy sis, assist ing organizat ions t o build or im prov e t heir BA pract ices. He speaks regularly at int ernat ional

conf erences.

 Tom holds a Bachelor of Applied Science in Chem ical Engineering f rom

t he Univ ersit y of Toront o and is act iv e in t he business analy sis and business archit ect ure com m unit ies.

(6)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

6

Outline

 Introductions and Housekeeping 12:00

 Vendor Presentations 12:05

• Seapine Software 12:05

• Jama Software 12:20

• TechnoSolutions 12:35

 Questions and Answers 12:50

 Close 12:59

(7)

IIBA Host

Tom Karasmanis

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

7

Question and Answer

• How to Ask Questions

 Use the Question box to ask questions.

Selected questions w ill be answ ered at the end, but you can ask at any time.

 Include the vendor ’s name if you w ant

a specific vendor to respond.

 Short, specific questions, please!

Ashu Potnis Derwyn Harris

(8)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

8

Requirements Change Management

Agenda

1. Purpose

2. Description

3. Input: Plan Business Analysis Approach

(9)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

9

Requirements Change Management

 Part of Task 2.5 – Specifically 2.5.4.5

 Also discussed in 2.1.4.4

Purpose

 Define the process that will be used to

manage change to the requirements or solution scope.

(10)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

10

Requirements Change Management

Description

 Process for requirements change

 Which stakeholders need to approve

change

 Who will be consulted or informed of

change (and who does not need to be involved)

(11)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

11

Plan Business Analysis Approach

Input to 2.5

 Effect of business analysis approach on

requirements change management (2.1.4.4)

 Depends on approach:

Plan-driven approach

(12)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

12

Plan Business Analysis Approach

Plan-driven Approach

 Only necessary changes (business case)

 Full analysis / impact analysis

 Change request / mini-project

Change-driven Approach

 Changes are treated the same as new

requirements – no business case

(13)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

13

Requirements Change Management

Determine process for change requests

 Who can authorize what; when to escalate

 Plan-driven:

• Change Control Board; formal process

 Change-driven:

• Project team has more control; less analysis

Impact analysis

(14)

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

14

Requirements Change Management

Plan the wording of the request

 Cost and time estimates of change

 Benefits and risks of change

 Recommended course of action

 Update project artefacts

(15)

Requirements Change Management IIBA Vendor Showcase - Seapine Software

Peter Varhol, Solutions Evangelist

June 14,

(16)

Agenda Impact Analysis Communicating Change Managing Authorizations Configurable Process CM Challenges

(17)

Process Authorization

Impact

(18)

Configurable Process

• Fits

• Automation

• Flexible

(19)
(20)
(21)

Managing Authorizations

• Permissions • Audit Trail • Ease of Use

(22)
(23)
(24)

Impact Analysis

Credit: Flickr, dgeezer

• Qualitative Data • Affected Artifacts • Re-work

(25)
(26)
(27)
(28)

Communicating Change

• Automated • Recorded • Traceable

(29)

Communicating Change

(30)
(31)
(32)
(33)

Thank you!

• Seapine TestTrack

www.seapine.com/testtrack.html

• Seapine View Blog

http://blogs.seapine.com/

(34)

Contour & Change Management

BA Times Partner Webinar

(35)
(36)

Typically a cumbersome process High reliance on a single person Document-centric process

Lack of visibility

Difficult to understand the impact

(37)

Change Requests

Change Control Board Versions of Documents

(38)

Change Requests

Change Control Board Versions of Documents Incremental Requestor Scope History Workflow Schedule People Suspect Impact Collaboration Overarching Baselines Notification Compare

(39)

DIFFICULTY VO L U M E O F D A T A ( C O M PL EX IT Y) Analysis Sign-off Traceability Development Deployment

(40)

DIFFICULTY VO L U M E O F D A T A ( C O M PL EX IT Y) Analysis Sign-off Traceability Development Deployment

(41)
(42)
(43)
(44)
(45)
(46)
(47)
(48)
(49)
(50)
(51)
(52)

Leverage your collective genius.

(53)

Requirements

Change Management

Presenter

Ashu Potnis

(54)

Track

Change Requests against individual repository artifacts

Requirements Change Management with TopTeam

(55)

Different Requirements Change Management Process is needed for different types of artifacts

Textual Requirements User Stories

(56)

Define Lifecycle for Requirements Artifacts

Configure

States & State Transitions

Each artifact’s maturity can be tracked by its state

Certain States can enforce change control

(57)

Stakeholders can submit a general Change Request from TopTeam Web

Submit

Change Request

Request Type can be specified (e.g. ER vs CR)

(58)

OR Stakeholders can submit Change Request against a specific artifact from TopTeam Web

Submit Change Request against a

(59)

Change Request Submission

Change Request is linked to the artifact

Change Request Form & Fields can be

(60)

Change Request is linked to the specific artifact

Change Request is assigned a unique

(61)

Change Requests can be submitted by Users when participating in Online Reviews and Approvals

Choose CR Type (e.g. ER vs CR)

(62)

All pending CRs in the Project can be tracked via the Change Request List

Use the CR list to Filter, Sort, Bulk Edit, etc.

(63)

Define Change Request Lifecycle

Configure

States & State Transitions

Change Requests follow the defined

(64)

User Business Analyst Product Manager Project Manager Developer Quality Assurance

(65)

Before Approving Change Request – we can run a Traceability Impacts Report

Multi-Level Trace report helps understand the magnitude and nature of impact on the system

Run Impacts Report

(66)

Change Request is Approved. Requirement is Updated.

Change Request

is Approved Product Manager

updates corr. Requirement

(67)

TopTeam keeps complete version history of changes made to Requirements along with a “Diff” view

Complete Version History

Version Compare view show exactly

what changed “Diff”

(68)
(69)

Compare Project Baselines to highlights differences in Requirements at important milestones

Choose Baselines to compare

Drill down with Version Compare to

see what changed “Diff”

(70)

Stakeholders are Notified of the Changes

Continuous

Activity Stream keeps everyone updated

Email notifications appear in your In box

(71)

Business Process Diagrams Screen Mockups Requirements Business Rules Use Cases Trace Links Open Source

(72)

San Francisco

Sydney New York

London

Anytime Anywhere Access

(73)

Rich Internet Explorer Plugin App Web Access and Collaboration Offline Desktop App

TopTeam Open API

(74)

integrations

This image cannot currentl y be d… Quality Center This image cannot

currently be

displayed. Team System (TFS)

TopTeam Open API (Integrate anything) Microsoft Word This image cannot current ly be … Microsoft Excel This image cannot currentl y be d…

(75)

• Requirements • User Stories

• Use Case Scenarios • Entity-Attributes

• Business Process Modeling • End-to-End Traceability

• Test Cases

• Online Reviews and Approvals • and more

(76)

Learn more or try it yourself

TopTeamAnalyst.com

"I am enjoying using TopTeam. It allows me more creative time, instead of document formatting time, so my analysis is better and

more detailed." Carl Knowlan

Senior Analyst & Product Manager Houston, Texas

(77)

IIBA Host

Tom Karasmanis

© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

77

Question and Answer

• How to Ask Questions

 Use the Question box to ask questions.

Selected questions w ill be answ ered at the end, but you can ask at any time.

 Include the vendor ’s name if you w ant

a specific vendor to respond.

 Short, specific questions, please!

Ashu Potnis Derwyn Harris

(78)

Peter Varhol Seapine Software [email protected] Ashu Potnis TechnoSolutions [email protected] Derwyn Harris Jama Software [email protected]]

Contact Information

Register for more webinars on the Professional Development page of our website – under Webinars.

78

© International Institute of Business Analysis

References

Related documents

Lesson 11: Product Owners increasingly need a mix of Business Analyst and Product Manager skills. Product Manager, Project Manager or

Objective – user satisfaction with software product Analyst goal – accurate requirements. Developer goal – software that

The project consists of a group of peers with following roles: Project Manager, Con- figuration Manager, Quality Assurance Manager, Web-master, Requirements Manager, Design

The project manager will either assign the change priority based upon the level of impact of the change to the project or escalate the change to the End

1) Project Manager —Responsible for the overall management and implementation of the project including the Quality Management Plan. 2) Construction Quality Assurance

Modify Completed Work Track Actual Effort, Cost, Delay Customer Change Request Assigned Change Request Impact Statement Completed Change Request Form Project Plan

The Project Manager will forward the Change Request From and any supporting documentation to the Change Control Board (CCB) for review and final approval. The CCB

Tester Developer Architect IT / Project Manager Business Analyst Database Professional Designer Software Quality Team Collaboration Project Transparency.. IT Organizations are