Talk:Application of Antifragility in Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 8: Line 8:
 
* 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. For example the chapter''' The definition of a good system is  '''. Is it suppose be like this and also the other same kind of chapters?
 
* In the article there is often mentioned number 1 and then bulletpoints. For example the chapter''' The definition of a good system is  '''. Is it suppose be like this and also the other same kind of chapters?
 +
*Maybe samekind conclusion in the end would wrap the text better together. Now it is little bit scattered in different parts.
  
 
== Content==
 
== Content==
Line 15: Line 16:
 
* Like I wrote in structure that try to use more headings.
 
* Like I wrote in structure that try to use more headings.
 
* You have used much New York Times articles as reference, it can be quite one-sided.
 
* You have used much New York Times articles as reference, it can be quite one-sided.
 +
 +
== Overall==
 +
 +
* Good article about subject that for me personal didn't have much information.

Revision as of 15:29, 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.

Contents

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 chapter The definition of a good system is . Is it suppose be like this and also the other same kind of chapters?
  • Maybe samekind conclusion in the end would wrap the text better together. Now it is little bit scattered in different parts.

Content

  • Having the aviation of one example for antifragility is very good. It gives reader immediately better understanding of the whole consept.
  • Pictures are nice looking and simple but still informative. Reader can easily understand what write have wanted to show with the picture.
  • Like I wrote in structure that try to use more headings.
  • You have used much New York Times articles as reference, it can be quite one-sided.

Overall

  • Good article about subject that for me personal didn't have much information.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox