Talk:Brainstorming technique: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 14: | Line 14: | ||
<ol> | <ol> | ||
<li> | <li> Elaborate how brainstorming is relevant to project/program/portfolio management and not brainstorming in organizational management | ||
<li> Focus on a particular aspect of project/program/portfolio management e.g. when making a business case | <li> Focus on a particular aspect of project/program/portfolio management e.g. when making a business case | ||
<li> Get a clear understanding of who your reader is | <li> Get a clear understanding of who your reader is | ||
<li> Consider alternatives of brainstorming - e.g. "silent brainstorming" | <li> Consider alternatives of brainstorming - e.g. "silent brainstorming" | ||
</ol> | </ol> | ||
Revision as of 16:02, 13 February 2018
Abstract Feedback
Text clarity Text is coherent
Language Good
Description of the tool/theory/concept Easy to follow, but see "relevance of article"
Purpose explanation Good structure, but who is your reader? Is it a project/program/portfolio manager or is the team? Are you focusing on project/program/portfolio management?
References Good. Try adding appropriate references from mandatory list of references, if it makes sense
Relevance of article Needs work. Consider to:
- Elaborate how brainstorming is relevant to project/program/portfolio management and not brainstorming in organizational management
- Focus on a particular aspect of project/program/portfolio management e.g. when making a business case
- Get a clear understanding of who your reader is
- Consider alternatives of brainstorming - e.g. "silent brainstorming"