Talk:Project Management Reporting

Feedback on Abstract:

Text clarity & language	The text is coherent.
Description of the tool/theory/concept	Very good. It's also good to describe the benefits of reporting. Perhaps consider good/bad examples of reporting (if it makes sense to add)?
Article purpose explanation	Well elaborated. However, could you specify the target audience (e.g. project managers/team members)?
Relevance to curriculum	Very relevant - keep it up.
References	Good references - keep referencing.

Feedback 1 | Reviewer name: Daniel Vorting

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

I think the abstract is good. I like that you elaborate on communication as an important part of project management and thus clearly state the relevance of the article in regards to project management. I like that you point out that PRINCE2 is a widely used method, but you acknowledge that a number of different methods exist. You could consider seperating the 7 steps of the process into bulletpoints for easier readability. I think you should consider writing a little more in-depth on where your theory will be applied. E.g. saying 'project reporting is especially important in this or that situation - that would further increase the readers curiosity and let them know the exact importance and relevance of the article. Overall good abstract that explains why reporting is important, and how you are going to elaborate on it later in the article. Little note: line 4 says 'import' and i think you mean important :-)

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

A bit hard to elaborate on, when the article is only half-finished. But i believe the proposed flow of the article with theory on the project manager role, and a nice walkthrough of the important aspects of the different reports, and what they should contain. I would definitely say the chapters build upon each other. But you do need to write a lot more theoretical content to support your article, but i suspect that is what the 'reporting according to PRINCE2 standards is for (where you've written missing the first steps). The written arguments I consider to be quite consistent and well written but i suggest you write some more.

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

Generally well written. I consider the grammar to be fine - a few misses (an/a) and the one mentioned above in answer 1. I think your language is rather precise and easy to read. I would however consider removing the 'by reading this article it can be concluded that...' in your limitations. It is a lot of unnecessary words. You can easily start the sentence right on 'By having consistent reporting...' and it would still make fine sense. Your sentences have a tendency to be a bit long, but I have a problem with that myself, so i know it is hard to deal with :-)

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

No figures or tables are used in this article. I would consider using some to give a better overview - maybe an example of a template, as you write about in the checkpoint report

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

I believe what the author is aiming towards is a practical relevance of the article. By outlining what is relevant to include in the reports, a project manager can make concrete use of this article. I find the academic relevance a little harder to find, but i believe it might just be because the state-of-the-art chapter is not yet finished. I think the abstract quite clearly describes the relevance of the article. I suggest you approach the article a little more academically in your first chapter in order to balance out the practical and academic perspectives.

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

I believe the article to be interesting for a practitioner to read. However as mentioned above i think the article is a little thin on the academic contribution side. I believe the article is leaning a bit too much against the PRINCE2 book (Axelos). I did a quick search for 'managing project reports' and quickly found an article that describes the different reports (https://blog.learningtree.com/managing-project-communication-using-prince2-part-3-of-3/). So what you really need to focus on is how you differ from just outlining the reports and their content, towards how and where this should be applied. Take a step back and reflect on why this is a good method for handling communication in a project and support it with academic references.

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

Previous work is well references. No summarizing of articles. The article clearly based on empirical data and not opinion. I suggest you find a few more references to give increase the validity of your arguments.