Sept09 Iiba Presentation

8/6/2019 Sept09 Iiba Presentation

1/24

Requirements Planning:Requirements Planning:

Presented by:Anita Keely, Sr. IT BSASteve Kubick, Sr. IT BSA

AutoZone Inc.

Presented by:Anita Keely, Sr. IT BSASteve Kubick, Sr. IT BSA

AutoZone Inc.

Reaping the Benefits for

Project Success

Reaping the Benefits for

Project Success


2/24

AgendaAgenda

Purpose and Audience

Planning Activity Part 1

Overview of BABOK Business Analysis Planning

Overview of AutoZone IT Business Analysis

Planning Top 10 Things Overlooked in Requirements

Planning

Planning Activity Part 2 Q & A - Open Discussion

References and Contact Information

Purpose and Audience

Planning Activity Part 1 Overview of BABOK Business Analysis Planning

Overview of AutoZone IT Business Analysis

Planning Top 10 Things Overlooked in Requirements

Planning

Planning Activity Part 2

Q & A - Open Discussion

References and Contact Information


3/24

Purpose and AudiencePurpose and Audience This presentations main goal is to emphasize the

importance of BA Planning and to suggest practical tools

and techniques that BAs can use in their day-to-day

activities.

The audience includes business analysts, business

systems analysts, project managers, and anyone playingthe BA role on software development projects.

BABOK tie-in: The topics covered here correspond to

Chapter 2 in the BABOK (v2.0), Business Analysis

Planning & Monitoring.

This presentations main goal is to emphasize the

importance of BA Planning and to suggest practical tools

and techniques that BAs can use in their day-to-dayactivities.

The audience includes business analysts, business

systems analysts, project managers, and anyone playingthe BA role on software development projects.

BABOK tie-in: The topics covered here correspond to

Chapter 2 in the BABOK (v2.0), Business Analysis

Planning & Monitoring.


4/24

Activity (Part 1): Create

Requirements Phase Work Estimate

Activity (Part 1): Create


Case Study: Big Bens New Help DeskSystem

Task: Provide an estimate on the numberof hours it will take you to complete therequirements phase activities.

Time Frame: 5 minutes


Task: Provide an estimate on the numberof hours it will take you to complete therequirements phase activities.



5/24

Business Analysis Planning& Monitoring

Business Analysis Planning

& Monitoring

Identifying Stakeholders

Anyone who has a vested interest in the project

Range from project software tester to CEO

Defining Roles and Responsibilities of

Stakeholders

Developing Estimates for Business Analysis

Tasks

Planning Communications with

Stakeholders

Identifying Stakeholders

Anyone who has a vested interest in the project

Range from project software tester to CEO

Defining Roles and Responsibilities of

Stakeholders

Developing Estimates for Business Analysis

Tasks

Planning Communications with

Stakeholders


6/24

Business Analysis Planning& Monitoring (contd.)


& Monitoring (contd.)

Planning Requirements Approach,

Traceability & Prioritization

Determining Requirements Deliverables

Defining Business Analysis Processes

Determining the Metrics to be Used for

Monitoring Business Analysis Work

Planning Requirements Approach,

Traceability & Prioritization

Determining Requirements Deliverables

Defining Business Analysis Processes

Determining the Metrics to be Used for

Monitoring Business Analysis Work


7/24

Business Analysis Planning& Monitoring (contd.)


& Monitoring (contd.)


8/24

AutoZone Planning MethodAutoZone Planning Method

AutoZone IT SDLC

3 Elements of Requirements Planning

1. Conduct Pre-requirements Analysis

Evaluation of information that is known or unknown prior to

the start of requirements2. Scope the Requirements Phase Work

Determining the initial boundaries of business analysis work

for the requirements phase.

3. Create Requirements Work Plan Documented framework for eliciting, analyzing,

documenting and managing project requirements.

AutoZone IT SDLC

3 Elements of Requirements Planning

1. Conduct Pre-requirements Analysis

Evaluation of information that is known or unknown prior to

the start of requirements2. Scope the Requirements Phase Work

Determining the initial boundaries of business analysis work

for the requirements phase.

3. Create Requirements Work Plan Documented framework for eliciting, analyzing,

documenting and managing project requirements.


9/24

Pre-requirements AnalysisPre-requirements Analysis

Scope Analysis

Stakeholder Analysis

Business Impact Analysis

ARS Analysis

Scope Analysis

Stakeholder Analysis

Business Impact Analysis

ARS Analysis


10/24

Scope AnalysisScope Analysis

Get the Scope Document

Analyze:

Project Description

Objectives

Critical Success Factors

In Scope

Out of Scope

Determine if Enough Info. is Defined

Get the Scope Document

Analyze:

Project Description

Objectives Critical Success Factors

In Scope

Out of Scope

Determine if Enough Info. is Defined


11/24

Stakeholder AnalysisStakeholder Analysis

Name

Title

Project Role

Business Area

Physical Location

Contact Info Preferred Communication Technique

Name

Title

Project Role

Business Area Physical Location

Contact Info

Preferred Communication Technique


12/24

Business Impact AnalysisBusiness Impact Analysis

Project Priority

Expected Benefits

Dependencies

Risks

