5: 30 Ways for the Agile Business Analyst to Add Value to
• identifying and resolving orphan records
• test migrations
• metrics for source and target systems.
Not only does this reduce the amount of work the
developers need to focus on, it can also provide the team
with initial testing of the proposed data structures in the
developed system, as well as an opportunity to confirm
whether system functions and screen designs work as
expected with populated data.
If there are issues or complexities with the data in the
source system, the Agile business analyst can initiate
discussions with the relevant areas as early as possible to
minimize their impact on ongoing development work.
In most cases, Agile business analysts will not be in a
position to build the data migration applications, but the
analysis work they do can assist the Agile development
team in testing, refining, and fixing these applications
before they are released.
13. Analyzing interface requirements for external systems
Similar to providing assistance on data migration activities,
the Agile business analyst can also assist the Agile
development team in investigating the requirements for
interfacing with external systems, including legacy systems
and third-party solutions. This can include identifying
available fields and formats for interchange, validation
rules, communication protocols, encryption algorithms, and
This is another area where preliminary work done by the
Agile business analyst can help to identify and address risks
to the project before they become substantial issues. It is