Adapting Agile in Large Organisations

Post on 16-Jan-2017

37 views 0 download

transcript

IIBA UK Midland Branch Event

Hosted by National Grid

IIBA - Delivering a Large Programme Using an Agile Approach

The Gas National Control Centre (GNCC)

Keeps the NTS balanced between the gas

demands of both industry and domestic

consumers and available suppliers

Ensures safe, secure and controlled

transmission of gas for today and

tomorrow

Matched supply and demand to ensure

safe and secure delivery of Gas to

consumers 3

What Is The Gas Control Suite?

4

iGMS is the legacy system that controls the National Transmission System for

Gas. The iGMS Evolution Programme (iEP) replaced iGMS with the Gas

Control Suite (GCS).

An Agile Approach Was Taken For the

Development of Fusion…

5 5

Fusion

On the whole the Gas Control Suite (GCS) was developed using a traditional

‘Waterfall’ approach.

However, an Agile approach was used to develop a bespoke Oracle Fusion

based application

What Is Fusion?

6

Why Agile For Fusion – Problem

7

Myths Of Agile

Agile means no documentation

Agile means no planning, just do it

Agile only works for

Developers/Software

Agile will fix all our problems

Agile doesn’t need Business

Analysts

Agile will solve world peace

8

Fusion - An Agile Journey

9

Requirements Engaged Business On

UI / UX Development

Agile Development – Practices

Results

11

“Agile software development has

brought the business and project

team into working together as one

team”

Nigel Evans – Lead Product Owner

Accelerated delivery by doing the

“minimum required”

Effective use of business resource time

and re-engaged the business

Built in checks on deliverable quality and

process

Visualisation deepened the business

engagement by ‘Looking Through The

Eyes Of The Customer’

Embedded new ways of working with

greater business engagement

Reduced development time

Users felt that they owned the project

Classic Agile Roles & Responsibilities

12

Team Composition

Scrum Master

Product Owner

Developers

Quality Analyst

No Role For The Business Analyst?

Scrum Team

Product Owner

Developers

Scrum Master

Quality Analyst

Do you need Business Analysts On Agile

Projects?

13

Where Did The BA’s Fit Into This?

14

BA

Product Owner

UI / UX Designer

Developers Scrum Master

Quality Analyst

Business Analysts Filled The

Gaps In The ‘Classic’ Agile

Approach

Maintained Consistency

Throughout

Custodians Of The

Requirements

The ‘Oil In The Machine’

Lessons Learned From Retrospectives

15

Myths Of Agile

Agile means no documentation

Agile means no planning, just do it

Agile only works for

Developers/Software

Agile will fix all our problems

Agile doesn’t need Business

Analysts

Agile will solve world peace

16

17

Myths Of Agile

Agile means no documentation

Agile means no planning, just do it

Agile only works for

Developers/Software

Agile will fix all our problems

Agile doesn’t need Business

Analysts

Agile will solve world peace

18

Q & A

Thank you for attending!

19

Are there any questions?