Constraints

Deadlines

Project Priority

Expected Benefits

Dependencies

Risks Constraints

Deadlines


13/24

ARS AnalysisARS Analysis

High-level Business Goals

Amount Budgeted Overall

Amount Budgeted for Requirements

Participating Functional Areas

Third Party Vendors Involved

Compare ARS to Scope

High-level Business Goals

Amount Budgeted Overall

Amount Budgeted for Requirements

Participating Functional Areas Third Party Vendors Involved

Compare ARS to Scope


14/24

Scoping the Requirements

Work

Scoping the Requirements

Work

Decipher the Areas of Requirements

Elicitation Identify the Source of the SME for a

Requirements Area

Identify Initial Questions

Identify Elicitation Techniques

Identify Communication Techniques Identify Possible Representation of the

Requirements Work

Decipher the Areas of Requirements

Elicitation Identify the Source of the SME for a

Requirements Area

Identify Initial Questions

Identify Elicitation Techniques

Identify Communication Techniques Identify Possible Representation of the

Requirements Work


15/24

Create Requirements Work

Plan

Create Requirements Work

Plan

Whats Included in a Requirements Work

Plan?

Why Create a Requirements Work Plan?

Whats Included in a Requirements Work

Plan? Why Create a Requirements Work Plan?


16/24

Whats Included in a

Requirements Work Plan?

Whats Included in a


Initial Approach for Requirements Elicitation

Initial Approach for RequirementsDocumentation

List of Planned Requirements Deliverables

Number of Meetings for Each Deliverable

Estimated Hours to Complete Requirements

In Scope Items Mapped to Deliverables

Outline for 1st Requirement Session

Initial Approach for Requirements Elicitation

Initial Approach for RequirementsDocumentation

List of Planned Requirements Deliverables

Number of Meetings for Each Deliverable Estimated Hours to Complete Requirements

In Scope Items Mapped to Deliverables

Outline for 1st Requirement Session


17/24

Why Create a


Why Create a


BA Benefits

Project Benefits

BA Benefits

Project Benefits


18/24

Creating a Work Plan: BA

Benefits

Creating a Work Plan: BA

Benefits

Reveals Requirements Elicitation Starting Point

Provides a List of Requirements Deliverables

Provides a Justifiable Estimate of Effort

Forces You to Think About Requirements Up Front

Forces You to Map Scope to Requirements

Reduces Fear of the Unknown

Helps Identify an Unclear Project

Hones Your Planning Skills

Reveals Requirements Elicitation Starting Point

Provides a List of Requirements Deliverables

Provides a Justifiable Estimate of Effort

Forces You to Think About Requirements Up Front

Forces You to Map Scope to Requirements

Reduces Fear of the Unknown

Helps Identify an Unclear Project Hones Your Planning Skills


19/24

Creating a Work Plan: Project

Benefits

Creating a Work Plan: Project

Benefits

Identifies Unrealistic Deadlines and

Expectations

Affirms Value of BA to Project Success

Sets Realistic Expectations for BA Work

Defines Requirements End Point for Project

Planning

Identifies Unrealistic Deadlines and

Expectations

Affirms Value of BA to Project Success

Sets Realistic Expectations for BA Work Defines Requirements End Point for Project

Planning


20/24

Top 10 Things Overlooked

in Requirements Planning

Top 10 Things Overlooked

in Requirements Planning

10. Creation of Meeting Minutes

9. Unusual Project Methodology8. Meeting Preparation Time

7. Follow-up Meetings

6. Vendor Calls and Demos5. Team Availability and Location

4. Requirements Research Time

3. Document Revisions and Approvals

2. Stakeholder Types, Habits and Personalities

1. Analysis Time

10. Creation of Meeting Minutes

9. Unusual Project Methodology8. Meeting Preparation Time

7. Follow-up Meetings

6. Vendor Calls and Demos

5. Team Availability and Location

4. Requirements Research Time

3. Document Revisions and Approvals

2. Stakeholder Types, Habits and Personalities

1. Analysis Time


21/24

Activity (Part 2): Create a


Activity (Part 2): Create a



Task: Provide an estimate on the numberof hours it will take you to complete of the

requirements phase activities.



Task: Provide an estimate on the numberof hours it will take you to complete of the

requirements phase activities.



22/24


23/24

Reference MaterialsReference Materials

BABOK Guide (v2.0)

Seven Steps to Mastering Business Analysis

by Barbara Carkenord

The Software Requirements Memory Joggerby Ellen Gottesdiener

BABOK Guide (v2.0)

Seven Steps to Mastering Business Analysis

by Barbara Carkenord

The Software Requirements Memory Joggerby Ellen Gottesdiener


24/24

Contact InfoContact Info

Anita Keely, Sr. IT Business Systems Analyst

Ph: (901) 495-7926

Email: [email protected]

Steve Kubick, Sr. IT Business SystemsAnalyst

Ph: (901) 495-7206


Anita Keely, Sr. IT Business Systems Analyst

Ph: (901) 495-7926


Steve Kubick, Sr. IT Business SystemsAnalyst

Ph: (901) 495-7206


Sept09 Iiba Presentation

Documents

Transcript of Sept09 Iiba Presentation