Talk:Application of Antifragility in Project Management
From apppm
(Difference between revisions)
| Line 7: | Line 7: | ||
* I didn't find really any grammar mistakes which is good. | * I didn't find really any grammar mistakes which is good. | ||
* Are the first chapters part of abstract or introduction or what.. You could elaborate little bit more with headings in the start so it would be easier to reader to follow the text. | * Are the first chapters part of abstract or introduction or what.. You could elaborate little bit more with headings in the start so it would be easier to reader to follow the text. | ||
| − | * In the article there is often mentioned number 1 and then bulletpoints | + | * In the article there is often mentioned number 1 and then bulletpoints. For example The definition of a good system is: |
1.* The amount of errors within the system is small | 1.* The amount of errors within the system is small | ||
*Each individual error is small, and will not cause a chain reaction (a small error should not lead to a bigger one) | *Each individual error is small, and will not cause a chain reaction (a small error should not lead to a bigger one) | ||
| − | * Negatively correlated to each other (lowering the odds for future errors each time a error is detected) | + | * Negatively correlated to each other (lowering the odds for future errors each time a error is detected) |
Revision as of 13:47, 22 September 2015
Josef: Hello, I really like your idea of looking at antifragility and its application in project management. However, I am not entirely sure if your discussion of "simulating failure scenarios" and "upside/downside risks" fits the heading. If you look at our PMI whitepaper, you will find a few categories/principles of Antifragiltiy and their application to project management. Nassim Taleb's book (which I reckon you must read if you were to write about Antifragility) contains many more possible points of "connection". I suggest to take that as a "point of departure", and see what you can apply how to project management.
Feedback of s141506, Reviewer 2
Structure
- I didn't find really any grammar mistakes which is good.
- Are the first chapters part of abstract or introduction or what.. You could elaborate little bit more with headings in the start so it would be easier to reader to follow the text.
- In the article there is often mentioned number 1 and then bulletpoints. For example The definition of a good system is:
1.* The amount of errors within the system is small
*Each individual error is small, and will not cause a chain reaction (a small error should not lead to a bigger one)
* Negatively correlated to each other (lowering the odds for future errors each time a error is detected)
