Automated Release Notes - STC19

Slide 1

Slide 1 text

• Michael Winslow • Core Application - Comcast • I’ve automated myself out of 2 jobs before Automated Release Notes @michaelswinslow michaelswinslow #stc19

Slide 2

Slide 2 text

@michaelswinslow

Slide 3

Slide 3 text

+ != @michaelswinslow https://pixabay.com/vectors/ford-mustang-car-racing-car-146580/ https://pixabay.com/photos/bulldog-puppy-dog-pet-sweet-black-1047518/ https://pixabay.com/photos/rug-carpet-woven-handmade-textiles-1088557/

Slide 4

Slide 4 text

+ Dev Ops DevOps != @michaelswinslow

Slide 5

Slide 5 text

YOU FOOL! It’s not about Dev+Ops, it’s about CULTURE! @michaelswinslow

Slide 6

Slide 6 text

Culture Automation Measurement Sharing C A M S Credit: Damon Edwards, John Willis https://itrevolution.com/devops-culture-part-1 @michaelswinslow

Slide 7

Slide 7 text

What’s an example of DevOps, Smart Guy? @michaelswinslow

Slide 8

Slide 8 text

Find something small to AUTOMATE. Then MEASURE, CODE and DELIVER it! @michaelswinslow

Slide 9

Slide 9 text

What to AUTOMATE? @michaelswinslow https://pixabay.com/photos/learn-school-student-mathematics-1996846/

Slide 10

Slide 10 text

HOW TO FIND THINGS TO AUTOMATE • Create a Value Stream Map • Cycle Time = Lead Time + Process Time • Identify things that are blocking the process • Toil (Manual, Highly Repeated Processes) Example

Slide 11

Slide 11 text

HOW TO FIND THINGS TO AUTOMATE Request Received Coding QA Approval Release

Slide 12

Slide 12 text

Change Acceptance Board Software Release Notes Software Release Notes The Change Acceptance Board (CAB) requires release notes with every release to Production They slow things down significantly. @michaelswinslow

Slide 13

Slide 13 text

Measure it! @michaelswinslow

Slide 14

Slide 14 text

developers deployment scrum master 6 hours 3 hours 2 hours • Veracode Scanning Change Acceptance Board • Create Release Notes Page • Create Summary (tickets) • Links to QA Tests • Verify Completeness • Add List of Artifacts • Verify Versioning • Verify Rollback Version • Create MOP Software Release Notes Software Release Notes 9 People 11 Hours @michaelswinslow

Slide 15

Slide 15 text

Is there a better way? @michaelswinslow

Slide 16

Slide 16 text

Code it! @michaelswinslow

Slide 17

Slide 17 text

<1 minute < 1 minute < 1 minute • Veracode Scanning Change Acceptance Board • Create Release Notes Page • Create Summary (tickets) • Links to QA Tests • Verify Completeness • Add List of Artifacts • Verify Versioning • Verify Rollback Version • Create MOP Software Release Notes Software Release Notes 0 People ~1 minute @michaelswinslow

Slide 18

Slide 18 text

IMPORTANT: Choose tools that can be extended

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Deliver it! @michaelswinslow

Slide 21

Slide 21 text

@michaelswinslow

Slide 22

Slide 22 text

@michaelswinslow

Slide 23

Slide 23 text

Now it’s FAST What about the QUALITY? @michaelswinslow

Slide 24

Slide 24 text

scrum master 1 hour Change Acceptance Board • Create Release Notes Page • Create Summary (tickets) • Links to QA Tests • Verify Completeness Software Release Notes 1.0 1.1 1.1 @michaelswinslow

Slide 25

Slide 25 text

scrum master 1 hour Change Acceptance Board • Create Release Notes Page • Create Summary (tickets) • Links to QA Tests • Verify Completeness Software Release Notes 1.0 1.1 1.1 Pre and Post Release States Identical @michaelswinslow

Slide 26

Slide 26 text

developers deployment scrum master 6 hours 3 hours 1 hour • Veracode Scanning Change Acceptance Board • Create Release Notes Page • Create Summary (tickets) • Links to QA Tests • Verify Completeness • Add List of Artifacts • Verify Versioning • Verify Rollback Version • Create MOP Software Release Notes 1.1 1.1 Human Errors @michaelswinslow

Slide 27

Slide 27 text

The Generated Release Notes @michaelswinslow

Slide 28

Slide 28 text

@michaelswinslow

Slide 29

Slide 29 text

@michaelswinslow

Slide 30

Slide 30 text

@michaelswinslow

Slide 31

Slide 31 text

@michaelswinslow

Slide 32

Slide 32 text

@michaelswinslow

Slide 33

Slide 33 text

@michaelswinslow

Slide 34

Slide 34 text

@michaelswinslow

Slide 35

Slide 35 text

@michaelswinslow

Slide 36

Slide 36 text

RESULTS • Over 4900 man hours saved (as of 5/4/2019) • Note: there are 2080 work hours in a year (40 hours x 52 weeks) But even better: • Release Management TRUSTS the validity of the Release Notes • Security BELIEVES that security scans are always performed • QA COORDINATES with the development teams • Technical Writing BUILDS these into public facing Release Notes • Senior Leadership INVESTS in automation (tools + development) …and that is CULTURE. @michaelswinslow

Slide 37

Slide 37 text

YOU WONDERFUL COLLEAGUE! We just scored a big win for DEVSECOPS! @michaelswinslow

Slide 38

Slide 38 text

•Thank You! Automated Release Notes @michaelswinslow michaelswinslow