venerdì 26 gennaio 2007

cosa trasmettere ai figli

Michel Houellebecq – Le particelle elementari (Bompiani, 1998) p. 170

"[per i maschi] i figli erano la trasmissione di uno stato, di regole e di un patrimonio. E questo principalmente nell'ambito dell'aristocrazia, ma non solo: anche tra i commercianti, i contadini, gli artigiani, in pratica in tutte le classi sociali. Oggi tutto ciò non esiste più: io sono un impiegato, cosa dovrei trasmettere a mio figlio? Non ho nessun mestiere da insegnargli, neppure so cosa potrà fare da grande; e comunque, per lui le regole che ho conosciuto io non saranno più valide, vivrà in un altro universo. Accettare l'ideologia del cambiamento continuo significa accettare che la vita di un uomo sia strettamente ridotta alla sua esistenza individuale, e che le generazioni passate e future non abbiano più alcuna importanza ai suoi occhi. E' così che viviamo; e oggi per un uomo avere un figlio non ha più alcun senso. La situazione delle donne è diversa, giacché non hanno mai smesso di provare il bisogno di avere un essere da amare – il che non è, né è mai stato, il caso degli uomini.”

sabato 13 gennaio 2007

Economist - But did they buy their own furniture?

The Economist, Aug 10th 2006 But did they buy their own furniture?

As a new YouGov poll for The Economist shows, Britons are surprisingly alert to class—both their own and that of others. And they still think class is sticky. According to the poll, 48% of people aged 30 or over say they expect to end up better off than their parents. But only 28% expect to end up in a different class. More than two-thirds think neither they nor their children will leave the class they were born into.

What does this thing that people cannot escape consist of these days? And what do people look at when decoding which class someone belongs to? The most useful identifying markers, according to the poll, are occupation, address, accent and income, in that order. The fact that income comes fourth is revealing: though some of the habits and attitudes that class used to define are more widely spread than they were, class still indicates something less blunt than mere wealth. Being the sort of person who “buys his own furniture”, a remark that Alan Clark, a former minister and diarist once reported as directed at Michael Heseltine, a self-made Tory colleague, is still worthy of note in circles where most inherit it.

A survey conducted earlier this year by Experian for Liverpool Victoria, a financial-services firm, shows how this convergence on similar types of work has blurred class boundaries. Experian asked people in a number of different jobs to place themselves in the working class or the middle class. Secretaries, waiters and journalists were significantly more likely to think themselves middle-class than accountants, computer programmers or civil servants. Many new white-collar jobs—in vast call centres, for example—offer no more autonomy or better prospects than old blue-collar ones.

CIO Magazine - Postmodern Manifesto

CIO magazine 1 may 2006

The Postmodern Manifesto, by Christopher Koch

In a 2005 SIM survey of skills that CIOs expect to most value in their IT staffs over the next three years, project management led the list, followed closely by company, functional and industry knowledge. Other skills in demand included business process reengineering, user relations management, negotiation, change management, communication and managing expectations. Only two technical skills (systems analysis and systems design) made the top 15—and both of those skills focus more on architecture and process than on hard-core programming.

To some extent, the deconstruction of IT has already occurred, especially in big companies where the large scale of IT and the separation of IT functions such as help desk, application maintenance and some programming have made them candidates for outsourcing. More and more jobs in IT will become components in a distributed services supply chain modeled on today's distributed manufacturing supply chains.

IT departments already have undergone a structural shift. The number of programmers employed in the United States has dropped by 25 percent since its peak in 2000, even though the total number of IT workers has increased slightly since then, according to the Bureau of Labor Statistics. In our "State of the CIO 2006" survey, 76 percent of respondents said they outsource application development, maintenance or support—more than double the next highest category.

In one respect, the distributed services supply chain model is actually creating more work. As pieces of the IT supply chain break off and become more specialized, the need for coordination of the pieces increases. That means the number of internal jobs dependent upon external people is increasing. This shift is reflected by the new emphasis in IT departments on relationship management and project management.
Economists call these kinds of skills tacit work, which requires the ability to analyze information, grapple with ambiguity and solve problems, often based on experience. Tacit interactions are complex and require interaction (such as managing a software development project) rather than being simple and solitary (fielding help desk calls with a script, for instance).

Tacit jobs have been growing three times faster than employment in the entire national economy, according to consultancy McKinsey, and they make up 70 percent of all U.S. jobs created since 1998 and 41 percent of the total labor market in the United States. These roles track pretty closely with the categories where the Department of Labor says IT employment has made the biggest gains since 2000: application engineers, systems engineers and network analysts.

Glass - Standish Chaos Report

Communications of the ACM, October 2006

Robert L. Glass The Standish Report: Does It Really Describe a Software Crisis?

Most academic papers and guru reports cite the same source for their crisis concern—a study published by the Standish Group more than a decade ago, a study that reported huge failure rates, 70% or more, and minuscule success rates, a study that condemned software practice by the title they employed for the published version of their study, The Chaos Report.
So the Standish Chaos Report could be considered fundamental to most claims of crisis.

