“This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project.” –Grady Booch, IBM Fellow Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system. Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and “paying off” debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization. Discover how technical debt damages manageability, quality, productivity, and morale–and what you can do about it Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure Identify technical debt items, and analyze their costs so you can prioritize action Choose the right solution for each technical debt item: eliminate, reduce, or mitigate Integrate software engineering practices that minimize new debt Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve.

If you’re trying to kick the “Buy Now/Pay Later” habit and get your spiraling debt under control, you need Managing Debt For Dummies now! This practical, commonsense guide provides straightforward strategies for coping with every kind of secured and unsecured debt, including, personal loans, car loans, mortgages, home equity loans, lines of credit, credit cards, finance company loans, and student loans. You’ll find out how easy it is to: Distinguish between good and bad debt Go on a “debt diet” to get back into financial shape Start a filing system to track debt and protect life after debt Adopt a smart spending regimen Increase your income Consolidate your debt Decide which bills to pay when you can’t pay them all Use credit cards responsibly You can still live well while slashing spending on groceries, clothing, and entertainment. Find out how in Managing Debt for Dummies.

Get out of debt and use credit wisely with this easy-to-understand, comprehensive guide to making your debt work for you. The key to borrowing, managing, and paying off debt is understanding what it is, how it works and how it can affect your finances and your life. Debt 101 is the easy-to-follow guide to discovering how to pay off the debt you have plus learning how to use debt to your advantage. Debt 101 allows you to take control of your money with strategies best suited for your personal financial situation—whether you are buying a home or paying off student loans. You will learn the ins and outs of borrowing in a simple, straightforward manner, managing student loans and credit card debt, improving your credit score, understanding interest rates, good debt vs. bad debt, and so much more. Finally, you can get ahead of the incoming bills and never let your debt intimidate you again!

The underexamined art and science of managing the federal government's huge debt. Everyone talks about the size of the U.S. national debt, now at $13 trillion and climbing, but few talk about how the U.S. Treasury does the borrowing—even though it is one of the world's largest borrowers. Everyone from bond traders to the home-buying public is affected by the Treasury's decisions about whether to borrow short or long term and what types of bonds to sell to investors. What is the best way for the Treasury to finance the government's huge debt? Harvard's Robin Greenwood, Sam Hanson, Joshua Rudolph, and Larry Summers argue that the Treasury could save taxpayers money and help the economy by borrowing more short term and less long term. They also argue that the Treasury and the Federal Reserve made a huge mistake in recent years by rowing in opposite directions: while the Fed was buying long-term bonds to push investors into other assets, the Treasury was doing the opposite—selling investors more long-term bonds. This book includes responses from a variety of public and private sector experts on how the Treasury does its borrowing, some of whom have criticized the way the Treasury has been managing its borrowing.

Examining various methods of debt management used in the US., Handbook of Debt Management, provides a comprehensive analysis of securities offered for sale by municipalities, states, and the federal government. The book covers laws regarding municipal bonds, the economic choice between debt and taxes and the tax-exempt status of municipal bond owners, capital budgeting, including state and local government practices, developing governmental and intergovernmental debt policies, pay-as-you-go with debt financing for capital projects, US Internal Revenue Service regulations on arbitrage in state and local government debt proceeds investment, US treasury auctions, and more.

The practical implications of technical debt for the entire software lifecycle; with examples and case studies. Technical debt in software is incurred when developers take shortcuts and make ill-advised technical decisions in the initial phases of a project, only to be confronted with the need for costly and labor-intensive workarounds later. This book offers advice on how to avoid technical debt, how to locate its sources, and how to remove it. It focuses on the practical implications of technical debt for the entire software life cycle, with examples and case studies from companies that range from Boeing to Twitter. Technical debt is normal; it is part of most iterative development processes. But if debt is ignored, over time it may become unmanageably complex, requiring developers to spend all of their effort fixing bugs, with no time to add new features--and after all, new features are what customers really value. The authors explain how to monitor technical debt, how to measure it, and how and when to pay it down. Broadening the conventional definition of technical debt, they cover requirements debt, implementation debt, testing debt, architecture debt, documentation debt, deployment debt, and social debt. They intersperse technical discussions with "Voice of the Practitioner" sidebars that detail real-world experiences with a variety of technical debt issues.