There is a lively debate around whether the Death Star could be classed as an Agile Project. I would suggest, that it’s more relevant to look to the Rebel Alliance. The Alliance shows us a good example of a cross-discipline hyper-productive Scrum Team in action.

The Death Star project does have a clearly defined Vertical Slice, which would seem to point to an Agile approach. The planet-destroying superlaser was delivered as a functional artifact whilst other less important features were dropped.

On closer inspection however we could surmise that the legacy command and control management structure has produced a flawed ‘Scrumbut’ implementation.

The failure to embrace good Planning and Engineering Practices left the weapon with a fatal flaw – open exhaust conduits that allowed it’s destruction.

Don’t be too proud of this technological terror you’ve constructed.” Darth Vader

Clearly a reference to ‘gold-plating’. It seems that Darth Vader was not attending the Daily Meeting or Sprint Review. I’ll leave you to decide whether Darth Vader was a Product Owner or Scrum Leader.

The Death Star was an Agile Project | Hacker News

1] Ackbar, Return of the Jedi “It’s a trap!” [2] The Emperor, Return of the Jedi “As you can see, my young apprentice, your friends have failed. Now witness the firepower of this fully ARMED and OPERATIONAL battle station!” qa-ds1-15215: I was checking out the design and noticed that thermal exhaust port AH-51 is open to the world.
Death Star II As an Agile Project

So, Vader takes an Agile approach. He prioritizes the features list (“Look, we really need the big laser thing; our customers will just have to come to us at first.”), and he works in vertical slices. At the end of the movie, it seems to have paid off.

A recent marketing campaign for MS Project postulated that Luke Skywalker achieved his goal in Episode IV using a traditional Gant Chart. I’m somewhat sceptical – the intuitive nature of the force and the distributed nature of the Jedi are far more akin to a self-organising Agile model.

The Episode IV team comprising Luke, Han, Leia, C3P0, R2D2, Chewy and OB1 is clearly a hyper-productive, cross-discipline Scrum Team. Conforming to the 7+ or -2 team number ‘sweet spot’. The team follows the pattern of an effective geographically distributed(at times) Scrum.

InfoQ: Jeff Sutherland: Reaching Hyper-Productivity with Outsourced Development Teams

Nathan Marz explain Storm, a distributed fault-tolerant and real-time computational system currently used by Twitter to keep statistics on user clicks for every URL and domain. Founding members of the ICAgile Consortium, Ahmed Sidky and Alistair Cockburn, discuss IC Agile, along with Bob Payne, a consultant, coach and trainer.
Distributed Teams Content on InfoQ

InfoQ.com (Information Queue) is an independent online community focused on change and innovation in enterprise software development, targeted primarily at the technical architect, technical team lead (senior developer), and project manager. InfoQ serves the Java, .NET, Ruby, SOA, and Agile communities with daily news written by domain experts, articles, video interviews, video conference presentations, and mini-books.