3 minor spelling correction
source | link

Perhaps a better way of asking what you're getting at is, "when is less iterative and more formal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicaeapplicable everywhere. Very few have no use.

Perhaps a better way of asking what you're getting at is, "when is less iterative and more formal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicae everywhere. Very few have no use.

Perhaps a better way of asking what you're getting at is, "when is less iterative and more formal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicable everywhere. Very few have no use.

2 Corrected 2 typos
source | link

Perhaps a better way of asking what you're getting at is, "when is lessnitwrativeless iterative and morenformalmore formal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicae everywhere. Very few have no use.

Perhaps a better way of asking what you're getting at is, "when is lessnitwrative and morenformal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicae everywhere. Very few have no use.

Perhaps a better way of asking what you're getting at is, "when is less iterative and more formal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicae everywhere. Very few have no use.

1
source | link

Perhaps a better way of asking what you're getting at is, "when is lessnitwrative and morenformal better?"

There are situations where this is the case:

  • When the requirements won't change.

  • When meeting new requirements is less important than hitting 100% of the original ones.

  • When all the technology components are mature and well understood.

In a sense you can take the opposite of what might drive you to be agile.

Very few techniques are applicae everywhere. Very few have no use.