Podcast
Questions and Answers
Identifying stakeholder needs is part of analyzing business processes.
Identifying stakeholder needs is part of analyzing business processes.
True (A)
Requirements gathering includes only documenting existing processes.
Requirements gathering includes only documenting existing processes.
False (B)
The BABOK® methodology is not recognized in international standards for business analysis.
The BABOK® methodology is not recognized in international standards for business analysis.
False (B)
Iterative development is a technique used to refine solutions over time.
Iterative development is a technique used to refine solutions over time.
Signup and view all the answers
Functional requirements outline what a solution should not do.
Functional requirements outline what a solution should not do.
Signup and view all the answers
Stakeholder consultation should only focus on customers and not employees.
Stakeholder consultation should only focus on customers and not employees.
Signup and view all the answers
Using methods like surveys and interviews is essential for gathering requirements.
Using methods like surveys and interviews is essential for gathering requirements.
Signup and view all the answers
Requirements validation is unnecessary once they have been gathered.
Requirements validation is unnecessary once they have been gathered.
Signup and view all the answers
Lean business cases require the ‘approvers’ to be actively involved in the development of the business case.
Lean business cases require the ‘approvers’ to be actively involved in the development of the business case.
Signup and view all the answers
Traditional business cases are constantly updated to reflect progress and lessons learned.
Traditional business cases are constantly updated to reflect progress and lessons learned.
Signup and view all the answers
Lean business cases support constant decision-making based on current market circumstances.
Lean business cases support constant decision-making based on current market circumstances.
Signup and view all the answers
Prototyping and user testing help to obtain feedback quickly and tailor the solution to the stakeholders' needs.
Prototyping and user testing help to obtain feedback quickly and tailor the solution to the stakeholders' needs.
Signup and view all the answers
A Requirements Traceability Matrix (RTM) is used to manage stakeholder consultations only.
A Requirements Traceability Matrix (RTM) is used to manage stakeholder consultations only.
Signup and view all the answers
The first version of a lean business case can be available in three months or more.
The first version of a lean business case can be available in three months or more.
Signup and view all the answers
Portfolio Epics are assessed for their feasibility and added value using a Lean business case and a MVP.
Portfolio Epics are assessed for their feasibility and added value using a Lean business case and a MVP.
Signup and view all the answers
Lean business practices follow a fixed price model.
Lean business practices follow a fixed price model.
Signup and view all the answers
The role of business analysts includes driving change and facilitating collaboration with stakeholders.
The role of business analysts includes driving change and facilitating collaboration with stakeholders.
Signup and view all the answers
Lean business cases are intended to be static and not revisited after implementation.
Lean business cases are intended to be static and not revisited after implementation.
Signup and view all the answers
Comparisons and prioritization are not important in the development of lean business cases.
Comparisons and prioritization are not important in the development of lean business cases.
Signup and view all the answers
Documenting requirements and specifications is not essential in an Agile development process.
Documenting requirements and specifications is not essential in an Agile development process.
Signup and view all the answers
An epic description should include a self-explanatory name and the expected outcome.
An epic description should include a self-explanatory name and the expected outcome.
Signup and view all the answers
Waterfall methodologies are preferred in the development of lean business cases.
Waterfall methodologies are preferred in the development of lean business cases.
Signup and view all the answers
A business service solely focuses on data storage and display.
A business service solely focuses on data storage and display.
Signup and view all the answers
The purpose of the portfolio kanban is only to show the timelines of strategic initiatives.
The purpose of the portfolio kanban is only to show the timelines of strategic initiatives.
Signup and view all the answers
A business analyst's responsibilities do not include making investment decisions.
A business analyst's responsibilities do not include making investment decisions.
Signup and view all the answers
Application services are primarily concerned with specifying what activity should be performed digitally.
Application services are primarily concerned with specifying what activity should be performed digitally.
Signup and view all the answers
Passing at least five of the seven quizzes is a condition to earn a bonus point for the exam.
Passing at least five of the seven quizzes is a condition to earn a bonus point for the exam.
Signup and view all the answers
You can receive a maximum score of 11 for successfully completing all quizzes.
You can receive a maximum score of 11 for successfully completing all quizzes.
Signup and view all the answers
PaaS and SaaS are examples of service orientations that a business analyst should understand.
PaaS and SaaS are examples of service orientations that a business analyst should understand.
Signup and view all the answers
A Business Case should be archived once it is approved.
A Business Case should be archived once it is approved.
Signup and view all the answers
The Lean Business Cases approach does not require an experimental and risk-driven method.
The Lean Business Cases approach does not require an experimental and risk-driven method.
Signup and view all the answers
Requirements are subjective descriptions of conditions that need to be satisfied.
Requirements are subjective descriptions of conditions that need to be satisfied.
Signup and view all the answers
Parallel approaches to design and implementation are utilized when drafting requirements.
Parallel approaches to design and implementation are utilized when drafting requirements.
Signup and view all the answers
Flowcharts and SIPOC are formats commonly used in the business domain.
Flowcharts and SIPOC are formats commonly used in the business domain.
Signup and view all the answers
A Minimal Viable Product (MVP) can be developed using a traditional, linear approach.
A Minimal Viable Product (MVP) can be developed using a traditional, linear approach.
Signup and view all the answers
Business rules do not change quickly in a dynamic environment.
Business rules do not change quickly in a dynamic environment.
Signup and view all the answers
Integrated DEFinition (IDEF) notation is intended for establishing scope in the business domain.
Integrated DEFinition (IDEF) notation is intended for establishing scope in the business domain.
Signup and view all the answers
Business Process Model and Notation (BPMN) is solely used in the information technology domain.
Business Process Model and Notation (BPMN) is solely used in the information technology domain.
Signup and view all the answers
Data Flow diagrams are a type of business model that is often utilized in BPMN.
Data Flow diagrams are a type of business model that is often utilized in BPMN.
Signup and view all the answers
A pricing corridor helps in managing the margin on SKU at both soft and hard floors.
A pricing corridor helps in managing the margin on SKU at both soft and hard floors.
Signup and view all the answers
Approval is required for all quote sizes regardless of IGM levels.
Approval is required for all quote sizes regardless of IGM levels.
Signup and view all the answers
The role of the Marketing Manager (MM) will remain unchanged in the future approval process.
The role of the Marketing Manager (MM) will remain unchanged in the future approval process.
Signup and view all the answers
The output of a process can include reports and documents.
The output of a process can include reports and documents.
Signup and view all the answers
Soft floors in pricing corridors indicate the minimum discount allowed on SKUs.
Soft floors in pricing corridors indicate the minimum discount allowed on SKUs.
Signup and view all the answers
IGM stands for 'Individual Gross Margin' in the context of pricing corridors.
IGM stands for 'Individual Gross Margin' in the context of pricing corridors.
Signup and view all the answers
Service orientation primarily focuses on hardware management.
Service orientation primarily focuses on hardware management.
Signup and view all the answers
A product list is an input in the process of creating price proposals.
A product list is an input in the process of creating price proposals.
Signup and view all the answers
The Customer Sales process does not involve any decision points.
The Customer Sales process does not involve any decision points.
Signup and view all the answers
Market Group and Business Group do not play a role in the approval process.
Market Group and Business Group do not play a role in the approval process.
Signup and view all the answers
Unified Modeling Language (UML) is an industry standard for software modeling.
Unified Modeling Language (UML) is an industry standard for software modeling.
Signup and view all the answers
The pricing corridor matrix only applies to order levels, not SKU levels.
The pricing corridor matrix only applies to order levels, not SKU levels.
Signup and view all the answers
Study Notes
Information Management
- Information management is a subject covering what information management is, its roles and architecture, tooling, design processes, business analysis, requirements management, and products. Topics include AI and Blockchain.
- Guest lecture by Jaap Kooiker and CJIB Strategic consultant.
- Weeks 1-7 cover various aspects of Information Management.
Workshop 6: Design Process: Business Analysis
- This workshop focuses on the design process within business analysis.
Overview: What is Information Management
- Information management is presented in the context of digital transformation.
- Knowledge of business and IT alignment is critical. This includes strategic perspectives, operational processes, and cultural alignment.
- Importance of governance design, roles, and expertise is highlighted.
- The course covers agile and scalable design using Safe methodology.
- An important aspect is Business Architecture, which designs business models, desired services, processes and required information.
How then, to get started?
- The key to achieving the desired goals are business analysis, decision-making, and requirements.
Agenda
- The agenda includes topics like business analysis, decision-making, Lean business case, Requirements, Process design, and Service Orientation.
- There are discussions on EPIC and portfolio management, which are part of the business case.
Business Analysis
- This section outlines the steps in business Analysis, including elicitation, strategy analysis, and requirements analysis and definition.
F.E. a.k.a. Business Analyst
- A chart outlines a business analyst's workflow, starting with incidents, business, first line, and ultimately, business approvals.
Professional Products
- This section describes professional products involved in the work process, with focus areas such as company architecture, design, change & portfolio management, and implementation.
- There are also concepts of bridging the gap between the current and desired situation, particularly concerning digitization, approach, process and information, customer value, and requirements.
Goals of Business Analysis: Standard Steps
- The goal of business analysis is to understand the context and objectives, consult with stakeholders, gather requirements, validate and prioritize, translate to specifications, and implement iterative developments.
- Businesses develop solutions using an international standard, such as BABOK® (Business Analysis Body of Knowledge), often combined with Agile or Design Thinking methodologies.
- Steps include stakeholder consultations, gathering requirements, validating and prioritizing, translating to specifications, as well as iterative development and documentation/communication.
Scope determination
- This is explicitly stated as a key part of gathering requirements
Stakeholder Consultation
- Methods like interviews, workshops, and surveys help understand customer and employee needs.
- Personas and customer journey mapping are also utilized.
- Understanding context and objectives is essential.
- Identifying all relevant stakeholders, including customers, employees, and external parties, and their needs, forms a crucial part.
Functional and Non-functional Requirements
- Understanding functional requirements (system behavior) and non-functional requirements (quality features like speed and usability) is critical.
- Also, the role of business rules (operating policies and restrictions) in defining the solution's scope.
- SMART criteria define concrete and verifiable requirements.
Validation and Prioritization
- Validation involves discussing the requirements with stakeholders to ensure correctness and achievability.
- Prioritization utilizes techniques like MoSCOW (Must have, Should have, Could have, Won't have), or weighted scoring to organize requirements.
Translation to Specifications
- Detailed specifications are created for developers, vendors, or other implementers.
- Tools like use cases, user stories, process models (BPMN), and data flow diagrams aid in clarifying solution function.
Iterative Development
- Agile practices (like Scrum) allow for continuous evaluation and adjustments to meet the needs, based on feedback.
- Prototyping and user testing are part of the process.
Requirements Traceability Matrix (RTM)
- A Requirements Traceability Matrix (RTM) is used to track progress and the implementation of requirements.
Business Analyst Roles
- The roles of business architect, functional engineer, business systems analyst, data analyst, enterprise analyst, management consultant, business consultant, Information Advisor, process analyst, product manager, product owner, requirements engineer, and systems analyst are discussed.
Business Analysis Competency Model
- The model emphasizes proficiency scale, knowledge areas (strategy analysis, requirements lifecycle management, etc.), technical skills, and business skills.
Portfolio Kanban
- Visualize, Manage, and Analyze portfolio backlog, implementing, and doing what is needed, which includes Epics. This process is to deliver value.
EPIC
- Key aspects include selecting self-explanatory names, outlining the expected outcomes, describing products and technical requirements.
- Creating success criteria and user stories are important to break down the bigger goal.
Epic and Feature Refinement
- The flow and processes of Epic and Feature Refinement are highlighted.
- Key concepts include Portfolio Kanban, Portfolio Backlog (Ready Epics), Program Kanban, and Program Backlog (Ready Features).
- The important role of the Epic Owner in the process is explained.
Example of Agreement on Structure
- The focus is on the agreement from a higher level (EPICS) through to smaller tasks and user stories.
Lean Business Case
- A Lean business case purpose and important components are discussed.
- It differs from a traditional business case in its approach and format (typically fewer pages).
Requirements Management
- This section explores various aspects of requirements management.
Requirements
- The course identifies and defines requirements, types of requirements (functional, non-functional, business rules), and the ways of defining requirements (parallel to design, before start of design).
Process Design
- IT processes should be seen as a structure from coarse to fine to maintain an overview. Business logic should be well defined; separate processes and business rules should be detailed.
- Crucial to keep the process overview, work from coarse to fine, and implement continuously and actively.
Process Orientation
- End-to-end processes, breaking processes into steps, mapping processes, and determining organizational aspects of work processes are part of the study.
- This aspect relates to the definition and breakdown of business processes within an organization.
Service Orientation
- Services are expected results, not the internal workings.
- Services should be deliverables, such as light instead of a lamp, or transport instead of a car.
PaaS: Product as a Service
- It's about the use of products as a service, not owning them.
- Customers pay for the service based on their usage and shifting needs.
SaaS: Software as a Service
- Software as a service is described as discrete services rather than monolithic designs.
- It has four properties, including discreet services, user-friendly access, repeatable outcomes, and composability.
Traditional vs. SaaS Software
- A table compares traditional software purchases (one-time) versus SaaS subscription models.
- Traditional software is often site-locked, requiring installation and updates, as well as considerable infrastructure and storage. SaaS programs are usually web based, require access to an internet connection, and are continuously updated without requiring installation or significant user-side infrastructure changes.
Term Business Services
- This section specifies Business Service definition and focus.
Term Application Services
- Application Service is explicitly defined to specify application behavior.
- Focuses on the functions, activities, and data outputted by the service.
Quiz
- Quizzes are designed to cover the material in the class.
- Students need to answer questions correctly to get a potential bonus point on the exam and must complete minimum of five of seven quizzes to receive a bonus point.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
Test your knowledge on business analysis methodologies, including requirements gathering and stakeholder consultation. This quiz covers essential concepts like iterative development, functional requirements, and lean business cases. Evaluate your understanding of how these techniques impact business processes and decision-making.
