Talk:Work Breakdown Structure

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

Jump to: navigation, search

Abstract Feedback

Text clarity Good

Language Good

Description of the tool/theory/concept Good

Purpose explanation Well addressed (e.g. clear that the Project Manager is the reader), but who you mention both projects and programs. It is important to make it clear which one you're referring to in the article as the subject area could differ depending on which one you look at? Or are you comparing WBS in both projects and programs?

References Good

Relevance of article In general the abstract is ok, since WBS is an old topic, when developing the article don't forget to elaborate and describe new developments on the topic and avoid to be too generic. Try to find new trends in the use of WBS.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox