PHÂN TÍCH NGHIỆP VỤ

KINH DOANH

Bài 8:
Chuyển giao yêu cầu

HCM – Nov 1, 2024

11/01/2024 1
 Objectives

Be able to:
 Understand tasks of “Delivering changes”
 Discuss factors affecting the delivery
approach
 Discuss system development lifecyles and
approaches.
 Identify roles in deliverying requirements
 Discuss techniques in planning, analyzing
and documenting the project work

11/01/2024 Trang 2
 AGENDA

1. Remind: Business analysis process

2. Procedure of delivering changes
3. Context
4. Lifecycles
5. Approaches
6. Roles
7. Deliverables
8. techniques
 Business analysis process

Business strategy and objectives

Investigate Consider Analyze Evaluate Define Delivering

requirement
situation perspectives needs options s changes

• uncover issues • analyze • identify where • examine the • gather and • Consider how
and problems stakeholders improvements potential document the
and their can be made to improvements the detailed requirements
perspectives on the business identified so far, are to be
the situation system develop some requirements delivered, the
• gap analysis: business options for changes changes
‘as is’ view vs and evaluate to the implemented
‘to be’ system them for business and the
•  Define how acceptability system business
the new and feasibility benefits realized
processes
should look

11/01/2024 Trang 4
 Delivering changes

 Objectives: consider how:

 the requirements are to be delivered
 the changes implemented
 the business benefits realised.

11/01/2024 Trang 5
 Delivering changes

 Procedure
1.Follow the lifecycle and approach adopted
2.Develop the business change solution.
3.Plan the implementation:
– Consider the environment for the change.
– Consider the culture of the organisation.
– Define the learning approach and develop the
required learning materials.
4.Review the predicted benefits.
5.Identify any actions required to realise the
benefits

11/01/2024 Trang 6
 Delivery Requirement Approach

 Consider how requirements will be

delivered.
 The business analysis work could
 Provide a large-scale, broad-scope
business change programme, or
 Be focused on a particular area.
 Delivery Requirement Approach

 As a result, delivering the requirements

could include some or all of:
 Business process change
 People changes
 Changes to organisational
structure
 Changes to IT systems
 Delivery Requirement
Approach

 Factors in deciding the delivery approach

 Delivery Requirement
Approach - Factors

 Context:
 the nature of the organisation and the
project
 provide the basis for deciding how the
solution will be delivered
 Some issues to be considered:
• Organization culture
• Constraints
• Prioritised needs
• And more…
  vary from project to project
 Delivery Requirement
Approach - Factors

 Lifecycle:
 the process adopted for developing and
implementing the solution
 Systems development lifecycle:
 Waterfall
 ‘V’ model
 Extended ‘V’ model
 Incremental delivery
 Boehm’s spiral model/Iterative
 Waterfall Lifecycle

Tasks of Business Analysts:

Support & answer

business-based
queries from the
development
team

assist in the user acceptance

help the business users

 V Model Lifecycle

the derivation of the test criteria shows:

how the acceptance criteria should be
derived from the requirements captured
during the analysis stage
Extended ‘V’ Model Lifecycle
Incremental Delivery Lifecycle
Spiral Model Lifecycle
 Approaches

The approach: determines the methods and standards

to be adopted
Considers 2 key issues:
 Delivery: do we require one delivery of the entire
solution or a phased delivery using incremental
releases?
 Development: there are two key questions to
answer.
• The need to work closely with the business users
during the development of the solution
• whether or not the requirements are clear and
well understood.
 Approaches

The approaches:
 Software development Approaches
 Unified Process
 Agile Approach
 Software package Approach
 Approaches

Unified Process:
 a generic software development process
 It is both an iterative and an incremental
approach
 using UML modelling techniques
 Phases:
• Inception
• Elaboration
• Construction
• Transition
 Unified Process

Source: http://en.wikipedia.org/wiki/Unified_Process
 Approaches

 Agile approach:
 from the Agile Alliance
 Methods: DSDM Atern/Scrum
 provides a framework for developing IT systems
in an iterative and incremental way.
 Adaptive (value-driven) rather than predictive
(plan-driven)
• Focus on meeting business needs
• Requirements change often
• Small number of developers
• daily in-person meetings and close collaboration
 Agile approach

 Agile approach:
 key techniques: evolutionary
prototyping, timeboxing and
prioritisation
 the danger that the emerging prototype
systems are not documented properly 
difficulties in live operation
 Agile - SCRUM

11/01/2024 Trang 23
 Approaches

 Software package approach

 Find commercial off-the-shelf (COTS)
solutions
 Advantages?
 Drawbacks?
 ROLES

 Project manager;
 Business analyst;
 Architect;
 Developer;
 Tester.
 DELIVERABLES

 Vary, depends on:

 the nature of the solution,
 the standards of the organisation
 and the lifecycle and approach adopted
 Can be:
• Business change plan
• Communication plan
• Training approach and materials
• Revised job roles and descriptions
• Post-implementation review document
• Benefits realisation plan
 TECHNIQUES

 A waterfall-based lifecycle requires:

 formal documentation that has been
reviewed and ‘signed off’
 Agile approaches:
 prototypes
 Organizations may have set templates:
 standards for modeling business
processes and IT requirements
 Development tools
 Summarize

 Objectives of “Delivering changes”

 Procedure of “Delivering changes”
 Factors in deciding the delivery approach
 Context
 Lifecycle
 Approach
 Roles
 Deliverables
 Techniques

11/01/2024 Trang 28
PHÂN TÍCH NGHIỆP VỤ
KINH DOANH

11/01/2024 29
 Exercises

11/01/2024 Trang 30