Collaborate 14: Day 1

Day One schedule for Collaborate 14 looks like so: 
  • Optimizer One-Day Master Class w/ Tom Kyte
  • PeopleSoft Technology SIG, if I have time
  • Collaborate 14 App Training (because why not)
  • IOUG Welcome Reception

I'll be trying to post interesting and relevant information here as necessary. 

Comments

Post a Comment

Popular posts from this blog

What Free AI Is Actually Costing Your Organization

Image
AI tools are cheap to start using and easy to rationalize as low-risk. Most of them are free, or nearly free, at the individual level. No procurement cycle, no budget approval, no formal decision. That's precisely what makes the organizational cost easy to miss until it's already accumulated. This post is about what that cost looks like in practice — not in licensing fees, but in competitive position, organizational visibility, and the quiet dependencies that form before anyone thinks to ask about them. The cost of not deciding Organizations that are slow to adopt AI tooling tend to frame their hesitation as prudence. In some cases that's accurate. But there's a real productivity gap opening between teams that have integrated AI into their workflows and teams that haven't, and that gap doesn't pause while organizations debate governance frameworks or wait for the pricing model to stabilize. What I've observed is that the hesitation often isn't about skep...
Read more

The Signal Problem in Entry-Level Hiring

Image
The frustration is real. LinkedIn is full of it — entry-level roles requiring three to five years of experience, candidates rejected before they get a conversation, a generation convinced the door is locked from the inside. That frustration is worth taking seriously. But most of the conversation stops at the complaint. What's less discussed is the mechanism: why the mismatch exists, who's responsible for it, and what can actually be done. I've been on the hiring side enough times to know we're not blameless. What candidates can do with this If you're early in your career, the job description problem cuts in your favor more than you might think. Most postings describe an ideal candidate, not a threshold. If you meet the core requirements — the actual must-haves — apply. The worst outcome is silence, which you were already getting by not applying. The experience you have is probably more credible than you're presenting it. Internships, co-ops, serious side project...
Read more

Velocity Is a Shadow; Throughput Is Reality

Image
In the previous post, we argued that estimation is a smell—a signal that teams are compensating for unmanaged uncertainty. Velocity, as a direct descendant of estimation, inherits that smell. Scrum reminds us that the purpose of a Sprint is to produce an *Increment of value* , not to consume a predetermined number of points. Velocity measures effort expended inside the team. Customers, however, experience outcomes: features delivered, bugs fixed, and capabilities unlocked. No customer has ever benefited from a higher velocity. Why Velocity Persists Velocity survives because it is visible, numeric, and easy to chart. It gives leaders something to point at and teams something to optimize. Unfortunately, that optimization rarely aligns with value delivery. When a measure becomes a target, it ceases to be a good measure. When velocity becomes important, teams respond predictably. Estimates inflate. Stories are sliced to satisfy point targets rather than user needs. Lower-risk, lower-valu...
Read more