Revision as of 20:53, 25 November 2014

Hermaeus Mora

General

• The article is formatted in a proper wiki fashion. The headings, lists and graphics are used correctly.
• Graphics used are relevant and clear. The 'Stage gate model' is borrowed from an article, it has a reference embedded in the graphic however it's also possible to add references to a figure in wiki. Same regards the 'Gephi network visualization'.
• Regarding the abstract, perhaps it doesn't need a heading and since the APPPM wiki is supposed to be developed over the coming years the phrase "Two years ago" should be put in absolute terms.
• As for the language used. Overall it's understandable, which is good. All the words and expressions are used in the proper context, however...
  • There are multiple grammar errors. Fortunately they are rather small, mostly regarding singular and plural forms, however although small they are still striking for the reader. This should be easily amendable with a grammar check in Word or google docs.
  • The structure of the language is at times informal. There are sentences which can be misinterpreted at first e.g. The system insures low health services prices for all the citizens. while others like For example, a network mapping of the company can enable the directors to be aware of informal links between employees from different department and this can be a good starting point to involve this employees in a cross functional project concerning this departments. should be divided in two for better understanding.
  • I can see that the author uses his/her English to the best possible extent so I would suggest that a native speaker/very proficient user has a quick glance at the text to correct the formulation of some sentences. Quoting The Ghost Writer (2010) "Well all the words are there, they're just in the wrong order." (some of them);)

Content

• Personally I found this article a very interesting read. It's relevant to PPPM and describes an ongoing issue.
• The abstract provides a good overview of the articles content.
• The structure is really clear. Author smoothly goes from one part to the other i.e. what is discussed, what's the situation, who's involved, what's the challenge, how to solve it and what will that achieve.
• The article falls under the case study write-up category. It's not just 100% informative though as after the introduction the author covers the possible solutions to the existing problem. It seems like an evaluation made by the author however it might as well be a description of the feedback from an advisor company.
• References. There are five hard references given, however they regard only the tools and concepts described not the actual content. Course 42490 TEMO is referred to yet nothing more than that. This is something that should be addressed because statements such as: "most of them [functional managers] have no skills and experience in project management." should be backed up by some data/references, else they simply become strong opinions. Moreover there is a reference to a software package 'Gephi', it could be nice to have a link to the owner.