Tweet
Tweet

Slide 1

Slide 1 text

@rushabh_mehta demo day november 2012

Slide 2

Slide 2 text

the problem • lots of feature development • < 10% release

Slide 3

Slide 3 text

how to prioritize? solve the biggest first ?

Slide 4

Slide 4 text

but • features are dependent • fundamental change requires breakdown of entire structure needs fix

Slide 5

Slide 5 text

and can’t be fixed! shiny new feature

Slide 6

Slide 6 text

lesson • features built in isolation • cannot be retrofitted in a complex software

Slide 7

Slide 7 text

solution Everyday ReleaseTM Brand NEW!

Slide 8

Slide 8 text

approved by experts actually, no... Everyday Release TM

Slide 9

Slide 9 text

philosophy • build something that can be released every day • release something every day small fix Everyday Release TM

Slide 10

Slide 10 text

anatomy of an Everyday ReleaseTM • problem: support ticket needs review • merge support ticket replies into “Communication” Day 1

Slide 11

Slide 11 text

anatomy of an Everyday ReleaseTM • make a reply thread widget in Javascript • add “Rich Text” editing in ticket Day 2

Slide 12

Slide 12 text

anatomy of an Everyday ReleaseTM • extend this to Lead and Contact • add Email Signature and Incoming Email Details Day 3

Slide 13

Slide 13 text

anatomy of an Everyday ReleaseTM • Remove “Profile Settings” page and make the Profile form editable. Day 4

Slide 14

Slide 14 text

shiny new feature the end.