Talk:Lean Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
(Content aspects)
(Content aspects)
Line 58: Line 58:
 
*It is quite clear, that the article is related to one of the proposed content categories.  
 
*It is quite clear, that the article is related to one of the proposed content categories.  
  
*The length of the article seems nice for the in debt description of a whole PM method, including phases. One could question if that is aligned with the idea of a wiki. Wikipedia, for instance, has a labyrinthine set of policies and guidelines summed up in its five pillars: '''Wikipedia is an encyclopaedia''; Wikipedia has a neutral point of view; Wikipedia is free content; Wikipedians should interact in a respectful and civil manner; and Wikipedia does not have firm rules. Encyclopaedia again is defined as: An encyclopedia or encyclopaedia (also spelled encyclopædia, see spelling differences)[1] is a type of reference work or compendium holding a comprehensive summary of information from either all branches of knowledge or a particular branch of knowledge.[2]. When pointing at reference work or compendium of comprehensive summary of information, one could argue that the article is to wide.  
+
*The length of the article seems nice for the in debt description of a whole PM method, including phases. One could question if the in debt description, is aligned with the idea of a wiki. Wikipedia, for instance, has a labyrinthine set of policies and guidelines summed up in its five pillars: '''Wikipedia is an encyclopaedia''; Wikipedia has a neutral point of view; Wikipedia is free content; Wikipedians should interact in a respectful and civil manner; and Wikipedia does not have firm rules. Encyclopaedia again is defined as: An encyclopedia or encyclopaedia (also spelled encyclopædia, see spelling differences)[1] is a type of reference work or compendium holding a comprehensive summary of information from either all branches of knowledge or a particular branch of knowledge.[2].  
  
*The overall flow seems logical and natural as stated before, the only part i would point on is the Perspective part, which should be considered to be moved to the end of the article.
+
*The overall flow seems logical and natural. Hence no suggestions are proposed.
  
*The starting article seem to have a nice size and contains the relevant introduction topic, however it could be nice if the statement will be more sharp. Maybe with concrete areas where the model is used and switch the "can´s" to "as is" or "is".
+
*The starting article seem to have a nice size and contains the relevant introduction topic, however some people may see "Many companies" as somewhat unclear opening statement. This view is surely different and thereby it is meant as discussion point, for general consideration.  
  
*The article provides sufficient sources and reference material, even though some links for further reading.
+
*The article provides sufficient sources and reference material, even though a crosslink and a link for further reading.  
  
*The resources look a like high to good quality reference material. The links are not taken into consideration.  
+
*The resources look a like high to good quality reference material, thus it is hard to define what the article mainly relies on. The links are not taken into consideration.  
  
*The article is linked to another article which describes a method for training purposes according to the content of the article and is thereby highly relevant.
+
*The article is linked to another APPPM wiki
  
 
*Overall the article seems to be quite objective.
 
*Overall the article seems to be quite objective.
  
 
* In general the article seems to be free for copy and paste plagiarism, anyway should the author put attention to review sources and destinations to be absolut sure, that copy paste and plagiarism is avoided.
 
* In general the article seems to be free for copy and paste plagiarism, anyway should the author put attention to review sources and destinations to be absolut sure, that copy paste and plagiarism is avoided.

Revision as of 03:55, 27 November 2014

Contents

Feedback on "Lean Project Management" by DBDHL

This is a great, well written article providing a solid description of Lean Project Management.

Formal aspects

  • The language is nice and easy to understand but proof-reading is recommended.
  • The structure of the article engages the reader. It is well structured and chronologically disposed.
  • The use of figures is great and supports the take-away points from the sections.
  • The figures seem correct, convincing and easy to understand.
  • I suggest adding figure numbers in the figure texts.
  • I suggest referring to the figures throughout the text. This hasn’t been done consistently.
  • It is assumed that the author has created the figures by him-/herself and that there are no copyright issues.
  • The article is very well formatted Wiki-style.
  • References are used consistently and correctly and seem to cover the topic to a great extent.

