As part of the Catalyze webcast series, Carol Miller will show us that there's more than one way to find a requirement in our second Catalyze webcast originally broadcast on September 20, 2007.
Carol is the VP of Professional Development for Advanced Concepts Center (ACC) and is also the VP of Professional Development for the Philadelphia chapter of the IIBA.
4. Requirements Elicitation The process, tools, and techniques used to actively obtain information from stakeholders regarding their view of the requirements Source: IIBA - A Guide to the BA Body of Knowledge v1.6 If only it was this easy! To Elicit: 1. to draw forth or bring out (something latent or potential) 2. to call forth or draw out (as information or a response) Source: Merriam Webster
5.
6. The Jungle Can You Find? Functional Requirements Business Requirements Quality of Service Requirements Implementation Requirements User Requirements
7.
8.
9.
10. Stakeholder Template SME Infrequent user Decision maker Casual user Information keeper (information is power) Frequent user Has ear of decision maker Spokesperson Charismatic leader Champion Controls funding Supporter Examples of Influence: Examples of Interest: Desired Current Commitment Level (HML) Influence Interest Name Stakeholder Role Stakeholder Information and Analysis
14. A Requirements Framework Knowledge Area Tasks Deliverables Requirements Communication and Management Training Enterprise Analysis Quality Assurance Techniques Guidelines, standards, reviews and inspections Requirements Planning Requirements Elicitation Reqm’ts Analysis & Documentation Solution Assessment and Validation
15. A Requirements Elicitation Approach Identify, Analyze, and Document Stakeholders Choose Elicitation Technique(s) Develop Questions for Each Chosen Stakeholder For Each Stakeholder or Group of Stakeholders Entry Criteria: Do You Understand Project Objectives and Scope? Plan Session, Develop & Send Materials Conduct the Elicitation Session Document the Stakeholder Requests Exit Criteria: Questions Answered? Requirements Analysis and Documentation Create/Update the Glossary of Terms
16. Which Requirements Are You Eliciting? Business Requirements Functional Requirements Quality of Service Requirements Constraints Assumptions Problem Space Solution Space What is the Scope of Your Responsibility?
17.
18.
19.
20. Identify your Stakeholder VIP’s I’m the “subject matter expert”. I’m well-respected, I know many important details, and I have lots of specific experience. You need me! I’m the “champion”. I may not know all the details, but I really like what you’re doing. I am influential and can convince people why they should like it too. You need me! I don’t necessarily ‘do’ the work around here, but I know lots of people in the organization, and can put you in touch with just the right one. You need me! Maven Salesperson Connector
21.
22.
23.
24.
25.
26.
27.
28. Example: ATM Context Diagram « keypad » identity account amount ATM Patron Bank Employee Bank Manager Bank Teller Courier ATM Technician Nightly Backup « display » balance status « printer » receipt « router » atm id patron info account amount atm status « router » patron status account balance terminal status ATM System « actor » Bank
29.
30.
31. A Requirements Elicitation Approach Identify, Analyze, and Document Stakeholders Choose Elicitation Technique(s) Develop Questions for Each Chosen Stakeholder For Each Stakeholder or Group of Stakeholders Entry Criteria: Do You Understand Project Objectives and Scope? Plan Session, Develop & Send Materials Conduct the Elicitation Session Document the Stakeholder Requests Exit Criteria: Questions Answered? Requirements Analysis and Documentation Create/Update the Glossary of Terms
Presenter Script: Welcome. It’s great to see such a great turnout today. I’d like to thank Tom and irise for inviting me to host today’s webinar. I hope you’ll find value in the time we spend together. This is a picture of me and I get out to a number of the industry conferences and IIBA chapter meetings, so if you see me in the future, you now know what I look like, so please stop and say hi. Today's topic centers on one of the core tasks performed by the Business Analyst – requirements elicitation. On the surface, sounds pretty straightforward. But in reality, it is one of the most difficult, most error prone, and most communication intensive tasks we face. Elicitation lies at the heart of requirements engineering - Getting the right requirements and documenting them in the right way to ensure your team builds the right solution. So today we’re going to talk about some things you should keep in mind as you plan out your next project.