The very notion of a "project" implies that somebody, elsewhere, has decided what's valuable, and that the team must accept that assessment. That is, if you have a project, then someone in management has decided that project is valuable enough to assign the work. 1/5
Imposed assignments from outside cannot reflect the current needs of the customers right now becuase there's an implicit time lag as the "project" moves though the system. The fact the decision was made elsewhere increases the odds that the work definition is stale. 2/5
The whole idea of a "project" works against your agility. 3/5
Agile teams speed up the loop by assessing value themselves by conversing w/ customers directly. You can't have it both ways. 4/5
Dump the "projects" and work on the product as a whole. Do what's needed to add value to the product, and learn what' valuable through frequent conversations (and other communications) with actual customers. 5/5
