Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
ERPNext Open Day November 2012
Search
Rushabh Mehta
November 30, 2012
Programming
0
310
ERPNext Open Day November 2012
Monthly review and moving towards Everyday Release (TM)
Rushabh Mehta
November 30, 2012
Tweet
Share
More Decks by Rushabh Mehta
See All by Rushabh Mehta
ERPNext Open Day February 2013
rmehta
1
220
ERPNext Open Day January 2013
rmehta
1
160
ERPNext 2012 Retrospective
rmehta
2
330
Other Decks in Programming
See All in Programming
MLH State of the League: 2026 Season
theycallmeswift
0
210
Kiroで始めるAI-DLC
kaonash
2
500
Laravel Boost 超入門
fire_arlo
2
170
rage against annotate_predecessor
junk0612
0
150
AWS発のAIエディタKiroを使ってみた
iriikeita
1
140
HTMLの品質ってなんだっけ? “HTMLクライテリア”の設計と実践
unachang113
0
480
機能追加とリーダー業務の類似性
rinchoku
0
180
CSC305 Summer Lecture 12
javiergs
PRO
0
130
Azure SRE Agentで運用は楽になるのか?
kkamegawa
0
1k
tool ディレクティブを導入してみた感想
sgash708
1
160
オープンセミナー2025@広島LT技術ブログを続けるには
satoshi256kbyte
0
150
Trem on Rails - Prompt Engineering com Ruby
elainenaomi
1
100
Featured
See All Featured
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
139
34k
Intergalactic Javascript Robots from Outer Space
tanoku
272
27k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Navigating Team Friction
lara
189
15k
Making the Leap to Tech Lead
cromwellryan
134
9.5k
StorybookのUI Testing Handbookを読んだ
zakiyama
30
6.1k
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
How GitHub (no longer) Works
holman
315
140k
Imperfection Machines: The Place of Print at Facebook
scottboms
268
13k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.4k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
The Invisible Side of Design
smashingmag
301
51k
Transcript
@rushabh_mehta demo day november 2012
the problem • lots of feature development • < 10%
release
how to prioritize? solve the biggest first ?
but • features are dependent • fundamental change requires breakdown
of entire structure needs fix
and can’t be fixed! shiny new feature
lesson • features built in isolation • cannot be retrofitted
in a complex software
solution Everyday ReleaseTM Brand NEW!
approved by experts actually, no... Everyday Release TM
philosophy • build something that can be released every day
• release something every day small fix Everyday Release TM
anatomy of an Everyday ReleaseTM • problem: support ticket needs
review • merge support ticket replies into “Communication” Day 1
anatomy of an Everyday ReleaseTM • make a reply thread
widget in Javascript • add “Rich Text” editing in ticket Day 2
anatomy of an Everyday ReleaseTM • extend this to Lead
and Contact • add Email Signature and Incoming Email Details Day 3
anatomy of an Everyday ReleaseTM • Remove “Profile Settings” page
and make the Profile form editable. Day 4
shiny new feature the end.