Brian White

Managing change in a software system is a lot like balancing your personal finances. With or without a resource allocation plan, the assets available and the demands placed on them change constantly. Whether it's your code or your checkbook, the result of mismanaging change over time is likely to be the same: disaster. The complexity and volatility of today's business demands have rendered "traditional" (i.e., ad hoc) methods for software change management obsolete. Distributed teams, multiple platforms, strict cost accountability, compressed release cycles: these mounting pressures dramatically escalate the risks of deploying new applications and integrating existing ones. With technology now serving as the primary interface to customers and partners, an organization ... (more)

Team Foundation: At Work

Do you find yourself tired after sitting in meetings all day? Do you have feelings of uselessness after weeks of bug fixing? Do you often find yourself feeling lonely, as if you've lost touch with your team and the status of your project? Are you frustrated by frequent fire drills and the sense that your project is in utter chaos? Are you hopelessly lost in a sea of changing policies and... (more)