Phoenix Project CH. 16 19 - Hoangdinh85/NTI-310 GitHub Wiki

The technical changes in these chapters between how IT Development (Dev) and IT Operations (Ops) run, represent a change in the way the departments see each other. Previously they saw each other as separate entities. As two separate departments whose goal was to ensure that the department succeeds in meeting its objectives. The problem with this type of view is that they don't see themselves as the same. They don't see how their actions contribute to a living product-stream and that the product-stream has a direct impact on the overall success of the company.

Changing the way they see their role in the product-stream of the company helps them to see the steam as a whole. By seeing the stream as a whole, they begin to see their role in the stream and how that the stream generates work-in-progress. They begin to see that managing this is key in their ability to complete work as a whole. Technically, they begin to realize that in order to break the vicious cycle of dealing with unplanned work, they need to stop starting new projects for a little while and finish up the projects the work in progress that continually gets hampers their momentum and quality of work. My suspicion is that as they get to a place where the are no longer fire-fighting they will ask themselves - how do we continue to be in a position where we don't have to be reacting to unexpected work.