Talk:Managing Successful Programmes (MSP)

From apppm
Revision as of 18:37, 14 February 2018 by Hani Mike Rae Selim (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Abstract Feedback

Text clarity Text is coherent

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

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

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

References Missing appropriate references to mandatory list of references

Relevance of article Consider the following:

  1. Who is the reader? Project Manager or Sponsor ect?
  2. What kind of issues can be tackled using future workshop?
  3. Ensure depth of the article so it contributes to the project management community more than a normal web search
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox