How to release in enterprise and not to go crazy

Dmytro Chernov, Odessa, 2015

Disclaimer (no silver bullet)

AboutDmytro ChernovHP QA Team Leader• 2+ in software development• 10+ in commerce/tech management• 20+ in IT

dmitry.chernoffua.linkedin.com/in/dmytrochernov

Agenda

•What’s enterprise software?• Process• Planning• Status• Automation• Integration• De-scope or postpone• Release

EAS - Theory“EAS is purpose-designed computer software used to satisfy the needs of an organization rather than individual users”

Wikipedia

EAS - Reality

Process

Enterprise Agile• Feature• Backlog Item (BLI)• Backlog status (Draft, In progress, Done) • Milestone• Iteration• Dev team• QA team

Planning of the new release

Status

Automation

If your automation doesn't meet at least one of the point – there is no need for it!

• Reducing test cycle time• Improving reliability of the testing• Increasing product quality• Improving test coverage• Finding bugs• No requires tons of time for

maintenance

Integration

De-Scope or postpone

2014-12-242015-01-222015-02-202015-03-212015-04-192015-05-180

200

400

600

800

1000

1200

1400

Left Work DaysLinear PlanLe

ft Da

ys

2014-12-01 2014-12-302015-01-282015-02-262015-03-27 2015-04-250

200

400

600

800

1000

1200

1400

BLIs WIPDraft VolumeScoped VolumeIn Development VolumeImplemented VolumeIn Testing VolumeTested VolumeDone Volume

Wor

k Pr

ogre

ss (

Day

s)

Burndown

Release

Retrospective (postmortem)

The End…

Thank you!