How To Stop A Kidde Smoke Alarm From Beeping

Metodologie agili??

The situation of software development in Italy is daunting.
lacks a culture of development, the vast majority of small businesses that make software or that have a development department, in fact does not use any methodology , approaching the software production process as if they were small artisans.

DISCLAIMER: there is nothing wrong with small-scale approach, the fact is that the craftsmen are few good: the carpenters who can build a beautiful chest of drawers from simple oak boards are few, and those few taken so long, and they charge a lot.

programmers hired by the small Italian company no resemblance to those chosen few woodworkers. They usually have limited time constraints, are often underpaid and their work is not appreciated by those responsible for non-technical (when in fact most people know to judge a well-constructed table).

The craft of software is more like the total lack of responsibility of project manager, project leader and general project-something: hire new graduates, pay it a bit 'less than the market average, smokily defined by their task, the time based on your impressions and after verification that the staff did not understand what to do , the time has increased tenfold, programmers hate each other and hate the project-something.

Well, if this is the situation in your company is immediately and brutally clarify one thing: you can not even put up a box of fruit, other than the bedside table in oak. You
use of methodologies.

The project-something at this point move up in memory of the magic word that demonstrate the winning path: metodologie agili , che negli cervelli dei diversi attori si traducono in:

[manager capo]: azienda all'avanguardia, siamo forti!

[project-something]: lavoro fatto bene, meno lavoro per me, più lavoro per lo staff.

[programmatore]: nessun vincolo, nessuna metodologia.

Le metodologie agili funzionano se il team di sviluppo conosce e usa già una metodologia (non agile), altrimenti è molto probabile che un processo agile venga preso come "nessun processo" e si consegni l'intero sviluppo all'anarchia.