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.

I would probably be doing lump sum split up over seperate milestones, say 25% first then so on...

MattyD
– MattyD

2011-08-26 01:29:46 +00:00
Commented Aug 26, 2011 at 1:29
@MattyD - If you do that place a timeline on how long they have to accept a given milestone. Otherwise they could in theory next accept the next milestone. This would lead you say 50% into a project, and in an effort to complete the milestone, they slowly make the milestone into something they could actually use. You also would need to determine how it would be delevered.

Ramhound
– Ramhound

2011-08-26 14:57:09 +00:00
Commented Aug 26, 2011 at 14:57

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 »