Talk:Critical Chain Project Management to cope with uncertainty

From apppm
Revision as of 22:18, 22 September 2015 by S145170 (Talk | contribs)

Jump to: navigation, search

Mette: Hello, I like your idea and I like if you would add the topic you have written within the brakets. As you write yourself it would be nice to add something specific/different in the article.

Review3, s150794:

Overall:

  • My first impression of this article is that it is clear and straightforward, and looks good with clearly defined headings and sections, and there are descriptive pictures with explanation.
  • You have a good academic language throughout the article.
  • The article is a bit short, but I see that you have some more topics you want to write about. :)

Abstract:

  • A good introduction to the term, but I'm not sure if you need the first sentence.

Theory of constraints:

  • I like that you start with a short introduction of this topic.
  • It think it is a smart way to highlight the implementation how you use the 5 points from the first paragraph to the next, with an adequate explanation.

Undesired effects of traditional approach:

  • Looks good so far. I look forward to the rest 

Some suggestions for improvement:

  • There are some space between some sentences that may give the text less flow. Tips could be to make the first part of “Theory of construction” to make it to a coherent paragraph.
  • Some sentences that where a bit long, which made it a bit hard to follow. A tip is to either divide of rewrite the sentences. Two examples:
    • “CCPM is an outgrowth of the Theory of Constraints(TOC) and was introduced in 1997 in Eliyahu M. Goldratt’s book, “Critical Chain”[2] in response to many projects resulted in larger duration, increased cost, and less derivable than expected.”
    • “TOC is a systems-management philosophy, originally applied to production system, based on the principle that any system must have a constraint that limits its output.”
  • Some of the sentence had some grammar faults. I would looked a little on sentence structure.
  • In addition to CCPM you could include a paragraph on risk, since you have this in the title.

Reviewer 2, s145170:

Overall:

  • The article clearly follows the “methods” structure, states the topic from the beginning and is compact and to the point.
  • The topic is related to a project, program or portfolio topic
  • Good and clear academic language
  • Figures that correspond to the theory described and cover the main aspects of the topic
  • The transition from the one headline to the other, as well as from sentence to sentence is logical

Abstract:

  • Good description of the context that is directly related to the Method
  • Important that you mention the Critical Path Method, which differs from the CCPM and you will compare them

Theory of constraints:

  • Nice introduction to the topic by stating the relation between CCPM and TOC, which explains why you will analyze the second.
  • Even if you describe the implementation of the “five focusing steps” to Project Management, you could refer to a real-world example, which would be combined with the analysis of the theory that you already did.

Undesired effects of traditional approach:

  • Important that you mention the undesired effects of traditional approaches, so that you strengthen the implementation of yours.
  • I like the example with the student syndrome, as it helps understand what you describe in practice.

Suggestions of improvements

  • As you cover the theory adequately (even if a part is missing, it is clear from the contents), a practical example is needed, maybe in the form of small practical implementations/examples like the “Student Syndrome”, in order to reinforce your theory description.
  • You could also add your own opinion somewhere in the text. As it is difficult to include our own opinion in the description of a theory, you could evaluate the implementation of this theory in a small example, as I proposed one point before
  • Maybe you could avoid some voids between small sentences.
  • If the figures are not yours, you may have to add a reference to avoid copyright problems

Very interesting topic with nice compact structure! I wish you good luck with the rest!

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox