Your SlideShare is downloading. ×
Agile in dbMotion -  Agile Israel 2014
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile in dbMotion - Agile Israel 2014

742

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
742
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Surprise: no major rejections
  • Examples:

    Review blocked items at the beginning of every release meeting.
    Epic owners for cross-team stories
  • Transcript

    • 1. POPULATION HEALTH dbMotion™ | FollowMyHealth™ Roy Emek, May 2014 Agile in dbMotion: A Story of Transformation
    • 2. Copyright © 2014 Population Health | Powered by Allscripts2 Bridge over the Choluteca, Honduras
    • 3. Copyright © 2014 Population Health | Powered by Allscripts3 Hurricane Mitch 1998
    • 4. Copyright © 2014 Population Health | Powered by Allscripts4
    • 5. Copyright © 2014 Population Health | Powered by Allscripts5 Context A 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
    • 6. 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 Context The company
    • 7. 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
    • 8. Copyright © 2014 Population Health | Powered by Allscripts8 Was This a Success? Employee Survey Overall: 88% positive factor
    • 9. Copyright © 2014 Population Health | Powered by Allscripts9 Was this a success? Bug Charts
    • 10. 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
    • 11. 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 Transformation Org. Change to Feature Teams
    • 12. 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
    • 13. Copyright © 2014 Population Health | Powered by Allscripts14 ● Cadence: Every two weeks ● Pick 1-2 items at a time What Worked for Us? Management Retrospectives
    • 14. 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 ○ ...
    • 15. 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)
    • 16. 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
    • 17. Copyright © 2014 Population Health | Powered by Allscripts18 ... we have come to value: Hard Data over Impressions and Intuition What Worked for Us? Data
    • 18. Copyright © 2014 Population Health | Powered by Allscripts20 Thank You

    ×