Comments on: Agile Development with SDL Tridion

By: Albert te Boekhorst

Albert te Boekhorst — Fri, 02 Sep 2011 14:31:28 +0000

Interesting subject Jules. I have been engaged on a Tridion project where I am the Scrum Master. We have been using Agile Scrum continuously for almost 1 full year now and still going strong.

So far we overhauled the clients entire website including a major change to the blueprint design and implemented a new information architecture.

If I find the time I will put my thoughts on the subject up on my blog.

By: Jules

Jules — Mon, 15 Feb 2010 07:49:44 +0000

Hi Paul, That sounds an awesome idea. Would love to know how you get along with that… Cheers,Jules…

By: Paul Stodart

Paul Stodart — Fri, 12 Feb 2010 00:44:48 +0000

Agile Project Management often works for Software Development as multiple parties have to commit to fixed deliverables within short bursts.

I am currently trialling the same philosophy within the Content Management process itself. Publishing content on time fails when English Master’s are not delivered, translations are not completed on time, reviewers are not available or publishing resources are distracted with something which is now more urgent.

We are now working with short “sprints” of 10 day cycles, and agreeing Content Plans with all Stakeholders. Priorities are clear, along with delivery and review dates. We are hoping this method will focus EVERYONE in the Content Organisation on achieving the same goal.

I will let you know how we get on.

By: Quirijn Slings

Quirijn Slings — Wed, 11 Nov 2009 20:25:07 +0000

Hi Jules. As you’ve pointed out very well, it’s especially the functional structure that gets in the way of an agile approach. Blueprint, schema and security design are things you need to think of up front – at least that’s what we’re always telling our customers.
IMO the best way around it is to keep these designs simple. That’s usually more future-proof than a very complex, tailored design. One example: I always recommend to use a single content parent for all content. You can use folders for security (works like a charm) and if you ever want to move content about, you can!

By: Jill Ducey

Jill Ducey — Wed, 11 Nov 2009 18:15:50 +0000

For Tridion projects I focus on Schema development, Taxonomy design and building Component Templates. I agree that Schema, Template, Folder/Structure Group and Application development fit Agile development. We modify all of these elements frequently since we always find better ways to approach our data.

We don’t have a lot of BluePrint branching yet and it’s a area we hope to find flexibility in when we have to rethink our approach.

I can already see how Content publications split by site (all English based) would be advantageous when it comes to Permissions. We chose to house all of our web properties in a single Content folder to limit publication license fees.

In my opinion Tridion is a powerful and layered CMS and having a good team, whichever development methodology you choose, is the key to success.