JD- Business Analyst

The customer is transitioning into a new operating model through a two-phase integration approach.

Phase 1 focuses on service continuity through an interim operating model. Staff will remain on their existing customer-managed devices and networks while being onboarded to the new environment, with access to Microsoft 365 and selected corporate systems. The customer will continue using its existing technology environment and business systems to support ongoing operations.

Phase 2 will establish a longer-term integrated technology and operating model. To support this, a detailed understanding of the customer's technology landscape is required, including its systems, infrastructure, networks, applications, data, and security services. This assessment will inform future integration activities and the development of a target-state architecture.

Key Deliverables

The engagement includes, but is not limited to, the following key deliverables.

Note: Dates detailed in the deliverable schedule are subject to change upon written agreement from the department's Program Management.

Deliverable

Timing

Business Workshop Material

Material required to enable and facilitate stakeholder discussions, knowledge sharing, and decision-making. It will contain a workshop agenda, presentation slides, workbooks, and supporting reference materials.

The workshops are conducted depending on the complexity of the topics being covered and the business objectives. Workshops will typically last between 1 to 4 hours. Post workshop actions, including summarising takeaways and tracking action items, to be completed within 1–2 days after the session.

Business Process Flows

The flows will include visual representations mapping out key business processes, showing the sequence of steps, decision points, and interactions.



These flows are designed to provide a clear and standardised view of how processes function, and support process improvements.

The Business Process Flows typically take 4–6 weeks to complete depending on the complexity of the processes, and 1–2 weeks for validation and finalisation with stakeholder approval.

User Stories

Document functional and non-functional story description, acceptance criteria, and priority. If needed include design mock-ups.

A user story to be completed before backlog refinement and approved by the product owner just after the sprint planning within each sprint.

Business Requirement Definition

Captures the objectives, desired outcomes, and functional and non-functional requirements that must be met. It will be the foundation for project planning, guiding development, testing, and ensuring alignment with business goals.

The Business Requirement Definition to be reviewed with relevant stakeholders, including subject matter experts, and technical teams. Finalisation to occur with the department’s Program Management.

Functional Design(s) specification

Describes the complete solution as per acceptance criteria of the user stories included for the application. This may include business process flows and interactions with 3rd party systems.

The Functional Design(s) specification to be created during sprint planning, after requirements are gathered, and before development starts.



It is continuously updated throughout the project to reflect evolving requirements and functionality.

Data and Security classification

Provides information on the data sets used in the solution and their security classification. It includes procedures for handling, storing, and disposing of data, as well as compliance requirements.

The Data and Security classification to be defined early in the project during the planning phase, before data is created, accessed, or processed. It is to be reviewed and updated periodically throughout the project.

Requirement Traceability Matrix

Captures the link between functional requirements and Test Cases developed for the project.

The Requirement Traceability Matrix to be created after requirements are finalised and before test case design begins. It is to be updated throughout the testing phase to ensure all requirements are covered to confirm that all requirements have been successfully validated.

Document Epics, Features, User Stories in DevOps

Describe high level functionalities including non-functional requirements in agreement with Business stakeholders.

In a sprint, User Stories are written in 1–3 days, ensuring they are transparent, actionable, and include acceptance criteria.

System Integration Specifications

The technical requirements for integrating various systems within a project. It includes detailed descriptions of data flows, interfaces, system dependencies, and defines the integration points.

The System Integration Specification to be prepared during design phase, reviewed and finalised before the Build. It includes gathering requirements and understanding system dependencies, and 2–4 weeks for drafting the integration details, review and validation with stakeholders. The timeline may vary depending on system complexity.

📌 Business Analyst (Melbourne)
🏢 Wipro APAC
📍 Melbourne