We need to speed up the query search time in the problem database.
To increase productivity in the Help Desk, we need to speed up the query search time in the Problem database.
Speeding up the problem database search time will save the company approximately $300,000 per year and prevent increases in staff.
Help Desk staff wait an average of 30 seconds per query, resulting in an average of 10% longer calls than the industry average.
A need or want of the business to solve a problem or achieve an objective.
A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
A condition or capability of a product or solution that documents a problem or objective of the business.
A need or necessary feature of a system that could be sensed from a position anywhere within the system.
A business rule is a directive that supports a business policy. A business requirement is a high level statement of the goals, objectives or needs of the enterprise.
A business rule is a an operating principle or self-imposed constraint on the business that applies to a specific project. A business requirement is a need or want of the business to solve a particular problem or achieve an objective.
A business rule is a particular type of processing requirement pertaining to the way business processes are performed, such as ''Interest will always be calculated using the rule of '78ths'.'' A business requirement is a feature or function of a product or solution that satisfies a need or want of the business to solve a problem or achieve an objective.
A business rule is a particular type of data requirement pertaining to the relationships between data classes/entities, for example, 'A Customer has one or more Accounts.' Business requirements may be stated as business rules, but they can also be other types as well.
Functional or non-functional requirements described in broad strokes.
Functional requirements described in broad strokes.
Non-functional requirements described in broad strokes.
Business needs described in broad strokes.
Deliverables, methodology, team roles, risk assessment.
Stakeholder list, team roles, methodology, risk assessment.
Methodology, team roles, deliverables, analysis techniques.
Timing of stakeholder interactions, team roles, stakeholder authority levels, methodology.
Lessons learned (both positive and negative).
Anecdotes about stakeholders, personal information to promote team building.
ERD, UML, ROI, ITIL and BABOK.
Organization standards and policies (OPAs), including document templates, lessons learned databases, and methodologies and processes.
Force field analysis.
Activity, sequence and workflow diagrams.
Solution assessment and validation.
Stakeholders and organizational process assets.
Analogous and parametric.
Top-down and three-point.
Summation and delphi.
Rolling wave and bottom-up.
Horizontal prototyping, Evolutionary prototyping, 'Throw-away' prototyping.
Document analysis and observation.
Does not assess internal components.
Does not have an impact on delivery dates.
Does not show collaboration with other projects.
Does not prevent difficulties in integrating multiple components.
Solution scope, sponsor authority, stakeholder lists.
Requirements planning, solution scope, business need.
Stakeholder list, business need, solution scope.
Organizational assets, domain SME list, enterprise architecture.
Break down scope.
Break down scope and objectives.
Break down functions, processes, or deliverables.
Break down functions and processes.
Determine the most feasible business solution scope.
Set strategy for the organization using techniques such as SWOT analysis (Strengths, Weaknesses, Opportunities, and Threats).
Establish strategic goals.
Decide which option of a feasibility study is the option to implement.
Business case is updated, Project Manager assigned, BA collaborates with PM, BA schedules requirements review meeting.
Prepare the division of work strategy, Prepare the requirements plan.
Assign Project Manager, Prepare the project charter, Schedule the requirements review meeting, Establish the measures of success.
BA begins to plan requirements activities, Conduct Stakeholder Analysis.
Geography, culture, project type, frequency, customer.
Stakeholder analysis, geography, project type, frequency, formality.
Geography, culture, project type, frequency, formality.
Customers, sponsors, stakeholders, domain SME, project team.
Risk aversion, neutrality, conflict.
Risk aversion, neutrality, risk seeking.
Risk aversion, mitigation, assumptions.
Risk aversion, mitigation, avoidance.
Interviewing, team building, planning, coordinating schedules.
Observation, thinking abstractly, deductive reasoning, Intuitive reasoning.
Resolving conflicts, negotiation, escalation, presentation.
Interviewing, facilitating cross-functional sessions, observation.
Allowing an online focus group to include members located remotely while participating by a network connection.
Reaching agreements with stakeholders on what interfaces are needed.
Coordinating the activities used to elicit interface requirements.
Capturing requirements attributes for interfaces.
Here's an interesting quiz for you.