AWS re:Invent 2016: How A Federal Agency Transformed Work and Adopted DevOps with GitHub (DEV204)

Post on 08-Jan-2017

124 views 0 download

Transcript of AWS re:Invent 2016: How A Federal Agency Transformed Work and Adopted DevOps with GitHub (DEV204)

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Natalie Bradley

DevOps Lead

Accenture Federal Services

Matthew McCullough

Director of Field Services

GitHub

@matthewmccullough

How A Federal Agency

Implemented DevOps with GitHub

Natalie BradleyDevOps Lead

Accenture Federal Services

Matthew

McCulloughDirector of Field Services

GitHub

How A Federal Agency Implemented

DevOps with GitHub

Let’s set the stage

Product &

Platform

Journey to

DevOps

Takeaways &

Next Steps

1 2 3

The Platform1

GitHub is how people build

software

GitHub Enterprise on AWS

• Cloud

• Performance improvement

• User ease

DevOps at a government

agency

Transform the way that

an agency does work

from a DevOps

perspective.

The Journey2

Initial assessments

Different starting points

& different velocities

Maturity model:

Everyone starts where they

are

“We never mandated it,

and they flocked to it”

Tools that enable the

journey

“Core DevOps

functionality”

Next Level:

Security

Roll out and timeline:

Quantify, set goals and don’t

overwhelm

Cultural transformation:

Behavior change

What did adoption look

like?

0

40

80

120

160

200

0

550

1100

1650

2200

Oct-15 Nov-15 Dec-15 Jan-16 Feb-16 Mar-16 Apr-16 May-16 Jun-16 Jul-16 Aug-16 Sep-16

Jenkins Programs GitHub Users

Concluding Thoughts3

Tools and

software development

patterns

What’s next?

In sum:Start with the platform

Run a capabilities assessment

Define a simple maturity model

Accept widely varied initial competencies

Create safe spaces for user experimentation

Educate and incentivize rather than mandate

Quantify adoption goals and broadcast progress

Q&A

Thank you!

Natalie Bradley

&

@matthewmccullough

Remember to complete

your evaluations!