Talk:Theory of Constraint
| Line 11: | Line 11: | ||
Mistakes : | Mistakes : | ||
“an” => and in the Abstract | “an” => and in the Abstract | ||
| + | |||
“ ) “ in 1.1 without “ ( “ | “ ) “ in 1.1 without “ ( “ | ||
| + | |||
“TOC in very process” | “TOC in very process” | ||
| + | |||
I’m quite sure it is “Six Sigma” instead of “Sex Sigma”. | I’m quite sure it is “Six Sigma” instead of “Sex Sigma”. | ||
| + | |||
I think that the referencing throughout the article is really well done. The flow of the article makes it quite easy to read overall, but some sentences should be shorter or rewritten for example : | I think that the referencing throughout the article is really well done. The flow of the article makes it quite easy to read overall, but some sentences should be shorter or rewritten for example : | ||
| − | + | “The rope is a signal generated by the constraint indicating that some CTs have been consumed which triggers the start for new CTs to be processed in the flow.” | |
Basically I think that some work on the syntax have to be done. | Basically I think that some work on the syntax have to be done. | ||
Finally I think the presentation is various and not too monotonous which is really great. | Finally I think the presentation is various and not too monotonous which is really great. | ||
| Line 35: | Line 39: | ||
*Conclusion and advices: | *Conclusion and advices: | ||
The subject is fully treated and well presented with a reduced amount of words, therefore it could be great to add more content regarding the possible extension or future development of the methods, original applications or your own point of view well argued. | The subject is fully treated and well presented with a reduced amount of words, therefore it could be great to add more content regarding the possible extension or future development of the methods, original applications or your own point of view well argued. | ||
| − | + | On the other hand, adding more examples in order to make the theory more accessible and visible can, I think, also be a great option. It could also clarify the connection with program, project or portfolio management. | |
Of course, the translation from Word to Wiki has to be done properly in order to ensure a good visibility for the article. | Of course, the translation from Word to Wiki has to be done properly in order to ensure a good visibility for the article. | ||
Revision as of 20:18, 22 September 2015
Josef: Jane, I like the idea. Make sure to stick to the structure we propose for "methods" articles. I am looking forward to reading about the application of TOC in project management!
Reviewer 3, Damien
This article was accessed the 22/09/2015 16:00
- Overall overview.
There are no Wiki functions used and no figures. However a word version was available for this review. The amount of text doesn’t fulfil the 3000 words required, so addition have to be made in terms of content. The plan and the structure of the article allow a reader to fully understand the concept without specific prerequisite knowledge.
- Formal aspect.
Mistakes : “an” => and in the Abstract
“ ) “ in 1.1 without “ ( “
“TOC in very process”
I’m quite sure it is “Six Sigma” instead of “Sex Sigma”.
I think that the referencing throughout the article is really well done. The flow of the article makes it quite easy to read overall, but some sentences should be shorter or rewritten for example :
“The rope is a signal generated by the constraint indicating that some CTs have been consumed which triggers the start for new CTs to be processed in the flow.”
Basically I think that some work on the syntax have to be done.
Finally I think the presentation is various and not too monotonous which is really great.
- Schemas and photos
I believe the tables furnished interesting content but gather a lot of text and could therefore be resumed or more precisely introduced. The positioning of the figures and tables cannot be judge at this point but the word version seems great to me.
- Links, connections and comprehension.
The article describes step by step the methods while considering literature reference. I think that provides a simple and great comprehension of the topic. The example is more than welcomed in the article, in order to complete the content, it may be a good idea to try to find another spot in order to introduce a practical example of how TOC can be used in a project ( even if it is necessary to oversimplify a situation).
- Bibliography
The references seem to be very serious one. The number of references is satisfying at this point, simply remember to explain for each one how it is relevant to the topic and why it should be consulted by the reader.
- Conclusion and advices:
The subject is fully treated and well presented with a reduced amount of words, therefore it could be great to add more content regarding the possible extension or future development of the methods, original applications or your own point of view well argued. On the other hand, adding more examples in order to make the theory more accessible and visible can, I think, also be a great option. It could also clarify the connection with program, project or portfolio management. Of course, the translation from Word to Wiki has to be done properly in order to ensure a good visibility for the article.
