NYCGB releases Spem in Alium (Tallis)

NYCGB, my second favourite choir* in all the world, has just released Spem in Alium by Thomas Tallis, conducted by Ben Parry.

As the email I received from NYCGB HQ this morning says,

Yes, Spem in Alium is that famous choral piece in forty parts, a Tudor titanic that still dwarfs most other English choral music half a millennium after its composition. But the truly remarkable thing about Thomas Tallis’s huge motet is that it manages to be intimate and personal, the full texture growing from and yielding to smaller-scale cameos. All the little details and the gradual shifts – and the climactic power – shine out from this new recording by the National Youth Choir, captured in the ideal acoustic of Tonbridge School Chapel.

If you are into early music, check it out, a blissful piece of choral music sung by a first class choir with that crystal clear NYCGB sound.

It is available (only £0.99) on:

  • My favourite choir is clearly the NYCGB alumni choir! 😉

Agile release planning with multiple projects

One of the biggest challenges we faced when we started down the Agile path was how to accommodate working on multiple projects concurrently. This is a little insight into how we are currently managing ourselves across two projects plus business as usual tasks.

The Agile ideal

Most Agile/XP/Scrum literature assumes a single, cross-functional team working on a single project for a single customer using a narrow range of technical disciplines. The primary reason for this is that task-switching is really expensive: it is much more efficient to remain focused on one project.

That way of working, though attractive, is more or less impossible in our situation; something that I’ve also heard from other university digital teams. We don’t just work on projects, we have business as usual commitments (which include meetings, support calls, personal development, blogging, editorial calendar updates, etc.), consultancy (where we work on approved institutional-priority projects managed by other teams) and portfolio mechanics (board meetings and related admin, writing up project ideas and terms of reference documents, etc.).

After all that excitement has been deducted from our working week, we are generally left with only about 40% of our time to dedicate to pushing projects towards completion. We therefore need to be careful to extract as much value as we can.

Continue reading Agile release planning with multiple projects