Several researchers, interested in pursuing the origins of this key data, have contacted Standish and asked for a description of their research process, a summary of their latest findings, and in general a scholarly discussion of the validity of the findings. They raise those issues because most research studies conducted by academic and industry researchers arrive at data largely inconsistent with the Standish findings.

Let me say that again. Objective research study findings do not, in general, support those
Standish conclusions.

Standish, please tell us whether the data we have all been quoting for more than a decade really means what some have been saying it means. It is too important a topic to have such a high degree of uncertainty associated with it.

Boehm - Requirements Volatility

Communications of the ACM, October 2006

Barry Boehm One-size-fits-all Methods: the Wrong Solution to new Problems

Requirements Volatility ratings for stable embedded devices are still in the 0.1% to 0.3% per-month range, but the counterpart ratings for rapidly changing competition-driven applications are often in the 10% to 30% per-month range.

Level 5 CMM - India

Communications of the ACM, October 2006

Michael Cusumano, Envisioning the Future of India’s Software Services Business:

In terms of process maturity, the Indian companies are difficult to beat as well: It is well known that, as of last year’s count, 80 of the World’s 117 SEI CMM Level-5 companies are based in India.

David Grossman

David Grossman, ospite nella trasmissione di La7 L'Infedele, condotta da Gad Lerner.

Parlano di Bruno Schulz, considerato affine a Kafks, un genio, ucciso per scherzo dalle SS nel 1942 e autore di un libro pubblicato da Einaudi, Le botteghe color cannella.
Probabile che Schulz sia citato nel libro di Grossman Vedi alla voce amore.

Sembrano interessanti, di Grossman, anche i libri per bambini e per adolescenti.

Dilbert - project management

Dilbert su PMI Journal (3-11-06 Scott Adams.)

Boss: Yesterday I had a great meeting about project Wombat.
Dilbert: What?! I've been managing that project for six months! How can you have a meeting without inviting me? !!
Greta: Have you noticed that meetings go smoother without any knowledge or expertise?
Boss (very small font): Kinda.


Khaled Fouam Allam: Solitudine dell'Occidente. Rizzoli 2006

Rafik Schami (siriano, cristiano): saga Il lato oscuro dell'amore (Garzanti)

Ivo Andric: Il ponte sulla Drina

Predrag Matvejevic: Mediterraneo

domenica 7 gennaio 2007

Agile and Toyota - Alistair Cockburn

due post il 31-12-2006 e 1-1-2007

Re: [APM] Management lineage of software processes

Interestingly, the Toyota Production System (TPS) was already doing most of what we now call agile, already back in the 1970s.

The west didn't notice what they were doing and misinterpreted it. (most of) Those of us who wrote the agile manifesto in 2001 were not aware of TPS, and simply wrote what was on our minds. Since then, many of us have looked at TPS --- and I for one, can't see that we've added very much to what was already in TPS (test-first comes to mind as an exception).


Re: [APM] Management lineage of software processes

Thanks, Boris. Well, I have three times visited a place in SLC(O.C.Tanner) where they are implementing TPS pretty strictly in their awards production, and I am unable to to suggest anything that they haven't already been doing for over a year. I.e., TPS already leads them to everything I know.

Personally, I think it's pretty nifty that we in software managed to reinvent our own localization of the ideas of TPS without knowing first about TPS. It doesn't bother me if Toyota got there first (over a 60-year period). I think the ideas are there to be found by multiple groups of people ... the math adds up, reflection and inspection lead there.

But the only reason I brought this all up was that someone asked about the sequencing of ideas and influences. AFAIK, we software people were not particularly influenced by Deming or TPS in coming up with the agile manifesto (I can speak for myself --- my information came strictly from staring at my interview results and management attempts in the early/mid 1990s ... I suspect the same was true for at least most of the people at the Snowbird meeting). And still, looking at time sequencing, it is clear that lean manufacturing got there first. I still don't know about Deming'sstuff.

Lean and contracting situations - Mary Poppendieck

post il 3-1-2007 RE: [leandevelopment] Budgeting a Lean Project


It seems that you are in a contracting situation, as opposed to developing software for use within your own organization. If I can make that assumption, then I would suggest that lean principles are not particularly viable unless lean contracting is also part of the equation. When you reach organizational barriers and lean organizations run up against non-lean organizations, it is often impossible for the supplier to act in a lean manner.

As an example, many automotive suppliers have adopted lean practices in order to supply Toyota. The lean areas of their plants are much more efficient and cost-effective, but they are usually not able to supply other automobile companies with the lean area of the plant – they have to maintain a non-lean (and less efficient) area of the plant to serve those other customers. Why? Because the Detroit automotive companies still want parts delivered in large batches – they thin the economies of scale are the dominating factor in their business, despite decades of evidence to the contrary.

Similarly, if you have customers that believe that accumulating huge batches of detailed requirements is the most efficient way to contract with suppliers, then you may have to operate in a non-lean way with those customers. When you find customers that want a lean supplier, you can partner with them in a lean way, and as the automotive suppliers found out, deliver better, more cost effective software. However, in general, the choice lies with the customer, not the supplier.

Mary Poppendieck