agile in dbmotion - agile israel 2014
TRANSCRIPT
POPULATION HEALTHdbMotion™ | FollowMyHealth™
Roy Emek, May 2014
Agile in dbMotion: A Story of Transformation
Copyright © 2014 Population Health | Powered by Allscripts2
Bridge over the Choluteca, Honduras
Copyright © 2014 Population Health | Powered by Allscripts3
Hurricane Mitch1998
Copyright © 2014 Population Health | Powered by Allscripts4
Copyright © 2014 Population Health | Powered by Allscripts5
ContextA Complete Transformation
Before After
Culture Focus on infrastructure
Focus on value
Organization Functional teams: front-end, back-end, DBA, QA
Feature teams
Process Startup-ish “let’s do the best we can and make it happen”
Agile / Kanban
Engineering tooling
ClearCase, 2-4 days for a build
GIT, Jenkins, Continuous Integration
Copyright © 2014 Population Health | Powered by Allscripts6
● The product: sharing and analyzing clinical data
● ~180 employees prior to the acquisition, ~130 of which in Israel
● Most of which are in Beer Sheva
● A few dozen customers, mostly in the US
● March 2013: Acquired by Allscripts for $235M
ContextThe company
Copyright © 2014 Population Health | Powered by Allscripts7
• “Higher quality; When you say you’re going to deliver something, you do” – An Executive, Major Customer
• “Better quality, better predictability” – Business Unit GM
• “We could have never delivered what we did over the last year if it wasn’t for these changes” – A team lead
Was This a Success? Quotes
Copyright © 2014 Population Health | Powered by Allscripts8
Was This a Success? Employee Survey Overall:
88% positive factor
Copyright © 2014 Population Health | Powered by Allscripts9
Was this a success? Bug Charts
Copyright © 2014 Population Health | Powered by Allscripts10
Was this a success? Quality
Bug driven hotfixes
# of customers grew x2.5 during this time
Oct. 2013
April 2013
Oct. 2012
Copyright © 2014 Population Health | Powered by Allscripts12
● A few weeks of discussions at the Director level● Buy-in, Buy-in, Buy-in. And then some more. ● Careful communication
The TransformationOrg. Change to Feature Teams
Copyright © 2014 Population Health | Powered by Allscripts13
● Tooling: Jira and Jira Agile (FKA Greenhopper)● Freedom to the teams
○ Board == Process○ Let the teams control their destiny
The Transformation Kanban
Copyright © 2014 Population Health | Powered by Allscripts14
● Cadence:
Every two weeks
● Pick 1-2 items at a time
What Worked for Us?Management Retrospectives
Copyright © 2014 Population Health | Powered by Allscripts15
● Every two weeks● 2-3 teams at a time● Format:
○ Board structure ○ WIP and WIP limits○ CFD○ Cycle time
What Worked for Us? Ops Reviews
● Lessons○ Board structure○ Story definition○ Card types○ Engineering
enhancements○ Cross-team
dependencies○ ...
Copyright © 2014 Population Health | Powered by Allscripts16
● We allocated 10% of our budget to engineering investment ○ Nothing happened
Automation reviews● Team Leads● Cadence: every three weeks● What did I do, what am I doing now, what do I plan next
→ Accountability, share success stories, share ideas and knowledge,
collaboration
What Worked for Us? Automation Reviews
(Or maybe we just got lucky with timing)
Copyright © 2014 Population Health | Powered by Allscripts17
Goal: Relative story sizing
Problem: ● How many points? ● Well, I think it’s
about 2 weeks for 3 people, so it’s something around 13 points. Maybe 13.5
What worked for us? Estimation Boards
Copyright © 2014 Population Health | Powered by Allscripts18
... we have come to value:
Hard Data over Impressions and Intuition
What Worked for Us? Data
Copyright © 2014 Population Health | Powered by Allscripts20
Thank You