Talk:Managing Successful Programmes (MSP): Difference between revisions

From DTU ProjectLab
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
Line 1: Line 1:
==Abstract Feedback==
==Abstract Feedback==


'''Text clarity''' Text is coherent
'''Text clarity''' Good


'''Language'''         Minor errors e.g. "  To achieve this, the '''''he''''' main idea is to sub-divide..." - remove "he"?
'''Language'''         Minor errors e.g. "  To achieve this, the '''''he''''' main idea is to sub-divide..." - remove "he"?


'''Description of the tool/theory/concept''' Good and easy to follow, but how does this relate to project magement rather than just organizational management or day-to-day problem solving at work? This should be emphasized and clarified in the abstract
'''Description of the tool/theory/concept''' Good, but consider going back to basics. Define what program management is and reference standards/material. Also, is it true that ''all'' organizations need good program management? Also, what defines a successful program?


'''Purpose explanation''' Good, but can improved once the article scope is narrowed down to a project management knowledge area or areas. Consider briefly explaining the structure of the article and the points to be discussed to set the reader's expectations
'''Purpose explanation''' Good and sets up the reader's expectations well


'''References'''         Missing appropriate references to mandatory list of references
'''References'''         Missing appropriate references to mandatory list of references
Line 14: Line 14:


<ol>
<ol>
   <li> Who is the reader? Project Manager or Sponsor ect?
   <li> Who is the reader? Program Manager etc?
   <li> What kind of issues can be tackled using future workshop?
   <li> What will the reader get out of this?
   <li> Ensure depth of the article so it contributes to the project management community more than a normal web search
   <li> Ensure depth of the article so it contributes to the program management community more than a normal web search
</ol>
</ol>

Revision as of 17:45, 14 February 2018

Abstract Feedback

Text clarity Good

Language Minor errors e.g. " To achieve this, the he main idea is to sub-divide..." - remove "he"?

Description of the tool/theory/concept Good, but consider going back to basics. Define what program management is and reference standards/material. Also, is it true that all organizations need good program management? Also, what defines a successful program?

Purpose explanation Good and sets up the reader's expectations well

References Missing appropriate references to mandatory list of references

Relevance of article Consider the following:

  1. Who is the reader? Program Manager etc?
  2. What will the reader get out of this?
  3. Ensure depth of the article so it contributes to the program management community more than a normal web search
Retrieved from "http://13.50.150.85/index.php?title=Talk:Managing_Successful_Programmes_(MSP)&oldid=48554"