Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-07 Technical debt.

Slides:

Advertisements

Similar presentations

8 Ways to Sweeten Your bid to buy a business without paying more Sunbelt Business Brokers.

Advertisements

Process and Product Quality Assurance (PPQA)

2-1 CHAPTER 2 Financial Statements, Cash Flow, and Taxes Balance sheet Income statement Statement of cash flows Accounting income vs. cash flow MVA and.

2 1. Client protection principles 2. Principle #1 in practice 3. Causes and effects of over-indebtedness 4. Participant feedback 5. Practitioner lessons.

Copyright © 2012 by Mark J. Sebern Technical Debt What is debt (in a financial sense)?

Copyright © 2012 by Mark J. Sebern Product Backlog PBI types (extended list) Feature Change Defect Technical improvement Knowledge acquisition Briefly,

Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity.

CSCI 577B Software Engineering B Technical Debt Ihsan Tolga.

Lecture No.13 Chapter 4 Contemporary Engineering Economics Copyright © 2010 Contemporary Engineering Economics, 5th edition, © 2010.

Contemporary Engineering Economics, 4 th edition, © 2007 When Projects Require Financing Activities Lecture No. 41 Chapter 10 Contemporary Engineering.

Project Support Function PM Planning Organizing Staffing Monitoring Controlling and Leading Project Support Functions Monitoring Controlling.

Developing and Implementing A Marketing Plan Paul E. Patterson and Larry D. Makus University of Idaho Department of Agricultural Economics & Rural Sociology.

SE 450 Software Processes & Product Metrics Software Metrics Overview.

3 - 1 Copyright © 2002 by Harcourt, Inc.All rights reserved. Ratio analysis Du Pont system Effects of improving ratios Limitations of ratio analysis Qualitative.

2-1 CHAPTER 2 Financial Statements, Cash Flow, and Taxes Balance sheet Income statement Statement of cash flows Accounting income vs. cash flow MVA and.

1 Extreme Programming & New Theory of Programming.

CPSC 875 John D. McGregor C20 – Technical Debt. Value-based SE SCS – success-critical stakeholder.

Contemporary Engineering Economics, 4 th edition, © 2007 Debt Management Lecture No.13 Chapter 4 Contemporary Engineering Economics Copyright © 2006.

Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.

The “Need-to-knows” for your financial future. * Do you ever want to buy a car? * Do you ever want to own your own home? * Do you know how debt can impact.

12 Steps to Useful Software Metrics

McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter Seven Accounting for Receivables.

Analyzing Product/Service Risks and Benefits

BPA FY 2003 Financial Condition Update: Liquidity Tools to Bridge the Gap Confidential – Sensitive Information BPA has a number of liquidity tools to bridge.

Software Engineering Process I

+ Chapter 2 The Accounting Equation. + Assets, Liabilities & Owner’s Equity The most obvious place to start an assessment of any business is with its.

SE-280 Dr. Mark L. Hornick 1 Process Adaptations.

Taking Charge of your Time. # Introduction Time management is about managing your day affectively so you can achieve all that you want to achieve. It.

Office 365 & Charts. Office 365 Features Latest versions of Office suites No tension of loosing your work Access from anywhere and on any device Share.

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution.

Feasibility Study.

PHSE - Economic wellbeing and financial capability Lesson 3 – Debt management L.O. – Capability 1.2b - Learning how to manage money and personal finances.

Credit Risk Dr Said Abu Jalala. Introduction Financial institutions have faced difficulties over the years for a multitude of reasons The major cause.

Contemporary Engineering Economics, 6 th edition Park Copyright © 2016 by Pearson Education, Inc. All Rights Reserved Debt Management Lecture No. 13 Chapter.

The Keys to Profitability, Accountability & Efficiency Changing How the Work Gets Done.

Software Engineering Risk Management. Understanding Risks Risks involve :  Uncertainty – there are no 100% probable risks  Loss – if the risk becomes.

1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.

Chapter 3 Project Management Concepts

How RISKY Is This??. How RISKY is This?? Buy a lottery ticket Only 3 will be sold Cost for a ticket $80 million Jackpot $2,000,000,000 Where is the

1 Understanding the Financial Statements Lecture No.35 Professor C. S. Park Fundamentals of Engineering Economics Copyright © 2005.

