Too often those adopting agile learn the ceremonies and perhaps even the dark art of story writing – but they delivery and efficiency aren’t that much better the “old ways”. Agile isn’t just about learning a new set of working practices – it’s about a commitment to maximise delivery of finished working software that is “good enough”.
I was chatting to a colleague who had received a Project Initiation Document/Statement of Work from a fairly well known SI House. He asked me to review it which I did. While it was well written and described plenty about how the solution would be designed and it’s many technical characteristics it failed to mention anything about the business benefits or business value of the solution.
As an agile practitioner, I always look to deliver features that have “high business value”. In general this means:
I have one simple question I ask if I want to find out if a team is producing a good quality product – would you deploy to production on Friday?
Many companies refuse to allow software to be deployed on Friday as few staff are on hand over the weekend if the deployed software fails to work leaving the service unavailable for 48 or more hours.