User login

client conversation

Preventing Agile Scrum methodology from degrading code quality

"practical advice for avoiding [delivering broken software with Scrum] – whether you’re an Organizer or you’re an Activist Developer"

The key problem identified is that incentive to abandon code quality to meet time/budget and feature goals.

The solution is to, first, not allow tests, in code, automated, or human, and other issues of code quality to be cut off from the features that are being built. Hide the time in the task estimates if absolutely necessary.

But also:

Scaling and Performance consulting

Stefan's recommended approach:

For performance consulting, begin by asking whether they have high server load or just slow page loads. In the latter case we must first find out if it's the server or something else yslow can tell you.

In the case of high server load you should ask for the slow log. It would be nice if they had monitoring data for cpu ram and so on. Don't ask for full access to the data first. Some companies are really cautious about that and it's not necessary to get access for a starter.

Syndicate content