• No results found

The Agile Software Factory

N/A
N/A
Protected

Academic year: 2021

Share "The Agile Software Factory"

Copied!
31
0
0

Loading.... (view fulltext now)

Full text

(1)

The Agile Software

Factory

Horizon Next Generation

Horizon Next Generation

Development Program

John Flenley, Vice President SITA Inc

(2)

“We don’t deliver garbage”

(3)

Who are SITA?

• Société Internationale de Télécommunications Aéronautiques

• Created and owned by the air transport community

• SITA is one of the world's leading specialists in air transport communications and IT solutions

• We deliver and manage IT solutions for airlines, airports, global

• We deliver and manage IT solutions for airlines, airports, global distribution systems and governments.

• Almost every airline and airport in the world does business with SITA

• SITA works collaboratively with the air transport industry and the industry itself drives the company's portfolio and strategic direction

(4)

Horizon Portfolio Overview

A c c e s s

E-Commerce Mobile Kiosk Agent / corporate direct Airline agent desktop Partner & GDS distribution P ri c in g

Analyse Manage Distribute

Total Fares Management

Price Shop

Direct Sales and Service

Fast and accurate control of fares S e rv ic e s

Profile & Loyalty Payments Ancillary Sales Intelligence

P S S C o re Inventory & RM

Reservations DCS W&B Ticketing

Flexible, efficient Passenger Service Systems core moved off legacy

Shared services for all channels and

(5)

Scope of the Next Generation PSS Program

Functions redeveloped in the current NG PSS programme

Existing open modules Integrated into NG design

PSS related touchpoints T o u c h p o in ts P ri m a ry R e ta il in g GDS & Online agent GDS & Online agent Partner & Alliance Partner & Alliance Call centre Call centre 3rd party Apps 3rd party Apps Desktop eCommerce Desktop eCommerce Mobile portal Mobile portal Social media Social

media KioskKiosk

Agent & Corporate direct Agent & Corporate direct Mobile agents Mobile agents Cabin in-flight Cabin in-flight Check-in Boarding Check-in Boarding N G P S S a d m in is tr a tio n N G P S S a d m in is tr a tio n Pricing control Price, re-price, refund Flight shopping Merchandising Merchandising Payment services Payment services Marketplace Service catalogue & fees

Merchandising engine

Integration platform and enterprise service bus Integration platform and enterprise service bus

P ri m a ry s e rv ic e s R e la te d f u n c ti o n s N G P S S a d m in is tr a tio n N G P S S a d m in is tr a tio n Revenue management Revenue integrity Revenue accounting Loyalty Business intelligence Fulfillment eTicket, EMD Fulfillment eTicket, EMD Inventory & schedules Inventory & schedules Reservations Reservations Departure

check-in & boarding

Departure

check-in & boarding

Weight & Balance Weight & Balance

D

a

ta Customer journeys

Customer

profiles Seat data

Pricing/ Pricing/ fee data

Inventory data Schedule data Reference data

(6)

Horizon Next Gen Program – Size

Program estimation and sizing through formal analytics

methodologies

5 year program with $155m development budget

100,000 Function Points (FP) in total for scope

Other Development Programs Function Point Counts * Other Development Programs Function Point Counts *

US Air Traffic Control Microsoft XP

Microsoft Office Professional Airline Reservation System NASA Space Shuttle

Google Search Engine Travelocity

FEDEX Shipping Controls Denver Airport Luggage

306,000 127,000 93,000 38,000 23,000 19,000 19,000 17,000 17,000

(7)

Change Program:

A New Process

(8)

Why we needed to change

Change drivers: by Year 3 we were over spent and

under delivered

• 50% budget spent and approximately 25% scope completed

• Delivery delays

• Technical debt build-up

• Quality issues

Change vision: we needed to be faster, on time, on budget

• Project acceleration to get back to 5 year plan

• Finite scope

• Engaged with 3 off-shore partners under same governance, responsible for development and testing prior to SITA acceptance testing

(9)

Why we needed to change

Change the process: a new way of working was needed

• Iterative large scale software delivery based on Agile

• Deliver functional integrated and performance tested solutions each iteration

• Continuous software build and integration

• SITA Quality Assurance for governance and validation

• SITA Quality Assurance for governance and validation

Change the plan: unify & simplify

• All Horizon Next Gen staff “reunited” with the Business and Software Development organisations

• Full-time SITA Integration Team

• Technical debt elimination

(10)

Distributed Organization

ARN – Copenhagen ATL – Atlanta BLR – Bangalore DEL – Delhi KBP – Kiev

KUL – Kuala Lumpur LED – St Petersburg LKY – Letterkenny LON – London OMS – Omsk All Software ATL: Supplier ARN: Supplier LON/KUL: Supplier ATL: Supplier LON: SITA ATL: SITA YVR: SITA All Software Development SITA QC SITA Business Line SITA Data Centre 3rdparty suppliers BLR: Off-shore partner DEL: Off-shore partner

DEL: Off-shore partner

KBP: Off-shore partner

OMS: Off-shore partner

LED: Off-shore partner LON: SITA

(11)

• Define and agree on common Definition of Done (DoD)

• Deliver working “shrink-wrapped” software out of the

Factory at each sprint as per agreed upon DoD

Program Delivery: Key Principles

Factory at each sprint as per agreed upon DoD

• Empower cross-functional teams to make decisions

collaboratively and proactively, take ownership and commit

to deliver working software at the end of each sprint

• Plan and execute software delivery iteratively

• Build, integrate and test continuously

(12)

The Estimation Process

1. Program Scope (Use Cases) / Analytics Criteria* Program Sizing

(Function Points*)

2. Program Sizing (FP*) / Productivity (hrs/FP*) Total Effort (hours)

3. Total Effort (hrs) / Forecast Completion Date Overall Resource

Capacity Plan

3. Total Effort (hrs) / Forecast Completion Date

Capacity Plan

4. Resource Capacity Plan / Prioritized Use Cases Stage Scope (Use Cases)

5. Stage Scope (Use Cases) / Prioritized Use Cases Sprint Scope (Use Cases)

(13)

Program Delivery: Resources

Partnerships with 3 off-shore suppliers

Agile methodology and principles Overall geographical distribution 3 theoretical scenarios based on

Software delivery strategy and plan defined from:

% T o ta l s c o p e 20.0% 25.0% 30.0%

Scenario 1 3 theoretical scenarios based on

risk management (scope vs. delivery process)

SITA’s capacity to produce Use Cases and Design Artifacts iteratively

Off-shore suppliers resourcing capacity and ability to produce software iteratively

13 © SITA INC UK Limited 2012. All rights reserved.

% T o ta l s c o p e 0.0% 5.0% 10.0% 15.0% 1 2 3 4 5 6 Scenario 1 Scenario 2 Scenario 3 Stages

(14)

Example Capacity Planning (1 Module)

10.0 12.0 14.0 16.0 18.0 # S cr u m T e a m s

S&S - Capacity Planning - Scenarios & Baseline Forecast

Scenario 1 0.0 2.0 4.0 6.0 8.0 10.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 # S cr u m T e a m s Scenario 2 Scenario 3 Baseline Forecast

(15)

Change Program:

(16)

End-to-End Delivery Process

Off-shore Supplier 2 Off-shore Supplier 2 Off-shore Supplier 1 Off-shore Supplier 1 Quality

Quality Business Line

(PSL, GSL) Business Line (PSL, GSL) Architects Architects SMEs BAs/BCs SMEs BAs/BCs SW Support & Off-shore Supplier 3 Off-shore Supplier 3 Continuous Integration Continuous Integration SW Support & Maintenance Quality Quality 1 2 3 4 6 7 Requirements documented Requirements & High Level Design completed Software delivered passes Factory Acceptance Test Software built and deployed Acceptance, Integration and Performance Tests Software Delivered for Demos / User Acceptance Test Software Delivered for Production 5 Supplier 3 Supplier 3

(17)

How did it work: Team Structures

• Plan the stages and iterations of the development program • Provide Subject Matter Expertise

• Feed off-shore factory with backlog of requirements and high-level design specifications

