Worst. ADF. Project. Ever.
summary
A cautionary project postmortem: using Oracle Application Development Framework under a fixed-price subcontract with a full team up front produces a growing binder of feature creep, rushed five-day tool training, and 80-hour weeks that exhaust staff. The result is hundreds of bugs, two months of work to fake back-button/session behavior, and a delivered rich‑internet app that runs but is fragile, confusing users with multi‑tab sessions and fragile state because no early proof‑of‑concept validates expectations.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:40Speaker and ADF background
- 4:10Subcontractor without access
- 5:36Fixed price vague requirements
- 7:02Full team coding no ramp-up
- 8:06Feature creep design by committee
- 10:54Inadequate tool training
- 13:07Overstretched resources risks
- 15:35Releasing poor quality code
- 17:25Miscommunication with users
- 21:41Delivery and lessons
- 23:48Ten things that could have been done differently
- 26:58Q&A
related talks
36mHow to make your daily routine, code and database more efficient
46m5 Things Developers do that Drive Me Crazy
34mHacking the Oracle Application Framework
16mSurviving without a database framework
52mFrom Irrational Configuration System to Functional Data Store
30mCloud native low code apps with Oracle APEX on Oracle Autonomous Database
19mFrom zero to hero: Rapidly building a mobile F1 app using Oracle APEX
28mNext-Gen, data-driven application development