1. Development constraints: time, process, policies
2. suggest future improvement opportunities
3. The POPIT Model approach: 5W1H
3.1. :information_source: WHAT? a holistic model that outlines the various dimensions within an organisation
3.2. WHERE? identifies the four domains within the organisation
3.2.1. Processes - Key business processes to deliver products & services to customers
3.2.1.1. are they well-defined?
3.2.1.2. is communication good?
3.2.1.3. is there IT support?
3.2.2. :busts_in_silhouette: Organisation - Structure, resources, roles and responsibilities
3.2.2.1. are responsibility clear?
3.2.2.2. how is collaboration?
3.2.2.3. is management effective?
3.2.3. :bust_in_silhouette: People - Staff and resources who carry out the work
3.2.3.1. are they skillful?
3.2.3.2. are they motivated?
3.2.3.3. are they aware of business objectives?
3.2.4. Information & Technology - Hardware systems and software applications that support the organisation's work
3.2.4.1. Information: required for effective work
3.2.4.1.1. Do the staff have the information to conduct their work effectively?
3.2.4.1.2. Are managers able to make decisions based on accurate and timely information?
3.2.4.2. Technology: a medium to drive organization's goal
3.2.4.2.1. Do the systems support the business as required?
3.2.4.2.2. Do they provide information needed to run the organization?
3.3. WHY? its important to understand all the areas that are impacted due to the implementation of strategy or the change programme
3.4. WHO? Stakeholders: Senior Management, Executives and Board of directors, Strategic consultants
3.5. WHEN? In a product development project or change management initiative
3.6. HOW? surveying and interviewing
4. REQUIREMENT ENGINEERING: OVERVIEW
4.1. Functional Requirements
4.1.1. Definition
4.1.1.1. description of the software's explicit behaviors, what it should and shouldn't do.
4.1.1.2. often specific & measurable
4.2. Non-functional Requirements
4.2.1. Definition
4.2.1.1. constraints on the services or functions offered by the software
4.2.1.1.1. Performance, security, availability
4.2.1.1.2. Speed, size, ease of use…
4.2.1.1.3. Applies to the whole software system
4.2.2. Quantity of requirement measurement
4.2.3. Categories of Non-Functional Requirements
5. BUSINESS OBJECTIVES MODEL
5.1. :information_source: The Business Objectives Model allows the stakeholders to identify the value of a project and then to use that value every day to make requirements decisions
5.2. Box and Arrow
5.2.1. - Box: business problem, objective, or product concept
5.2.2. - Arrow: Link between boxes
5.3. Elements of Business Objectives Model
5.3.1. :white_check_mark: Business objective: Measureable target that specifies when the business problem is solved
5.3.2. :desktop_computer: Product concept: Vision of the actual solution that the business chooses to implement in order to meet the business objective It is typically described by a list of high-level features
5.3.3. :white_check_mark: Success metric: A business objective that will actually be measured to determine whether the project is successful, or additional measures that are related to the solution
5.4. Business Problem: Issue preventing the business from achieving its goals
5.5. Developing Business Objectives Model
5.5.1. starts with an intial problem
5.5.2. ...which leads to an objective to solve it
5.5.3. :arrow_right: ....then it may by itself lead to another problem
5.5.3.1. what is preventing us from achieving our objective?
5.5.3.2. how to solve it?
5.5.4. ....or to a solution, that may lead to another problem as well
5.5.5. :os_win: ....then finally, a product concept, or set of solutions that satisfy all the given objectives
5.6. More References
5.6.1. How To Write Business Objectives (With Examples): https://www.indeed.com/career-advice/career-development/business-objective
5.6.2. How to Set, Track, and Achieve Business Objectives with 60 Examples: 60 Examples of Business Objectives | Smartsheet
6. Business Analysis: Overview
6.1. WHY Outsourcing Business Model and the rise of the Business Analyst?
6.1.1. To reduce costs
6.1.1.1. :white_check_mark: find developing countries for outsoucing (India, Vietnam)
6.1.2. Lack of senior IT personnels
6.1.2.1. problems of communication between business and outsource team
6.1.3. Handling of requirements
6.1.3.1. needs professional staff for better and clearer requirements
6.2. Business change lifecycle
6.2.1. Alignment: initial stage
6.2.1.1. :busts_in_silhouette: link an organisation’s strategy to its external environment
6.2.1.2. :warning: A Business Analyst needs to be aware of the external environment and make recommendations for change
6.2.1.3. :pencil2: Eg: A strategy from an Unhappy Bank is to differentiate itself from competitors by offering innovative products and services that cater to the evolving needs of its customers. How to align their digital transformation project into this strategy?
6.2.1.3.1. Review customer feedback to identify areas where a process can be improved
6.2.1.3.2. Conduct market research to identify industry best practices and benchmark against competitors, especially fintechs
6.2.1.3.3. Engage with employees to communicate the proposed change and address any concerns or feedback
6.2.2. Definintion
6.2.2.1. the elements that will support the change are defined
6.2.2.1.1. A high level document was prepared that included Unhappy Bank’s vision
6.2.2.2. Roles of BA
6.2.2.2.1. run a feasibility study and search for options
6.2.2.2.2. manage stakeholders
6.2.2.2.3. perform a gap analysis
6.2.2.2.4. define the requirements
6.2.3. Design
6.2.3.1. develop a design that encompassed new or improved business processes
6.2.3.2. Roles of BA
6.2.3.2.1. defining acceptance criteria for testing
6.2.3.2.2. acting as a liaison between the business and IT teams
6.2.3.2.3. ensuring that the end product aligns with the business needs
6.2.3.3. :star: the Business Analyst helps to ensure that the IT team delivers what the business requires, thus avoiding any potential mismatch between expectations and actual results.
6.2.3.3.1. In other words, when Business wants oranges, IT team will deliver oranges and not lemons.
6.2.4. Implementation
6.2.4.1. The project team with the developers should have a clear tasks to be implemented at this stage
6.2.4.2. Roles of BA
6.2.4.2.1. to ensure that the development tasks are clear by supporting the project team
6.2.4.2.2. to manage change requests that may arise during the implementation phase, ensuring that any changes align with the overall project objectives.
6.2.5. Realisation
6.2.5.1. Once the project is real and the go-live phases have passed, then we needed to ensure that the digital transformation project was successful and had the benefits it was suppose to have.
6.2.5.2. Roles of BA
6.2.5.2.1. perform a post implementation review
6.3. The range of analysis activities
6.3.1. Strategic Analysis and Definition
6.3.1.1. Consultant’s work, often done by seniors & managers
6.3.2. Business Analysis
6.3.2.1. resolve business issues
6.3.2.2. recommend business changes
6.3.2.3. enhance/replace existing IT system to align with business needs
6.3.2.4. domain knowledge
6.3.2.5. stakeholder relationship management
6.3.3. IT system analysis
6.3.3.1. Specification
6.3.3.2. Modelling
6.4. BA's Responsibilities
6.4.1. support the implementation
6.4.1.1. Developing test scenarios for User Acceptance Testing (UAT)
6.4.1.2. Writing user manuals & guides
6.4.1.3. Providing training for new processes & software
6.4.1.4. Defining job roles
6.4.2. core responsibilities
6.4.2.1. Investigate business systems
6.4.2.2. Evaluate actions to improve business operation
6.4.2.3. Document the business requirement
6.4.2.4. Elaborate requirements to be up-to-date with user’s business needs and to make a evolutionary system development
6.4.3. Extended responsibilities (choose 1 to specialize in)
6.4.3.1. Strategy implementation
6.4.3.2. Business case development
6.4.3.2.1. A document that describes the findings from a business analysis study
6.4.3.2.2. recommended course of action for senior management to consider.
6.4.3.3. Benefit realization
6.4.3.3.1. Post-implementation reviews
6.4.3.3.2. Evaluate & report achieved benefits
6.4.3.4. Specification of IT requirements
6.4.3.4.1. Modelling
6.4.3.4.2. UI/UX prototyping