Talk:Financial appraisal of project proposals

From apppm
Revision as of 09:33, 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 Coherent

Language Good, with some minor errors e.g. write "to evaluate" instead of "to evaluates." Re-read the abstract

Description of the tool/theory/concept Easy to follow, but the image is too small to read. In most cases, I would personally recommend to not use diagrams in abstracts, but rather move them to a "background" section where the tool is more thoroughly explained

Purpose explanation Good, but consider: is this tool primarily applied for portfolio or program management?

  1. Is this tool primarily applied for portfolio or program management?
  2. Who is the reader? Project or Program manager or any project team member?

References Missing appropriate references to mandatory list of references

Relevance of article It is relevant. Consider the following:

  1. Try to link it to a knowledge area of project/program/portfolio management
  2. Ensure depth of the article so it contributes to the project/program/portfolio management community more than a normal web search
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox