Lean and agile approach

Lean planning approach

Superpartners applies a “Lean” approach to longer term programs of work.

The primary planning horizon is focussed on the immediate planning horizon (six months) in which programs are scheduled to a greater level of detail. Beyond the primary planning horizon, the Program is scheduled, however at a lesser level of detail.

Stage completion dates are base-lined within delivery timeframes (“time window”) to reflect the level of risk and uncertainty associated with such a significant program of work.

Program schedules continuously develop as delivery outcomes are progressively realised and further detailed planning occurs for the next planning horizon.

The Lean Planning Approach is consistent with the Agile Approach.

Agile approach

Superpartners utilises an Agile approach to major projects, such as software development. Agile ensures:

• Transparency of development progress, as incremental packages of working software are progressively released and demonstrated
• Improved team dynamics given that all work will be performed by co-located teams.

The Agile approach starts with a workshop that produces a number of high level statements (“Epics”) that describe the end to end functionality to be delivered.

Once the high level “Epics” have been created, the work is packaged up into release cycles and prioritised. Epics are prioritised and form the basis of the Master Product Backlog.

Teams (“Scrums”) co-locate and usually comprise of the following roles:

• Scrum Master
• Product Owner
• Tech Lead
• Analyst Programmers
• Business Analysts
• Test Analysts

Role based Communities of Practice are set up to facilitate cross scrum understanding of work being performed in order to better enable integration.

The Agile approach to developing software is a test led approach whereby functionality is continuously tested to ensure that it is delivering to the stated user stories and integrating across functional domains.