Tag Info

New answers tagged

2

One way of looking at velocity is to think of it as "the amount of work that can be completed in a given amount of time". Assuming that fixing technical debt is actual work, it should be counted. You must remember that velocity is just a tool to help you work better. If adding technical debt to you velocity helps you, do it. If it doesn't, don't. The only ...


4

Velocity is defined as "number of units of work completed in a certain interval". To implement a unit of work, you typically have an existing part of software and add some new code and/or change some existing code. When the existing part of software contains a lot of technical debt, and you have to deal with it to implement a change, one would expect to need ...


1

The value of refactoring cam be measured like so: currently new feature x will cost 5 devs 2 weeks. If we refactor y old component, the cost of new features will be reduced by an estimated 20%. So new feature x will only cost 4 devs over 5 weeks. Refactoring is an investment in reducing the cost of future developments. If you can't make that argument for ...


2

I think the point the other answers miss is you need to measure the cost of refactoring against the lost revenue from not refactoring. Refactoring for the sake of changing code is a waste of time. It needs to bring value to the table. In this context I do not mean spending an hour refactoring a problem class, but the major refactoring such as changing to a ...


1

Benefits of having a refactored system You make a business case for refactoring by comparing the business bottom-line benefits between doing and not doing it. It means either reduction of current real costs, or an increase in future real cash inflow. The key budget items affected by refactoring are the follows: Maintenance costs - if the current system ...


37

It will earn the company F million pounds, over t years at a cost of x dev-days work Which is ignoring maintenance costs, support costs, the cost of sales/marketing, and makes a whole lot of assumptions about how the feature will be taken in the marketplace. But whatever; your question is clear enough about what you're looking for: How can I make a ...


3

Firstly, you need to estimate the dev cost for the re-factoring as you would the sales driven feature request. This may well be tricky to get accurate if it's a large job but, assuming you have sufficiently experienced people in the 2 technologies, it should be doable. Secondly, you need an estimate of the cost of not re-factoring. If you were doing the ...


2

The value of refactoring comes up in multiple different ways. It helps you make other changes later, so the X days the that feature would have taken would now take 2/3X days to complete. To use the agile terminology it increases velocity. The explicit change listed would over time help since you would no longer need to maintain developers with VB6 ...


10

The question you should ask yourself is how is the salesperson know that the feature will cost x developer-days of work. Given that even good project managers with years of professional experience cannot often tell that, such data coming from a salesperson seems extremely... speculative. According to my experience, salespersons usually don't make estimates, ...



Top 50 recent answers are included