Quick Fix Design Using Joint Application Development (JAD) Facilitated Sessions with In-Session Documentation

(the yellow mark

Need to Solve a Business Problem. . .

shows the phase
targeted by this session)

Try our experienced JAD facilitator teams


	Quick Fix Design JAD Sessions

People Involved
Technical Components
Typical Activities
Potential Deliverables

Our Promise:

Audience focused implementation plan with action items
Cost-benefit based selection of best solutions
7-point evaluation of alternative strategies
Comprehensive solution generation process

Benefits:


	A quick fix is a short-term improvement to an existing situation that solves an identified problem without requiring retraining or major new technology. The benefits of the stop-gap solution have to be observable in a short period of time. A JAD session can help the right people identify potential fixes and select the best alternative.

Enables quick fixes that work the first time
Share best practices across multiple projects
Define reliable stop-gap solutions quickly
Decrease the potential for negative chain reactions
Define all associated activities at the appropriate level of detail
Generate innovative solutions by impacted parties
Test a potential solution before it is implemented



		Client Representatives, End Users, Business Managers, System Analysts, Business Analysts
		System Designers, Contingency Planners
		Business Process Owners, Operation Managers, Information Technology Managers, Data Administrators, Project Planners, Project Leaders, Auditors, Security, Developers, Standards, Vendors, Quality Assurance, Independent Verification and Validation Team, Production Planners, Information Technology Specialists, Human Resource Representatives, Trainers, Telecommunications Specialists, Technical Experts
		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.


		- Problem statements - Requirements documents - Existing process and procedure documentation - Existing system documentation
		Risk Assessment, Business Process Modeling, Workflow Diagramming, Prioritization, Breakout Sessions, Problem Definition, Problem / Symptom Reduction, Process Modeling, 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.

	Create high-level process model of business
	Identify mission critical application functions
	Identify environmental and social dependencies
	Overlay organizational chart on the process model
	Define process and interface ownership
	List all internal and external interfaces
	Develop workflow diagrams for complex activities
	Prepare preliminary contingency document
	Agree on testing, training and change management plans
	Define business problems and opportunities
	Create high-level data model of major business entities
	Define data entity ownership and responsibilities
	Define first-cut project scopes and initial estimates
	Create intuitive data model
	Define key attributes for entities
	Expand key attribute metadata
	Collect, analyze and document problem statements
	Determine problem causes based on process models
	Define benefits of solving problems
	Generate new system requirements
	Create problem statement/requirement statement matrix
	Evaluate existing system for "Quick Fixes"
	Create function statements for identified processes
	Define physical design constraints
	Identify discretionary design factors
	Expand new system process model to include functional controls
	Correlate physical design constraints to logical models
	Identify range of tradeoff design decisions
	Evaluate impact of tradeoff decisions on implementation
	Select final physical design alternative
	Define functional and data components of selected design
	Identify system-level control functions and data
	Initiate program/procedure detailed specifications
	Create preliminary project test plan




	Scope statements and diagrams clearly delineate the business areas covered by each quick fix component. Categorization of contingency actions by authority and by purpose of the plan (e.g., avoidance, containment or recovery). 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. Implementation plan and schedule with situations and dates when components or levels of the quick fix will be put into production by the proper authority. 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. This representation ensures sufficient coverage of the quick fix. Test and change management plans detail actions that have to be taken to validate the quick fix. Workflow diagrams indicate where specific manual procedures need to be modified. 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. Critical success factors identify information needs and systems that are critical for organizational success. Cross-references relate problems to symptoms and requirements. Current system process models are overlaid with problem statements and project scope. Quick Fixes are recommended short term, stopgap solutions based on the evaluation of the existing situation. Validated and prioritized business requirements break down into functional, performance, constraining, informational and subjective requirements. Open issues are unanswered questions and issues that must be resolved before continuing with the project. A testing strategy identifies testing goals, tools, and environment.