New answers tagged

0 votes

If higher story points represent exponentialy more effort why are they allocated linearly?

I think there is some misunderstanding. A task takes time from start to completion. And once it is completed it takes more time because the spec wasn’t quite right, or there are bugs, or anything else ...
gnasher729's user avatar
  • 44.7k
-3 votes

What Comes First, Project Planning or Requirment Analysis?

Business Case Charter Document Work Breakdown Structure Estimate work package and task durations Develop project schedule and analyze critical path Evaluate results of critical path Reconcile budget ...
Wendy Blomquist's user avatar
2 votes
Accepted

How do you do major changes within an iterative setup?

Its hard to understand what is really your question. But the common issue is that people think about Agile as "chaos". This is not true. Its completely fine even in Agile development to have ...
libik's user avatar
  • 302
2 votes

How do you do major changes within an iterative setup?

Super vague question but I guess the answer is often "You don't" The "Big rewrite" is always something you need to do, but the cost is always very high and there are always other ...
Ewan's user avatar
  • 74.6k
4 votes

Sufficient conditions for refactoring

There's this fact/urban legend that if you put a frog in hot water, it will jump out. But if you put a frog in cold water, it will stay in. If you then heat up the water, the frog does not notice and ...
Flater's user avatar
  • 48.7k
4 votes

Sufficient conditions for refactoring

I've found that many codebases in large companies degrade over time No, I find what degrades is (a) the existence of staff who understand the code, and (b) the correspondence between the ...
Steve's user avatar
  • 8,474
26 votes

Sufficient conditions for refactoring

To enable a codebase to be refactored, the fundamental necessity is test coverage. Ideally fast, automated test coverage. You want to be able to assert, with high confidence after every refactoring ...
Thomas Owens's user avatar
  • 82.4k
6 votes

Sufficient conditions for refactoring

A significant factor is tooling used by the team and the proficiency with which developers use the tools. The concept of refactoring was originally developed in the Smalltalk context, and there were a ...
Hans-Martin Mosner's user avatar
47 votes
Accepted

Sufficient conditions for refactoring

Refactoring takes time. If not done well, it creates bugs that you need to fix. So it costs. You refactor when the benefits outweigh the cost of refactoring. There are good times for refactoring: one ...
gnasher729's user avatar
  • 44.7k
3 votes

Sufficient conditions for refactoring

It really depends on where you are coming from. There is a good argument for "never refactor" if you just look at it on a time cost vs new feature benefit point of view. The common arguments ...
Ewan's user avatar
  • 74.6k
-1 votes

Sufficient conditions for refactoring

My honest answer is that mostly what prevents refactoring is time, i.e. resource availability. Especially in small companies there simply aren't enough bodies to refactor old stuff, what matters is ...
Gigabit's user avatar
  • 217

Top 50 recent answers are included