Multi-supplier Development with Magnolia - quatico.com3415c627-878e-4652-afc2... · Magnolia User Conference June 9, 2016 Michael Aemisegger Jan Wloka Quatico Solutions AG Multi-supplier

Magnolia User Conference June 9, 2016

Michael AemiseggerJan Wloka

Quatico Solutions AG

Multi-supplierDevelopment with

Magnolia

Magnolia User Conference June 9, 2016 2

Quatico SolutionsCrafting SoftwareA small software engineering shop in Zurich.

We build tailored web applications often with non-trivialserver logic and digitalize business.

Our aim is to deliver very good results not just becauseour customers demand it, but because we’re craftsmen,and we are proud of the results of our work.

www.quatico.com

Magnolia User Conference June 9, 2016 3

• Scale with business demands

• General company policy

• Need for specialized suppliers

• Extend your development team

Why multiple suppliers?

Magnolia User Conference June 9, 2016 4

• Team talks and coordinate every week

• Testing after integration of binaries

• Test - Bugfix cycle may take weeks

• Client responsibilities

• Integrate binaries

• Manual testing of releases

A common approach:Develop off-site,

Integrate, deploy and test on-site.

Magnolia User Conference June 9, 2016 5

• Delayed discovery of conflicts

• Bugs found by end-to-end tests

• High management efforts

• Unsatisfying progress & quality

• Higher costs than expected

Results are...

Magnolia User Conference June 9, 2016 6

• Results integrated infrequently

• Testing late in process

• No separated responsibilities

• Too many manual tasks

Main reasons...

Magnolia User Conference June 9, 2016 7

• Often not accepted

• Supplier’s development process

• Supplier’s tooling and

infrastructure

• Inefficient and expensive

Another approach:Develop, integrate, deploy and test on-site.

Magnolia User Conference June 9, 2016 8

• Scalable Architecture

• Automated Integration

• Extended Organization

Source Integration StrategyDevelop off-site,

Integrate source and test-on-site

Magnolia User Conference June 9, 2016 9

Scalable Architecture

Magnolia User Conference June 9, 2016 10

• Module Generator

• Fully automated build chain

• Off-site module builds

• On-site integration and release builds

Automated Integration

Magnolia User Conference June 9, 2016 11

• Supplier teams (on-/off-site)

• Individual planning/development

• Implement all layers

• Core Module team

• Release Team (on-site)

• Run CI Infrastructure

• Build releases, inspect results

Extended Organization

Magnolia User Conference June 9, 2016 12

• Separate Release planning

• Cherry picking

• Managed API changes

Orchestrated Releases

Magnolia User Conference June 9, 2016 13

• Clear responsibilities

• Release ownership

• No supplier lock-in

• Speed

What do you gain?

Magnolia User Conference June 9, 2016 14

• Between core and additional suppliers

• Automatically enforced conventions

• Less side effects

• Less blame game

Clear responsibilities

Magnolia User Conference June 9, 2016 15

• Automated gathering of quality metrics and test coverage

• Releases with cherry picked binaries

• Customer decides what is released

Release ownership

Magnolia User Conference June 9, 2016 16

• Little system knowledge needed

• Creative Freedom for suppliers

• Exchange suppliers with little overhead

No supplier lock-in

Magnolia User Conference June 9, 2016 17

• More releases in less time

• Less manual testing

• Faster learning from mistakes

• Respond faster to business

needs

Speed through faster feedback

Magnolia User Conference June 9, 2016 18

The Big Picture

Source Integration StrategyOther strategies

Magnolia User Conference June 9, 2016 19

Thank You.