Capability Maturity Model CS3300 Fall The Problem Contractors over budget and late. Need a way to rank how likely a software company is to deliver.

University of Southern California Center for Systems and Software Engineering Technical Debt Part II CS 577 Software Engineering Supannika Koolmanojwong.

Taking Charge of Your Time Presented by. Time_E_HO.ppt: p. 2 Rev. 01/22/99 Objectives n To increase awareness of your attitude toward time. n To learn.

1 Planning – Agile Style Highsmith, Ch 7 All kinds of iterations! CSSE579 Session 3 Part 1.

Avoiding Financial Trouble Prince William Area Financial Education Program.

Copyright © 2012 by Mark J. Sebern Scrum Overview (from

Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint review and retrospective.

Copyright © by Mark J. Sebern Software Engineering Process I The case for agile processes.

Software Engineering Lecture 6: Risk Analysis & Management.

Financial Statements for a Corporation Chapter 19.

Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.

A Dealing with Dollar $ workshop Understanding Credit and Debt.

Copyright © by Mark J. Sebern Software Engineering Process I SE Technical Practices.

Copyright © 2012 by Mark J. Sebern Sprints Sprint planning Sprint execution.

#7-Effect of Agile on Post-Contract Award Subtopics #1- Documentation #2- Regulatory oversight #3- Participating in Agile reviews #4- Measurement ELO ELO.

Copyright © 2013 by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?

Accounting for Receivables Chapter Seven Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.

Chapter 14 Planning Debt Financing Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.

Swami NatarajanOctober 1, 2016 RIT Software Engineering Software Metrics Overview.

Basics of financial management

Software Engineering Process

Economic Impact on Personal Finances

Software Quality Engineering

Welcome to Corporate Training -1

Unit 5: Personal Finance

Software Engineering Process

Software Engineering Process

Process of Developing Project Cash Flows

Presentation transcript:

Copyright © by Mark J. Sebern Software Engineering Process I SE Technical debt

Copyright © by Mark J. Sebern Technical Debt What is debt (in a financial sense)? Principal, interest, payments, compounding What’s the basic idea of “technical debt”? Is “debt” (always? ever?) a bad thing? Is “debt” (always? ever?) a good thing?

Copyright © by Mark J. Sebern Kinds of Technical Debt Unfit (bad) design Defects Insufficient test coverage Excessive manual testing Poor integration and release management Lack of platform experience Other kinds? Briefly, define each kind

Copyright © by Mark J. Sebern Types of Technical Debt How do the following types differ? Naive technical debt Unavoidable technical debt Strategic technical debt

Copyright © by Mark J. Sebern Consequences of Technical Debt Unpredictable tipping point Increased delivery time Significant # of defects Rising development & support costs Product atrophy Decreased predictabilit y Under- performanc e Universal frustration Decreased customer satisfaction

Copyright © by Mark J. Sebern Causes of Technical Debt Deadline pressure False “acceleration” Decreased verification Cumulative debt effects (decreasing velocity)

Copyright © by Mark J. Sebern Managing Technical Debt Managing debt accrual Making debt visible Servicing the debt

Copyright © by Mark J. Sebern Managing Technical Debt Managing debt accrual Making debt visible Servicing the debt Good technical practices Strong “done” definition Understanding of debt economics (delay vs repayment costs)

Copyright © by Mark J. Sebern Managing debt accrual Making debt visible Servicing the debt Good technical practices Strong “done” definition Understanding of debt economics (delay vs repayment costs) Managing Technical Debt Don’t forget that debt bears interest!

Copyright © by Mark J. Sebern Managing Technical Debt Managing debt accrual Making debt visible Servicing the debt Good technical practices Visibility at the business level (balance sheet) Strong “done” definition Visibility at the technical level (defects, PBIs, cards) Understanding of debt economics (delay vs repayment costs)

Copyright © by Mark J. Sebern Managing Technical Debt Managing debt accrual Making debt visible Servicing the debt Good technical practices Visibility at the business level (balance sheet) Deciding whether to repay Strong “done” definition Visibility at the technical level (defects, PBIs, cards) Repay when found, incrementally, high- interest first Understanding of debt economics (delay vs repayment costs) Repay while producing value (avoid balloon payments)

Copyright © by Mark J. Sebern Review Types of technical debt Consequences Managing technical debt