When a SW project finish, a Project Manager is a happy, a company can send the bill and … the team moves to another project leaving the code to the lucky maintenance team.

Is the project team deeply motivated to build a product who can last for long? Is the maintenance team skilled (and willing and has the right incentive) to make the system working better and better?


Here is a possible recipe:

Form long-lived teams around applications/products, or sets of features.  A team works from a prioritised backlog of work that contains a mix of larger initiatives, minor enhancements, or BAU-style bug fixes and maintenance.  Second-level support should be handled by people in the product team.  Everyone in the team should work with common process and a clear understanding of technical design and business vision.

via Projects are evil and must be destroyed | Evan Bottcher.

What do you think?