Software Engineering with Visual Studio Team System

Another process and engineering book has arrived that focusing on building products using Team System not through the typical working a task list of planned steps but rather allowing the flow of customer value to drive the project.


Sam Guckenheimer describes this as a “value-up” paradigm:

In my book, I discuss what I call the value-up paradigm. In short, this is the team’s focus on flow of customer value as the driver of a project, as opposed to the work-down through a list of planned tasks. In the book, I list seven characteristics of this paradigm, describe its implications for each of the disciplines on the team, and the implementation with Team System. Here’s the table from the book. (If you’ve read either of the current versions of __MSF_, the value-up concepts should be very familiar.)_

I look forward to picking up a copy of this latest [book](http://www.amazon.co m/exec/obidos/redirect?link_code=ur2&tag=pataltmancom&camp=1789&creative=9325& path=ASIN%2F0321278720%2Fpataltmancom%3F%255Fencoding%3DUTF8%26camp%3D1789%26l ink%255Fcode%3Dxm2)![](http://www.assoc- amazon.com/e/ir?t=pataltmancom&l=ur2&o=1).