Content aspects

  • It’s great the article starts by explaining the importance of the topic. This is engaging the reader and works as a great appetizer to read more.
  • Consider to include some of the findings from the article so it works as a summary.
  • The topic is assumed to be highly relevant for a practitioner considering to apply Lean project Management within an organization.
  • It is clear that the article belongs to the “Introduction and overview” category since it takes care of the proposed elements.
  • The length of the article seems appropriate. The article seems to cover the topic to a great extent without being too “heavy” to read.
  • There is a great chronological red thread throughout the article as well as a nice overview.
  • References are in general used extensively with relevant sources of high quality.
  • The article has a section referring to other Wiki pages, which is great.
  • It can be a bit difficult to distinct between own opinion and statements from literature:
    • From the top section: Using “our” in the following sentence makes it seem like it is written by a company and is a bit confusing: “Competition in our industry increasingly makes more important the desire of optimizing what leads to provide our customers better service or product…”
    • From the discussion: “LPM philosophy would become an important part of the companies’ culture because they would see the long-term benefits of applying LPM tools and techniques” – where does this statement come from?
  • The article doesn’t seem to have “copy/paste” plagiarism.


Feedback on "Lean Project Management" by Linus R.V

Well structured, into deep written big article, which immerse the reader into the world of Lean and the Lean Way of project Management

Formal aspects

  • In general the article seem to be free of spelling errors. However, there is a minor constant issue related to the grammar, this issue is constant throughout the article. The article would improve further immediate, by solving that issue.
  • The article is well written, with only minor issues regarding long-winded, hard-to-follow sentences.
  • The flow of the article seems natural and leaves no space for confusion.
  • The figures are meaningfull and appropriate. It would be nice if they were directly linked to the sections were the topic related to a specific figure is explained.
  • The figures also seem to be free for errors in the graphics. Further there is however a issue related to the references in the figures, where a single one of them (PMI-Phase delivery model) points at the PMBOK GUIDE in the description of the figures, where the rest is relation free. That needs to be aligned.
  • Are the figures re-drawn or directly copied from others content?. If they are directly from other content, consider some actions according to your protection from copyright claims.
  • The article is formatted correctly. The appeareance of the figures on the other hand, looks like to have some room for improvement according to size and alignment in the article and each other.

Content aspects

  • Since the article is describing Lean and How to manage projects in a Lean way, the assumption is made that the article is of highly interest for a practitioner.
  • The article describes Lean and How to manage projects in a Lean way into debt, with propper phase descriptions and the evaluation of tools. Thereby the article highly relates to a project management topic. When that is said, the direct link or interaction with general project, programme and portfolio management methods is minor or not existing and may put LPM in the light of a stand alone approach.
  • It is quite clear, that the article is related to one of the proposed content categories.
  • The length of the article seems nice for the in debt description of a whole PM method, including phases. One could question if the in debt description, is aligned with the idea of a wiki. Wikipedia, for instance, has a labyrinthine set of policies and guidelines summed up in its five pillars: 'Wikipedia is an encyclopaedia; Wikipedia has a neutral point of view; Wikipedia is free content; Wikipedians should interact in a respectful and civil manner; and Wikipedia does not have firm rules. Encyclopaedia again is defined as: An encyclopedia or encyclopaedia (also spelled encyclopædia, see spelling differences)[1] is a type of reference work or compendium holding a comprehensive summary of information from either all branches of knowledge or a particular branch of knowledge.[2].
  • The overall flow seems logical and natural. Hence no suggestions are proposed.
  • The starting article seem to have a nice size and contains the relevant introduction topic, however some people may see "Many companies" as somewhat unclear opening statement. This view is surely different and thereby it is meant as discussion point, for general consideration.
  • The article provides sufficient sources and reference material, even though a crosslink and a link for further reading.
  • The resources look a like high to good quality reference material, thus it is hard to define what the article mainly relies on. The links are not taken into consideration.
  • The article is linked to another APPPM wiki
  • Overall the article seems to be quite objective.
  • In general the article seems to be free for copy and paste plagiarism, anyway should the author put attention to review sources and destinations to be absolut sure, that copy paste and plagiarism is avoided.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox