View source for Talk:Mindfulness and Cognitive Biases in Project Management

Anna: In regards to the choice of topic, I feel like this article does not really fit any of the two types of articles that we want to see for this course. An idea could maybe be to focus on a specific tool that could help a manager to be a "mindful manager" in order to narrow the scope of your article down.

----

'''LasseHoier87 reviewer 3'''

The article is not finished as stated in the section ”To the reviewer”. I have therefore not reviewed the part where the author is writing ideas to the rest of the article. I will comment on what is available at the time of the review. 

(Wiki article Peer Review template is used. To see question see "Wiki Article Peer Review and Peer Evaluation")

Formal aspects: 

*It follows the "method" structure in a good and clear way
*Free of grammatical, spelling and punctuation error. Maybe change “We” to more formal style
*Written in a fine engaging style, short sentences also leading nicely to the next point.
*I think the figures is ok, but maybe the figure with a lot of text is not suitable (you have a tendency to skip it) Maybe some bullet points with a very short description would be better?!
*The figures are understandable, but I think “figure 1” should be enlarged. 
*The choice of figures is fine, but the label is missing. Use [[file….|none|thumb|caption]] or similar to get label on the figure 
*The tables and figures is referred to in the text and works fine.
*Regarding copyright on the figures. I can not see any reference in relation to the figures. 
*I think the overall wiki formation of the article is fine. There are some small things, as mentioned earlier, the placement of the figures, layout of figure. But overall the formation is nicely done. 

Content aspects:

*For practitioners the early version may be a bit theoretical, but if some examples of use could be made, the full understanding would be good. 
*I think the article fits the purpose of this course very good. It is dealing with some key issues in term of system engineering and the behavior behind the development towards high complexity in society.
*The article is relating to the project management category. But could be used in other aspects also. The article is categorized well within the content categories.
*It is hard to evaluate the length of the article at this point, but looking at the “thoughts” of the author – I doubt it will too short.
*The logical flow through the article is fine. It seems like there will be a red thread through the rest of the article as well.
*The starting summary of the article should describe the content in a more detailed way. 
*The sources and reference material is illustrated fine in the end of the article, but should of course be completed with “full name of author, title, year etc.”
*The sources and reference material is fine and is mostly relying books, standards and journals. Fine 
*There are no link to other Wiki APPPM articles, but one link to oxford dictionaries, which is of doubtful relevance. 
*Difference between own opinion and statements from literature is hard to say at this point. The article is mostly describing the basic ideas of mindfulness and cognitive biases.
*There is no reason to think there is any type of plagiarism.

----


'''Username: s146898 Reviewer #2'''

Hey :) I really like the topic of your article and I believe it’s an interesting perspective to look at the psychology behind project management. However, I am not entirely sure whether this is a method. The article is not finished and therefore, the feedback will apply mostly to the finished text. However, I did skim through your notes and they seem to be leading in a good direction and it seems the article will be coherent, once it’s finished. 

Formal aspects
*I would say that this article fits into the Explaining or Illustrating a Method type. However, it does not follow the structure suggested for this type of article. Consider clearly describing which is the big picture, what mindfulness means for project management and then go into detail about how it applies. Think about what are its limitations and maybe what are the pros and cons for using it.  
*As far as grammar is concerned, the vocabulary and language are quite neat. However, there are many times in which “are” is used instead of “is” and vice-versa. e.g. “The social intricacy of human behaviour are one of the larger reasons for this change.” “Engineering systems is per definition socio-technical systems”
*I like the use of figures and the fact that they are mentioned in the text. However, Figure 1 is very small and not easily readable. 
*You could consider linking the article to other wikis 

Content aspects
*Personally, I believe practitioners would be very interested in this topic, as human behaviour plays a big role in the complexity of projects. 
*I would reconsider the summary. Maybe introduce the context in which mindfulness is used in project management, the “big picture” 
*I like that your list of references includes relevant books and articles. Don’t forget the Annotated bibliography for each source
*Maybe you’d like to consider a section called “Limitations” as well. 
*Generally, the article seems to have a logical flow. Of course, it is not finished yet…

'''Username: s143352 Reviewer 1'''

Formal aspects:
*The article is written in a good and accurate manner and the reader is well guided through the different sections.
*No gramma faults or spelling.
*The references used throughout the text are from reliable sources (respected universities).
*The figures clarify the content easily, and are quite interesting.
*Figures and pictures are missing references. 
*There is no link to other APPPM wiki article, but perhaps it’s a product of the unique topic?

Content aspects:
*Very interesting reading. I really like the atypical topic. 
*Super input with questions. It holds the reader's attention and gets the reader/project manager to reflect on itself.
*As a proposal could be to bullet point Intuitive vs. rational thinking in project management.Our society primarily honor the rational thinkers, but what about the uncertainty aspects in projects, could the intuitive thinkers have an advantage there?
 
*As a proposal could be to link the article to more practical every day project manager tasks, such as establish project teams, group dynamics etc.

------