Mary/Tom:

have you written on, or do you know of a good treatment of, possible
practical consequences of handling software development as "projects"
or "products"? I'm a bit sloppy in my description here, but I think
you might know what I mean.

This might be simply an insignificant semantical difference, but I
think I've seen you express a preference for the latter at some time.

I myself am bothered by how the concept of a "project" seems to have
become an excuse for not having to think about things like
ineffeciences caused by multi-tasking, the problems of maintaining a
huge number of differing initiatives that all attempt to modify the
same code base, and so on. "Just start a project and we'll be fine. No
'buts'!"

I believe our language controls our thinking, which controls our
behavior. Who has experience with this when it comes to talking about
"products" or "projects"?

Best regards
Tobias Fors