Live Webinar December 5, 2011 – 2:00 pm – 3:00 pm EST
Presented by: CollabNet
Duration: 1 Hour + 30 min Question Period 1 Category C PDU – Free PDU

Technical debt isn’t listed on your balance sheet, yet it can destroy your business.

Products carry technical debt when they are difficult or risky to change. The Wall Street Journal recently reported that eBay lost its competitive edge due to nine million lines of bad code that cannot be changed easily.

Is your company next? To thrive in the new economy, you’ll need to adapt your products to your evolving understanding of their requirements as you get feedback from the marketplace.

• Can technical debt be prevented with more enlightened management practices or technical practices?
• Does Scrum make the situation better or worse?

In this session, long-time developer and recovering software architect Michael James explores recent discoveries about technical debt, and what you can do about them.

Presenter: Michael James (LinkedIn profile), CST, CollabNet

PDU Category C documentation details:

Process Groups: Executing

Knowledge Areas: 4- Integration 5 – Scope 11 – Risk

• 4.3 Direct and Monitor Project Execution
• 5.2 Define Scope
• 11.2 Identify Risks

Click to register for Technical Debt: The High Cost of Future Change