• Interface with Off-shore Core Team

• Trust teams to self organise and deliver on commitment • Manage teams not people (contracts are for teams)

SITA Cross-Functional Team (XFT)

Senior Delivery Managers, Project Managers, SMEs, Architects,

Business Analysts, Testing and Continuous Integration

• Manage supply chain (input/output analysis and prioritisation) • Manage Scrum Teams (number and work allocation)

• Protect Scrum Teams from involvement in day-to-day management

Off-shore Core Team (OCT)

Program & Project Management, Chief Scrum Master, Proxy Product

17 © SITA INC UK Limited 2012. All rights reserved.

• Protect Scrum Teams from involvement in day-to-day management • Core team roles and responsibilities aligned to functional domains • Chief Scrum Master has full view of all Scrum Teams

• NFR Test Team do non-functional testing at module level

Chief Scrum Master, Proxy Product Ownership, Technical Management,

Technical Leadership, QA Management, Configuration Management, Integration/NFR Testing

• Each Scrum Master manages two teams, each BA supports two teams • Scrum Teams focus on development and functional testing

• Hold daily Scrum Team meetings which feed into Scrum of Scrums • Output is continuously integrated and tested until ready for final

verification and end-to-end testing

Scrum Teams 50% Scrum Master 50% Business Analyst 1 Technical Lead 5 Developers 2 Testers

(18)

Governance through Metrics

Daily Metrics

• Use case burn down

• Automated Coding standards

checking

• Automated Unit

Sprint Metrics (trends)

• Automated unit test coverage • Frequency of

builds and runs of automated test suites

Checklist of Agile documentation

• Produced by OCT and monitored and approved by SITA QA including test plan, design and test exit reports

Product Release • Defects found in Acceptance Integration or Performance: Categorised into Severity1-5s • Total defects per • Automated Unit Test results • Test case execution, passed against planned • Defects • Use cases

planned for Sprint compared to number done • Manual functional test coverage (GUI) • Automated functional and non-functional test coverage

• Total defects per function point and KLOC

• Requirements coverage by test cases executed

(19)

Communication

• Weekly webinars with XFT and OCT plus weekly forums for ad-hoc

matters

• SITA Delivery Management Team completed 6-8 site visits per year to each vendor

19 © SITA INC UK Limited 2012. All rights reserved.

• Webinars and video-conferences for stage planning, reviews and

retrospectives

• Webinars and video-conferences for each sprint review including

demonstrations of working software

• All documentation shared in one repository

• OCT feedback the output of daily stand-ups, scrums and “scrum of scrums” to XFT via reporting of standard metrics and processes

• Multi-vendor OCT Integration meetings twice per week

Key OCT resources based on-shore alongside XFT

(20)

Software Delivery Framework

Elaboration Acceptance, Integration, Performance Planning Development
(21)

A Stage In Detail

Copyright © SITA Information Networking Computing UK Limited 2012. Confidential. All rights reserved.

21

Copyright © SITA Information Networking Computing UK Limited 2012. Confidential. All rights reserved.

(22)
(23)

Acceptance, Integration and Performance

• AIP is run as sprints and match those of development. Sprint test execution is planned according to suppliers sprint backlog and quality control is one sprint behind development

• Functional automation concentrates on services for inter-operability with other SITA products

• Severity 1-2s are patched from development during the sprint; Severity 3-5s fixed in any agreed sprint for that release

fixed in any agreed sprint for that release

• Test cases are linked to requirements matrix to ensure full coverage or expose gaps

• Sprint summary report is provided for progress on acceptance, integration and meeting performance required for user stories

• Release exit report issued by SITA Test Manager

(24)

AIP Acceptance Criteria

Criteria for entry into AIP

• No known Sev 1s or 2s outstanding on functionality for test

• Maximum 15% of Sev 3s outstanding on functionality handed over (or no more than

0.15 severity 3’s per function point and no more than 0.26 severity 3-5s per function point)

• 100% of planned test cases for functionality have been executed and 80% of planned test

cases have passed

• Coding standards met and signed off

