Skype's Lenn Pryor left a comment responding to my post, The Skypecast service shows a developer program failure.

Skypecasts is a step in a new direction for Skype as it uses some new server based conferencing technology to enable a scalable infrastructure. At the time the product was planned, Skype made a deliberate decision to start by first building a stable platform, testing, learning, and growing BEFORE exposing a public API. This makes good operations sense and enables us to stabilize the product before making it available as a service that developers will rely on.

It is not an oversight, nor a failure, but a deliberate step to ensure the best experience for all. Incidentally, your post stops short of helping your readers and Skype understand what you think developers would do with this API and what the killer scenarios are for this API in your humble opinions. We always welcome input and ideas from the community and hope to see those needs met as we grow Skypecasts from an early vision into a successful platform.

Lenn, thanks for filling us in. It seems some agile development methods, like short, evolutionary development cycles, are evident in Skype's production of Skypecasts. Skype Journal and our readers (with Skypecasts will they be listeners? panelists? discussants? microphone hogs? carolers?) will amp up the conversation.