Talk:Meetings Management

From apppm
Revision as of 22:26, 13 February 2018 by Hani Mike Rae Selim (Talk | contribs)

Jump to: navigation, search

Abstract Feedback

Text clarity Text is coherent

Language Good, but try to write shorter and more concise scentences

Description of the tool/theory/concept Easy to follow

Purpose explanation Elaborate on the purpose of the article - what will the reader get out of this/learn? Briefly explain the structure of the article in the abstract to set reader 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 etc?
  2. Add more context around project management e.g. meetings the Project Manager organizes and leads with the project steering group
  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