• Open defects per function point and KLOC against agreed threshold

Criteria for exit of AIP

• No known Sev 1s or 2s outstanding on stories/functionality

• No more than 0.15 severity 3’s per function point and no more than 0.26 severity 3-5s

per function point

• 100% of planned test cases for user story/functionality have been executed

• 100% of functional requirements coverage by test cases

• Performance requirements are met

(25)

What were the problems?

Excessive Rework

Inability to feed factory with volume

Quality of those artefacts

25 © SITA INC UK Limited 2012. All rights reserved.

External dependencies

Missing dependencies

(26)

Agile Factory Model: Vendor view

Initial Concerns

• Fixed price contract for Agile projects

• Sizing based on function points

• Expected high productivity (<16 hours per function point)

• High-level of testing coverage (100% of all

Outcome

• Time and material contract with service credits

• Function points are now the norm

• Achieved 15-16 hours per function point (80% development life cycle)

• High-level of automated testing coverage • High-level of testing coverage (100% of all

functionality, >80% of all business logic)

• Continuous parallel functional, integration and performance testing as per Agile vs. after development as per Waterfall

• Continuous integration for modules developed by off-shore partners

• High-level of automated testing coverage (100% of all functionality, >80% of all business logic)

• Development and functional testing performed in parallel resulted in 40% less defects and defects found by SITA Quality post

development, reduced from 70% to 15%

• Continuous integration, essential due to high number of scrum teams working in parallel, ensured consistent processes and practices

(27)

Program Achievements

Output and productivity increased from 0.8% total program FPs per month, to 5% total program FPs per month.

• 29,000 FPs delivered in 12 months - as much as was achieved in the previous 3 years using Waterfall methodology

Average cost per FP reduced from $2650 to $1100 currently, with a final target of $1,000

final target of $1,000

Quality increased from 0.47 defects per FP to 0.29 defects per FP • Defects found by off-shore suppliers (rather than SITA) increased

from 30-50% to >85%

• 85% of the inherited technical debt absorbed at no additional cost

(effort equivalent to the development of 1,700 FPs)

(28)

Summary

Finite scope and accurate sizing

Clearly define and agree on the Definition Of Done

Plan scope of work and resources ahead and iteratively

Empower team to self-manage

and take ownership

Identical vendor structure, governance and timings

Improve continuously

through measuring and lessons learned

Quality deliverables by discovering and

fixing problems early

(29)

Delegation

works

Self-managing teams

works

Common governance

works

Continuous improvement

works

Bottom-up management

works

Continuous integration

works

Simple structure

works

Agile

works

(30)

SITA Panel

• Aveek Dasgupta: Estimation and Analytics Specialist

• Patrick Holden: Program Director

• Declan Holmes: Director Delivery, Integration &

Maintenance

(31)

THANK YOU

John Flenley Vice President, Software Development [email protected] www.sita.aero

References

Related documents

According to the analysis of energy weighting method, fault frequency and the resonances have been enhanced by multi-scale binary spectrum and converted to time domain

Data does not allow a comparison of Scotland’s sectoral performance with other international countries 7 , but as its sector mix is very similar to that of the UK, it is

Droumaguet, Matthieu 2012, Markov-Switching Vector Autoregressive Models: Monte Carlo experiment, impulse response analysis, and Granger-Causal analysis European University

“Absorption and fluorescence spectra of the neutral and anionic green fluorescent protein chromophore: Franck-Condon simulation” Chemical Physics Letters 2012 , 541 ,

It problematises the notion 'traditional', which leads to a better understanding of how indigenous content functions in peace research, for example by exploring

14 example Impact of policy measure s on youth inclusion 15 Trends in the way selected policy measure s influence unemplo yed young people 16 1 Bridgebui lding to

Source: Statistics for Wales, Fuel Poverty Estimates for Wales: 2018, (29 August 2019, SB 34/2019) and Local Government Data Unit Wales, Living in Wales 2008 Fuel Poverty

The multiple correspondence factorial analysis (MFCA) determined that longitude, three climatic variables (i.e. mean annual rainfall, summer humidity index, and frost-free period)