What’s the best way to manage project execution today?
There’s a ton of methods to choose from – Waterfall, Agile Scrum, Kanban, RUP, Agilefall, BPU. You name it, there’s a method out there. And that’s the point. These methods were developed for different types of project work. Agile methods have been proven to speed up delivery of software with reduced risk. Classic waterfall methods still do a great job for infrastructure work like building out networks and opening new offices. In order to appease the business leaders that don’t “get” Agile, a hybrid has been developed that still reports milestones and date targets while primarily executing in Agile fashion. Some call this hybrid approach “Agilefall” and there are combined software/hardware projects that employ Agile for the software component, Waterfall for the hardware, and program management over the whole thing to make sure they sync up.
So which one for your IT department? Well, let’s take a look at the type of work IT does. Software development? Yes. Application rollouts and integrations. Check. Network build-outs? Yep. Desktop/laptop refresh cycles? We do that too. Suffice to say, IT is a diverse place with a very heterogeneous set of work. Obviously, one size does not fit all here.
So, what to do? The answer is pretty simple – use the method for the job at hand.
But wait – doesn’t that create a free-for-all, with project managers picking their favorite execution method? Without governance that’s exactly what will happen. So, let’s add some governance.
First, establish a PDLC – project development lifecycle – with key control artifacts and processes. A common project selection and initiation process. A common set of high-level control artifacts such as status reporting (yes – an Agile status will look different from the others – but we still need status!), risk and issue logs. Then, setup standard methods within the PDLC for project managers and scrum masters to follow. The governance should also include a set of parameters that help you choose which method to follow.
While trying to establish a rigid SDLC that everyone in IT follow could result in gridlock, having multiple methods need not result in chaos. A little standardization and governance can go a long way.