Skip to content

Tag Archives: methodology

How to explain backend changes that support undelivered features

My current work environment is in a cost-pressured large national transport enterprise with a familiar internationally-recognised brand name. We have to build a lot of systems that model many real-world, highly-regulated, parameters and states. This data is often used to feed into other systems that feed the voracious information maw of an often severely critical […]

Air France stops maintenance in China after screws missing from plane

This is why I don’t trust off-shoring of aircraft maintenance. The same reason that poisonous substitutions are made in toothpaste or cheap lead paint used on a children’s toy; it’s the whole idea of taking something based in complex skills and knowledge-based engineering and buying on price, which ends up in a business environment like […]

The Frustrated Architect

An interesting set of slides by Simon Brown from a talk he gave about the role of the architect. A PDF is attached to the linked post or you can view the slides online. Wish I had heard the talk (see below). The Frustrated Architect: Software architecture plays a pivotal role in the delivery of […]

REST and SOA and Agile and Waterfall

Recently I’ve been working on two projects. They are an exercise in contrasts. First the technologies and the development methodologies. So the first company uses a very Waterfall process and the integration platform is SOA. We’ve managed to build, in the middle of this, a small and focussed Java component that uses JMS in and […]

Business change methodology gaps | Keep The Joint Running

Whatever else you do, give yourself a chance: Rename every project, initiative and strategic program in your organization to reflect the business change goal instead of the system name: Sales Force Effectiveness Project instead of Salesforce.com Implementation; Evidence-based Decision-making Initiative instead of Business Intelligence Implementation. The impact is surprisingly large. — Business change methodology gaps | […]

Managing to the numbers | Keep the Joint Running

People who manage purely by revenue or share price generally shaft their companies in the medium term. Bob Lewis, of IT Catalysts, is always worth a read and has many insights which I think all developers and architects should pay attention to. So you improve fulfillment (improved quality) and customer service (reduced cycle time). Revenue […]

That’s the just the way it’s done round here

Many of us hear this phrase in our workplace. When you hear it, what you’re really being told is that the company is afflicted with one or more of the following: is afraid of change not interested in improvement has a rigid top-down process development style doesn’t care what you think I think the greatest […]

Agile and assembly lines

Coder Friendly’s got an interesting article about Agile Evangelism. First I’m not going to take issue with the article itself but something that he quotes from DanC’s Lost Garden on Managing Complexity: The repetative (sic) steps that a single worker performs on an assembly line is a good example of a simple task This is […]

Systems versus Individuals and technical debt

I kind of disagree with this picture by Josh Susser regarding the “circle of death” in terms of code quality and late night effort. It is right enough as far as it goes but it doesn’t go far enough. First up, the easy way out – take a day off, go for a walk in […]

Agile is hard

Johanna Rothman on agile adoption for the organisation: Agile requires the discipline to move projects through teams. Multitasking is nuts in agile. Moving team members around to have the “best” specialist available for a particular team is nuts. Performance reviews for individuals is nuts. Managers have to change everything they do, if they want to […]