Archive for October, 2008

Amazon EC2 graduates: Here Comes The Cloud!

October 28th, 2008

Cloud of Fire Last Friday was an horrible day for the markets, but a big step forward for the IT industry. EC2, The first large-scale on-demand computing cloud, graduates and is now labelled as production-ready, with SLAs.

After bout 2 years of beta testing and improvements, Amazon offers a computing cloud alongside its storage cloud. Being the first of its kind, the cloud will certainly have a great impact on the IT industry as a whole.

Initially, when Amazon launched its WebServices division and its storage service S3, it might have appeared as a weird move from the large retailer. But now, several years later, with EC2 and the myriad of additional services (payment, content delivery, etc.), it makes a whole lot sense. Amazon is clearly positioning itself to build the infrastructure of the Web. This is big business. And they’re several steps ahead the competition, emerging from Google (using a different approach with AppEngine), Microsoft (with their rumored “Cloud OS” named Strata), and maybe the smaller force.com (even if I don’t really believe in its proprietary approach).

It’s a huge opportunity for software vendors and service providers (plus a death threat to many hosting providers that can’t adapt fast enough): access to a high-end technology and infrastructure to deliver new services to customers at a fraction of the capital required before it. Any startup can now rely on a strong and scalable infrastructure to imagine and create new products and services, without worrying about consequent capital investment in hardware and infrastructure. Also, it will be easier to imagine and try ideas, fostering fast innovation cycles in the online business.

OK. And what about ECM in this?

Enterprise Content Management is about managing content, right? And content, especially pictures or videos, require space to be stored, computing power to be processed (think large picture management, video processing, etc.) and bandwidth to be delivered. It requires infrastructure. A lot. Exactly what the cloud revolution is addressing. That’s why I really expect a strong transformation in the ECM market enabled by the cloud-related technologies and the widely available broadband: we are about to be able to deliver to organisations a high level of service at a fraction of the price is currently cost priced. The Cloud enables new players (and I expect our company to play a key role here) to offers innovative services in the ECM market, disrupting existing leaders stuck with their centralized, aging technology.

Imagine your content repository, plugged onto a high performing cloud-based infrastructure (be it Hadoop / HDFS, my team is already working on and we begin to get really interesting results), S3+SimpleDB (I don’t really believe in this option actually) or Google AppEngine (interesting but so closed and proprietary…). It just opens new horizons to content stores, content processing and content management! Horizons that were just dreams before at reasonable prices. It only can make innovation more vibrant in this area. And we’re not the latest on this…

The ECM market, due to its nature, is gonna be one of the most impacted by the cloud in the IT industry. We now have to achieve unlimited storage and near-linear scalability! We’re committed on this!

So, the could is coming and will dramatically the IT landscape. For the best I think. Don’t give up open source and open standards. They’ll be even more important. And you’ll get the most from the Cloud. Just another step. But a big one. Interesting times ahead… :-)

Stay tuned!

EB.

“Scrum and XP from the Trenches” by Henrik Kniberg

October 9th, 2008

Trying to help our teams (4 of them, each having its own Scrum Master and Product Owner) properly start to implement Scrum, I was looking for more than theory to get them started, to prevent them from common traps and pitfalls. I was getting often the same questions and mistakes in setting up the process. I had to find something to avoid writing my own guide to Scrum… ;-)
And… I've found (actually I remembered a mail, a friend sent me a while back) the gem: "Scrum and XP from the Trenches" by Henrik Kniberg. This is an actual guide for implementing Scrum in your team, although the author says the reverse. It is answering a lot of practical questions and daily issues, staying away from dogmatism and often suggesting several solutions to needs (like: in what to should we keep the backlog? how could it be integrated with our issue tracker? etc.).

And it's free for online reading, so: try the book from InfoQ and buy it it you like it [Amazon, Lulu].

Happy reading!

EB.

PS: plus, it gave me the first opportunity to actually use my new toy, an ebook reader, the Sony PRS-505. And I'm positively impressed by the level of reading comfort.

About

October 1st, 2008

coming soon… :)

Scrum Essentials I

October 1st, 2008

Scrum!
Credit: darkmatter on flickr

This is the first post of a series on Scrum, focusing on real-world implementation in an average small software company.

As part as our switch to Scrum, I have read a number of articles and watched a dozen hours of conferences. From this I’ve created this compilation, I could call "Scrum Essentials", that I’ve used to introduce Scrum to people before doing a short and condensed hands-on training.
So I’ve decided to share it. :-)

Introducing Agile and Scrum

I would propose to start with those 2 conferences by Scrum’s inventors:

And this slide deck, explaining the differences between agile and waterfall approaches, why it works and how to implement it: Introduction to Scrum by Simon Baker.

About the Backlog

The product backlog is a high-level document for the entire project. It contains broad descriptions of all required features, wish-list items, etc. It is the "What" that will be built. It contains rough estimates, usually in "story points" or days. At the start of each sprint, the Team choose with the PO which items will go into the Sprint Backlog, refining their estimate and breaking stories into smaller items/tasks.

And for teams, like ours, that need to work on several projects, here are some interested thoughts and processes (that we actually use, by the way):

About User Stories

User stories are describing the system’s behaviors from users’ point of view. This is typically what the PO will write to allow the Team to code the software. It is critical to master this aspect to get a good Scrum.

Which is nicely completed by Writing contracts for agile development when fixed-priced projects and requirements have to be assessed initially. We use this to estimate & scope projects alongside Agile Specs, see: Agile Specifications: is it an hoax? and Nokia Test: Agile Specifications.

You might also want to read the posts of Mike Cohn on User Stories to get practical answers.

About Planning & Estimating

User story estimation and planning is key to any agile team. And it might be very confusing for traditional Project Managers becoming Scrum’s Product Owners (PO). Mastering the art of agile planning is really core to a successful Scrum implementation (and can be done in steps).

You can watch the conference "Agile Estimation" by Mike Cohn @ Agile 2008: part 1part 2.

About migrating to agile for a company

And last but not least, maybe more targeted at executive, wondering how to migrate their processes to Agile / Scrum: ADAPTing to Agile: A Guide to Transitioning

And some interesting blogs to read

Happy reading!

That’s all for the essentials. I would love to get feedback if you think I should add something or if you know some hidden treasures. Or if you try them :-)

I’ll post more about our switch to Scrum and our implementation details in the following weeks.

Hope it helps,

EB.