Talk:Maslow's Hierarchy of Needs and Project Management

From apppm
Revision as of 14:03, 24 February 2019 by PanosVoun (Talk | contribs)

Jump to: navigation, search

Contents

Feedback on Abstract:

Text clarity & language Ok
Description of the tool/theory/concept The tool/theory/concept is not enough described
Article purpose explanation There is no explanation of the purpose of the article
Relevance to curriculum Make sure you clearly relate it to project, program or portfolio management
References Missing references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
Other The abstract should be a summary of your article. It should combine a description of the tool/theory/concept, its relation to project, program or portfolio management and a clear statement of the purpose of the article.


Feedback 1 | Reviewer name: Panagiotis Vounatsos

Question 1 TEXT

Quality of the summary: Does the summary make the key focus, insights and/or contribution of the article clear? What would you suggest to improve?

Answer 1

The summary is clear and concise, and it presents where the wiki article stands in terms of use for the project manager. The summary could also refer to the perspective of Project Manager and the limitations.

Question 2 · TEXT

Structure and logic of the article: Is the argument clear? Is there a logical flow to the article? Does one part build upon the other? Is the article consistent in its argument and free of contradictions? What would you suggest to improve?

Answer 2

The structure and logic of the article are nice, and the article is of good length. I cannot think of any improvement for this question.

Question 3 · TEXT

Grammar and style:

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

Answer 3

The grammar is clear and understandable

Question 4 · TEXT

Figures and tables:

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

Answer 4

Figures are clearly shown, and properly referenced. There are not any tables in this text.

Question 5 · TEXT

Interest and relevance:

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

Answer 5

The present article can be used both for academic and practical reasons. Both, the theoretical background and the application in project management, are given. Limitations section could be added.

Question 6 · TEXT

Depth of treatment:

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

Answer 6

The article is interesting for a practitioner to read because it provides insight as of how Maslow’s hierarchy of needs can be applied for team management. There is an analysis of all the needs and how project/program/portfolio managers should act for each need. From what I understood from the article, the higher the need in the pyramid it is, the more difficult it is to provide from the perspective of the project manager. I think it would be nice to comment regarding the level of need, up to which a project manager and a company usually tend to cover for their employees

Question 7 · TEXT

Annotated bibliography:

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

Answer 7

''The article cites and acknowledges previous work and presents annotated bibliography. I think that References 4, 5, 6, 8 and 9 are similar in terms of Authors, “Journal”, pages and year. Should it be separately given if they are different paragraphs of the same technical report?

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox