Posts Tagged ‘cultural resistance’

Is Agile Broad Enough?

Friday, June 11th, 2010

It is widely accepted that Agile delivery demonstrateably adds value to software teams and their ability to bring software to fruition. There is however a question around whether Agile can achieve its full potential in the face of cultural resistance within the wider enterprise. For some there is now the acceptance that IT has the potential to be more than a cost burden; it is actually an avenue to compete more effectively in the market. IT is a strategic tool where projects with quantified business value deliver everything from streamlined internal processes to new customers through social networking sites. The better able the enterprise is in harnassing IT the better it will prosper, however it is not easy and they achieve varying degrees of success.

Set against a wider context of the end-to-end business process, actually delivering some working code comes far downstream. What needs to happen first? First ideas need to emerge in the organisation, gain momentum, become scoped, costed and valued and then, if all goes well, the initiative results in working system.

Given the project delivers a working service, we would be interested in a retrospective aimed at measuring success. For instance, certain assumptions were made regarding how much value the project would bring and how much it would cost to bring to fruition. We want to know whether it was ultimately worth taking this project forward once it has had a chance to ‘bed down’ because that information is valuable. Ideally a cycle can be established where the assertions and outcomes of initiatives are tested so that they may inform future estimation activity resulting in the ‘go/no go’ decision that governs all intiatives becoming more accurate. In this scenario, the estimates of future projects (cost and value) are compared with the resulting outcomes ultimately leading to the enterprise fully directing the IT function and reaping maximum competitive advantage.

Tags: idea management, governance, PMO, Programme management, Project management, effort estimation, value analysis, agile evolution

Café Culture

Monday, May 24th, 2010

Remember when they changed the alcohol laws and expected the British would start drinking like our European neighbours? Have you been into your city centre on a Friday night recently? It didn’t happen. It might happen but cultural change takes a long time.

If we are going to wait around for fundamental business cultural change before Agile can work it could be a really long wait. People will lose patience, the next big thing will come along, and everybody will jump on that bandwagon heading nowhere fast. No, no, no, there’s too much that is really good about Agile and what works – works, so let’s leave it alone. What I’m talking about is Agile Requirements – that’s rigour around user stories. Stories don’t belong in Delivery, they’re an input to Delivery, they’re the ‘requirements’, and they belong to the business. Yes, this goes against the status quo – all well – that’s what makes for a good conversation – right?

Does this violate the Agile principle of ‘cross-functional teams’. No, I’ve already said that what’s in Agile Delivery works and stays as it is. I’m just saying that it isn’t efficient to show up on day one of a Scrum for a planning meeting and expect all these expensive people to start writing stories from scratch, or worse yet, trying to make sense of a big mash-up of stories and fragments before they can get to work building something. It’s demoralising and it’s counter-intuitive. It doesn’t work. You show up on day one, you want some good quality stories to get your teeth into. That’s common sense – maybe not common practice, but it’s common sense.

I’m going to make the distinction between Agile Requirements(AR) and Agile Delivery(AD). So, to be clear, part of the story telling has to happen outside of AD. Once the iteration is underway, the two work together, but AR outputs stories and AD takes them as an input. This has a lot of ramifications – and they’re all good.