Business Requirement Gathering Using Joint Application Development (JAD) Facilitated Sessions with In-Session Documentation

(the yellow mark

Need to Define Business Requirements. . .

shows the phase
targeted by this session)

Try our experienced JAD facilitator teams


	Requirements Gathering JAD Sessions

People Involved
Technical Components
Typical Activities
Potential Deliverables

Our Promise:

Business problem based requirements validation
Multi-tiered requirements prioritization process
5 component requirements decomposition
Repeatable requirements generation approach

Benefits:


	Requirements gathering introduces technology specialists to what the end-user needs and how those needs influence the technological solution. Business experts need to understand the consequences of the tradeoff decisions they will be asked to make as the project progresses. A JAD session creates an environment that inspires both sides to get what they need with minimal time investment.

Gather business and system requirements in short time frame
Assess the impact of proposed requirements
Increase buy-in by all project participants
Prioritize and scope requirements dynamically
Achieve consensus of requirements by all stakeholders
Eliminate requirements that cost more than they are worth
Reduce the major cause of project failure



		Operation Managers, Client Representatives, Business Analysts, Business Managers, End Users
		Data Administrators, System Analysts, Data Analysts
		Business Process Owners, Information Technology Managers, Database Administrators, Project Leaders, Auditors, Security, Standards, Vendors, Quality Assurance, Contingency Planners, Human Resource Representatives, Trainers
		We offer experienced JAD facilitation teams (session leader and session analyst) with proven track records who work virtually or at your site to deliver the best possible result.


		- Data models - Process models - Project scope and objective - Corporate standards - Policy and procedure documentation
		Prioritization, Breakout Sessions, Problem Definition, Problem / Symptom Reduction, Interviewing Techniques, Scoping Techniques, Cost/Benefit Analysis, Requirements Definition, Requirements Decomposition, Requirements Validation
		Diagramming tools, Spreadsheets, Word processors, Upper CASE

All of the following business system analysis activities and deliverables can also be supported via e-Coaching


	Each session is unique. We create the actual session agenda together with you based on your business needs. The selection of the deliverables is a pre-session activity.

	Define business problems and opportunities
	Evaluate impact of emerging technologies
	Identify first level data entities
	Create high-level existing system process model
	Scope project
	Collect, analyze and document problem statements
	Determine problem causes based on process models
	Define benefits of solving problems
	Define project objective
	Generate new system requirements
	Create problem statement/requirement statement matrix
	Decompose and prioritize new system requirements
	Create function statements for identified processes
	Initiate preliminary new system process model
	Expand preliminary new system process models
	Assign post-session tasks and schedule post-session meeting
	Populate data stores with required data elements
	Create first-cut data model for proposed system
	Walk-through logical design documentation
	Expand new system process model to include functional controls
	Define functional control data
	Evaluate organizational standards and guidelines
	Identify system-level control functions and data
	Initiate program/procedure detailed specifications
	Evaluate impact of failure to meet requirements




	Critical success factors identify information needs and systems that are critical for business continuity. Validated and prioritized business requirements break down into functional, performance, constraining, informational and subjective requirements. Risk assessment of potential internal and external disruptions that can either degrade or interrupt performance of business functions, operation of plants, or affect the quality of products and services. High-level process models show business functions performed by organizational units and the internal and external information flows they produce and need. Business function/system matrixes relate applications or automated functions to business functions. List of assumptions that define the baseline against which each deliverable was established. If the baseline is changed, the validity of the other deliverables is at best questionable. Post-session task assignments define the actions that individuals have to do to clarify open questions or resolve open issues. Problem/opportunity statements define what the organization has to address. Data rules constrain the structure of information stored in the attribute, e.g., numeric/alpha, number of characters, storage type, etc. Data validation rules constrict the values stored in the attribute. Business rules document organizational decisions. Default values are assigned to attributes in the absence of an explicit value. A synopsis contains a short overview of the results of the entire session for the management review The project objective relates this project to strategic corporate goals. Cross-references relate problems to symptoms and requirements. Open issues are unanswered questions and issues that must be resolved before continuing with the project. Module descriptions specify all required algorithms and control logic for each module of the system. Procedure definitions specify procedures for use of the automated system.