This phase is designed to understand an organisations current state across their people, processes, and technology, to define a future state business and architecture view to meet business requirements and establish an implementation roadmap. The road map items will align to the Discovery and Implement phases of the Solution Delivery Method.

This Strategy phase is optional as not all business initiatives that require a solution to be delivered will be created from a well-defined strategy, or a client may have a pre-existing strategy or road map.

This phase captures the solution requirements, creates the architecture runway, defines the technical design, determines the testing approach and establishes an executable plan for implementation.

Typical delivery from this phase includes:

• A requirement backlog captured as a set of Features, Epics and User Stories.
• A Solution Architecture definition - this can be based off the standard RDS template or clients can choose to use their own template(s)
• A Change Management Strategy to enable the acceptance of the solution within the organisation.
• A Test Strategy to ensure the functional and non-functional elements of the solution are fit for purpose.
• An Implementation Estimate using a bottom estimation approach based on the requirements backlog and associated architecture definition. Estimates are generated using RDS's Implementation Estimation Tool.
• A Project Approach and Project Plan to deliver the project.
• A Business Case or Funding Request to secure the Implementation Phase project funding.

Similar to the Strategy Phase, not all deliverables may be required.

This phase focuses on delivering outcomes through a series of contained iterations and close collaboration with key stakeholders. Each iteration contains 5 stages;

• Define: create the backlog for an implementation project and represent the backlog grooming process required at the beginning of each iteration.
• Build: represent the build tasks of an iteration, containing development, configuration, and infrastructure tasks.
• Test: integration and user acceptance testing of the backlog items built in the iteration.
• Showcase: demonstrate the deliverables completed and tested in the iteration to ensure alignment with stakeholder expectations.
• Release: release of completed and business accepted feature capability to a targeted environment in the system landscape.

This phase covers post-production deployment, warranty and optional ongoing support services including improvement and issues management. Additionally, user training and change management can be included in this phase. In delivering these services for LSSA, we support their contractual obligations to the South Australian Government, which are based in ITIL Service Management processes. This phase is adapted to meet specific client requirements and generate outputs and artefacts required.

The Framework specifies the stages of a project, the processes that are undertaken for each stage and the products that can be produced. The Framework can be tailored for individual projects and is ISO9001 and ISO27001 certified. The Framework has been developed using the latest PRINCE2 Agile methodology released in 2018, blending in PRINCE2 Project Management with an agile approach to product delivery.

The RDS Team hold PMP and Prince2 Practitioner certifications in traditional project management methodologies. We also have an extensive history of Agile project execution, with staff holding Certified Scrum Master, PMI Agile Certified Practitioner, ITIL 4 Foundation and Prince2 Agile certifications.

Identifying who key stakeholders are for the given project and determining their responsibility for and attitudes towards the projects.

Focuses on the targeted, appropriate involvement for all stakeholders at various levels early and is often used to enable buy-in and ownership. This activity involves the definition of a Communication Plan that defines the engagement activities to be undertaken and the appropriate channels for delivery.

Focuses on ensuring the business is prepared to own and accept the change organisationally, behaviourally, functionally, and technically.

Focuses on overall sustainability of the change through knowledge transfer and client capability development (where required) including the execution of staff enabling processes, while tracking benefits realisation where required.

• The use of JUnit and related toolsets, such as Mockito, for the authorising of automated unit tests. For many applications, a suite of such tests is constructed, and then built into the CI/CD pipeline using Jenkins and SonarQube.
• The use of JMeter for performance and load testing, particularly on performance-sensitive areas of functionality.
• The use of Postman for API testing.
• The user of Zephyr and JIRA for the tracking of test runs and test results, and the management of test suites.