Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

As a scrum master, we had a developer who constantly argued that every story the team sized was larger than what the team thought, and found realized he wanted to refactor every piece of code he came across. Thus, a 3 point story was always an 8 for him. Clearly this was screwing up the delivery of value. So somehow there needs to be some understanding of when to refactor, and how the decision should be made. Just my thought, from that (and a few other) experience.

Curtis Reed
– Curtis Reed

2017-03-28 18:09:46 +00:00
Commented Mar 28, 2017 at 18:09

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »