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
300
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
LT 2025-06-30: プロダクトエンジニアの役割
yamamotok
0
760
XP, Testing and ninja testing
m_seki
3
240
「テストは愚直&&網羅的に書くほどよい」という誤解 / Test Smarter, Not Harder
munetoshi
0
170
Blazing Fast UI Development with Compose Hot Reload (droidcon New York 2025)
zsmb
1
290
High-Level Programming Languages in AI Era -Human Thought and Mind-
hayat01sh1da
PRO
0
770
#QiitaBash MCPのセキュリティ
ryosukedtomita
1
1.3k
“いい感じ“な定量評価を求めて - Four Keysとアウトカムの間の探求 -
nealle
1
10k
Team operations that are not burdened by SRE
kazatohiei
1
310
プロダクト志向なエンジニアがもう一歩先の価値を目指すために意識したこと
nealle
0
130
NPOでのDevinの活用
codeforeveryone
0
830
Quand Symfony, ApiPlatform, OpenAI et LangChain s'allient pour exploiter vos PDF : de la théorie à la production…
ahmedbhs123
0
190
A2A プロトコルを試してみる
azukiazusa1
2
1.4k
Featured
See All Featured
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Practical Orchestrator
shlominoach
189
11k
Being A Developer After 40
akosma
90
590k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Art, The Web, and Tiny UX
lynnandtonic
299
21k
4 Signs Your Business is Dying
shpigford
184
22k
Thoughts on Productivity
jonyablonski
69
4.7k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.5k
Java REST API Framework Comparison - PWX 2021
mraible
31
8.7k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
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.