DTU ProjectLab - User contributions [en-gb]

Talk:Managing habits in a project

2019-02-20T07:56:09Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Really good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Good but when you know the specifi..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good but when you know the specific tool you can mention it in your abstract
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good
|-
|'''Other'''|| In the last phrase you write specific tools and methods will be explained in the article. Be careful not trying to cover too many.Your structure of the article looks good so far!
|}

Talk:Key performance indicator (KPI)

2019-02-20T07:34:02Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| OK but remember to correct your misspellings |- |'''Description of the tool/theory/concept'''|| G..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| OK but remember to correct your misspellings
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good but try to relate it more to project, program or portfolio management
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Make sure to relate KPIs to project, program or portfolio management instead of the organisation in general
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''||
|}

Talk:Resources

2019-02-19T14:50:18Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Yes it's coherent
|-
|'''Language'''|| Good but a few misspellings
|-
|'''Description of the tool/theory/concept'''|| What is it exactly the article will focus on? Looking at the processes you mention in the end, be careful not to make the wiki too broad. As an example "managing teams" has its own wiki so trying to fit that and all the other can be too much. Consider choosing one Project Ressource Management Tool
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Ok but could be more specific as Resources in Project Management if that is your focus
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| The Abstract is too long so consider deleting the questions.
|}

Talk:Risk identification methods

2019-02-19T14:33:49Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| OK but could be a bit more clear |- |'''..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| OK but could be a bit more clear
|-
|'''Purpose explanation'''|| Good but you switch from focusing on risks in projects to focus on programs afterwards its a bit confusing. Is the article about both or one of them?
|-
|'''Title of the Wiki'''|| Good but could also be Risk Identification Methods in Project Management if that's your focus
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
If you are in doubt about how to make them in the wiki then have a look at the "Help" function in the side of the page or look at previous years articles. If you click "edit" in one of the old ones you can see how it is done but please do not change anything.
|-
|'''Other'''|| Abstract should be the first. Consider only writing about risk identification methods in either project, program or portfolio management.
|}

Talk:What is SWOT

2019-02-19T14:04:02Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good - few misspellings and avoid writing "We" |- |'''Description of the tool/theory/concept'''||..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good - few misspellings and avoid writing "We"
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| I can see that you relate SWOT to project management so remember to mention it in the abstract too
|-
|'''Title of the Wiki'''|| Remember the question mark -> What is SWOT? but you could also call it The use of SWOT in Project Management if thats your focus
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
If you are in doubt about how to make them in the wiki then have a look at the "Help" function in the side of the page or look at previous years articles. If you click "edit" in one of the old ones you can see how it is done but please do not change anything.
|-
|'''Other'''||
|}

Talk:Evolutionary purpose as motivational driver in project and programme management

2019-02-19T13:32:11Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Good |- |'''Purpose explanation'''|| Good..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| I know you got the title from the Excel sheet but consider only writing about evolutionary purpose in project management or program management and not both
|}

Talk:Use of Business Model Canvas to Kickstart the project management

2019-02-19T13:09:52Z

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant as long as the focus is how BMC is used in project management
|-
|'''References'''|| Really good that you reference to other wikis! For the other references here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Be careful not trying to cover too much but consider only mentioning BMC for kickstarting one of the project management methods
|}

Talk:Programmification of work

2019-02-19T13:05:36Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Good but it would be good with more detai..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good but it would be good with more details and you have space for it since the abstract is a bit short
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good
|-
|'''Other'''|| The abstract is a bit short.
|}

Talk:Prince2

2019-02-19T12:43:05Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Good but the abstract is a bit short so y..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good but the abstract is a bit short so you have space to explain further
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Abstract is a bit short
|}

Talk:Outcome

2019-02-19T12:39:29Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Not that clear |- |'''Language'''|| OK |- |'''Description of the tool/theory/concept'''|| Not sure what the article will ac..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Not that clear
|-
|'''Language'''|| OK
|-
|'''Description of the tool/theory/concept'''|| Not sure what the article will actually contain
|-
|'''Purpose explanation'''|| Not that clear
|-
|'''Title of the Wiki'''|| Could be more descriptive.
|-
|'''Relevance to curriculum'''|| Yes since you focus on project management.
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| The abstract is too short. Have a look in the Course Handbook where the suggested structure is mentioned.
|}

Talk:Outcome, output, benefit

2019-02-19T12:11:49Z

Ebkh:

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Not that clear
|-
|'''Purpose explanation'''|| OK
|-
|'''Title of the Wiki'''|| OK but the title could be more specific.
|-
|'''Relevance to curriculum'''|| Relevant. Good you decided to focus on one of the types of management and not all of them.
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| The abstract is too short. Have a look at the recommended structure for the wiki in the Course Handbook. What will the reader gain more than an explanation the words outcome, output and benefit?
|}

Talk:Epistemic vs. Aleatory uncertainty

2019-02-19T12:00:19Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good
|-
|'''Other'''|| Are you focusing on project management or project, program and portfolio management? You could narrow your topic to one of them.
|}

Talk:Epistemic vs. Aleatory uncertainty

2019-02-19T12:00:06Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| - Good |- |'''Language'''|| - Good |- |'''Description of the tool/theory/concept'''|| Good |- |'''Purpose explanation'''|| ..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| - Good
|-
|'''Language'''|| - Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good
|-
|'''Other'''|| Are you focusing on project management or project, program and portfolio management? You could narrow your topic to one of them.
|}

Talk:Cost Control

2019-02-19T11:52:48Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Not that clear |- |'''Language'''|| OK |- |'''Description of the tool/theory/concept'''|| Not clear what the article will ..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Not that clear
|-
|'''Language'''|| OK
|-
|'''Description of the tool/theory/concept'''|| Not clear what the article will actually contain and what methods are just mentioned briefly
|-
|'''Purpose explanation'''|| OK
|-
|'''Title of the Wiki'''|| It is a broad titel and it looks like you focus on project management so you could write Cost Control in Project Management
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| I'm not sure what you want to include in your article. You mention a lot of different methods so be careful not to make the article too broad
|}

Talk:Cash flow and milestone payments

2019-02-19T10:43:53Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good but with a few misspellings
|-
|'''Description of the tool/theory/concept'''|| Could be more clear. Could decide to choose either project, program or portfolio management
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good but if you decide to choose one either project, program or portfolio then you could write e.g. Cash Flow and Milestone Payments in Project Management
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Change the order between the abstract and the introduction so the abstract is first.
|}

Talk:Scheduling: Critical path, PERT and Gantt

2019-02-19T10:26:09Z

==Feedback on Abstract:==
{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| OK but could mention something about a comparison or the fact that the article is made to help choosing the right method
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| You need a headline for the abstract and the "content box" is before the abstract and the abstract is a bit long. This topic very broad. If you go for it then focus on which method to choose depending on the project and the comparison of the methods since this it what is useful for the reader. So focus on your part 2 and keep 3,4,5 to a minimum. Otherwise it might be better to focus your article so it is not too broad. Let me know if it does not make sense.
|}

Talk:The Triple Constraint in Project Management

2019-02-19T10:09:05Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good - few misspellings though |- |'''Description of the tool/theory/concept'''|| Good |- |'''Pur..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good - few misspellings though
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good but a looks like you are missing references in the first line
|-
|'''Other'''||
|}

Shannon & Weaver Model for Communication

2019-02-19T10:06:31Z

Ebkh: /* Abstract */

'''Using the same reference again and caption doesn't work.... '''
== Abstract ==

Communication is an essential factor in project management and is defined as the exchange of information, intended or involuntary <ref name="Pmbokguide">"Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Fifth Edition; 2013 " </ref>. Successful communication is affected when what is implied is perceived as intended. Communication within project management seen as a foundation function that integrates the areas of scope, schedule and resources <ref name=''Zulch''> ''Zulch, B. Communication: The Foundation of Project Management. Procedia Technology. 2014 Oct; 16: 1000-10009'' </ref>.
Ineffective communication can therefore lead to misunderstandings and to a failure of a project. For that reason, an effective communication system and a fundamental understanding of the project manager to the communication maintenance during the life cycle of a project are mandatory for a successful project <ref name="Pmbokguide" />.
Thus, a solid understanding of communication and developed skills to communicate are necessary for project, programme or portfolio manager to ensure the potential for cooperation and an effective communication within the project team and with external stakeholders.

The following article looks into the basic model of communication and its components which is known as the ''Shannon and Weaver Model for Communication''. This model is often referred as the ''Mother of all Models'' '''REF''' and was primary designed to improve technical communication of radio and telephone. <ref name=''Shannon1948''> ''Shannon, C.E. A Mathematical Theory of Communication. The Bell System Technical Journal. 27; 1948: (July and October): 379–423, 623–656'' </ref> Later, the model was used in order to understand and develop effective communication as it offers insights in the way in which communication is designed.
After a detailed model description, the three levels of problems according to Shannon and Weaver will be elaborated as well as the application and the limitation of this model.

== Model Description ==

In 1948, the first major model for communication system was developed by Claude Elwood Shannon and published as "A Mathematical Theory of Communication" in The Bell System Technical Journal <ref name=''Shannon1948''/> . One year afterwards, the book was edited with an additional introduction by Warren Weaver and the article was published as “The Mathematical Theory of Communication” in The Bell System Technical Journal <ref name=''Shannon1949''> ''Shannon, C.E., Weaver, W. A Mathematical Theory of Communication. The Bell System Technical Journal. 1949" </ref>. The content of the work was to identify the quickest and most efficient way to get a message from one point to another. Their goal was to discover how communication messages could be converted into electronic signals most efficiently, and how those signals could be transmitted with a minimum of error. Originally, this study was designed under a technical aspect and was formulated as a binary mathematical model. <ref name=''Shannon1948''/> <ref name=''Shannon1949''/>
In 1964, C. E. Shannon and W. Weaver extended their first paper with more mathematical aspects and suggested some ideas for a broader application of the fundamental principles of communication theory. <ref name=''Shannon1964''> ''Shannon, C.E., Weaver, W. A Mathematical Theory of Communication. Champaign, IL, US: University of Illinois Press. 1964'' </ref> Eventually, it became the most well-know and basic model of communication, the ''Shannon and Weaver Model for Communication''.

The Shannon and Weaver Model of Communication represents the communication process in a linear form which involves a one-way communication with others (sender and receiver). The model deals with six basic elements which form the general communication system according to Shannon and Weaver. <ref name=''Shannon1964''/>

=== Basic Elements ===
[[File:General Communication System.png|500px|Figure 1: General Communication System. Inspired by Shannon and Weaver Model of Communication <ref name=''Shannon1964''/>.]]

'''Sender''' 
'''Encoder''' 
'''Channel''' 
'''Decoder''' 
'''Receiver''' 
'''Noise''' 

=== Example ===

=== The Levels of Problems for Communication ===

'''Level A''' 
'''Level B''' 
'''Level C''' 

== Application ==

== Limitations ==

== References ==
<references />

== Annotated bibliography ==

*'''A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Fifth Edition, 2013'''
''Chapter 10'' - The chapter Project Communication Management describes the process of the three steps in order to develop a strategy and implement a communication strategy. Fundamental definitions and tools are also presented in this chapter.

Talk:Getting Things Done (David Allen)

2019-02-19T09:20:48Z

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| It is not related to project, program or portfolio management
|-
|'''Title of the Wiki'''|| A new title could be relevant if you adapt the article to project, program or portfolio management
|-
|'''Relevance to curriculum'''|| How does it relate to project, program or portfolio management? Try to make it related to project management
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|}

Talk:Create a pitch

2019-02-19T09:12:21Z

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Not clear how it is related to project, program and/or portfolio management
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| The topic has to be related to project, program or portfolio management and it is not.
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|}

Talk:Resource-Constrained Critical Path Method

2019-02-19T09:05:51Z

Talk:Project Management: Cost vs. Price

2019-02-19T08:50:16Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good but could also be cost and price in project management
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| The abstract is a bit short so if you want to be a bit more specific you have space.
|}

Talk:Project Management: Cost vs. Price

2019-02-19T08:49:27Z

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| The abstract is a bit short so if you want to be a bit more specific you have space.
|}

Talk:Performance-based contracting

2019-02-19T08:31:28Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Could be more clear
|-
|'''Purpose explanation'''|| OK
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Remember to make it clear that it is related to project, program or portfolio management
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Make sure not to follow the same structure as the Wikipedia article about the same topic
|}

Talk:Performance-based contracting

2019-02-19T08:31:11Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Could be more clear |- |'''Purpose explan..."

Talk:Resource allocation and crashing

2019-02-19T07:57:16Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Ok but could be more clear |- |'''Language'''|| OK but a few misspellings. |- |'''Description of the tool/theory/concept'''..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Ok but could be more clear
|-
|'''Language'''|| OK but a few misspellings.
|-
|'''Description of the tool/theory/concept'''|| Could be more clear
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| It is good that you limit to project management.
You mention that you will describe three techniques. Remember it is better to describe fewer things in depth than a lot superficially.
|}

Talk:Benefits Realisation Management (BRM)

2019-02-19T07:45:07Z

Ebkh: Created page with "{| |'''Text clarity'''|| OK |- |'''Language'''|| Some mistakes. Avoid writing his or hers about the method. |- |'''Description of the tool/theory/concept'''|| Good |- |'''Pur..."

{|
|'''Text clarity'''|| OK
|-
|'''Language'''|| Some mistakes. Avoid writing his or hers about the method.
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| I am not sure if you focus on program management or it will be about project, program and portfolio management.
|}

Talk:Meeting Management

2019-02-19T07:19:01Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| OK |- |'''Language'''|| OK with some misspellings |- |'''Description of the tool/theory/concept'''|| Try to make it more cl..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| OK
|-
|'''Language'''|| OK with some misspellings
|-
|'''Description of the tool/theory/concept'''|| Try to make it more clear what the article will contain.
|-
|'''Purpose explanation'''|| Good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Yes but remember to focus on the importance of meeting management in project, program and portfolio management.
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Be careful not to try to cover too much it is better to go more in depth with specific parts.
|}

Talk:Projects integrating Sustainable Methods

2019-02-18T22:50:40Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Really good |- |'''Language'''|| Good - few mistakes |- |'''Description of the tool/theory/concept'''|| Good |- |'''Purpose..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Good - few mistakes
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good but could add the abbreviation too (PRiSM)
|-
|'''Relevance to curriculum'''|| Relevant
|-
|'''References'''|| Good
|-

Talk:Resources

2019-02-18T22:19:16Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| - |- |'''Language'''|| - |- |'''Description of the tool/theory/concept'''|| - |- |'''Purpose explanation'''|| - |- |'''Titl..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| -
|-
|'''Language'''|| -
|-
|'''Description of the tool/theory/concept'''|| -
|-
|'''Purpose explanation'''|| -
|-
|'''Title of the Wiki'''|| Ok but could be more specific as Resources in Project Management
|-
|'''Relevance to curriculum'''|| Yes
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Abstract is missing so I cannot evaluate it. The wiki could be too broad when looking at the structure.
|}

Talk:Shannon & Weaver Model for Communication

2019-02-18T22:01:31Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Really good |- |'''Language'''|| Good |- |'''Description of the tool/theory/concept'''|| Good |- |'''Purpose explanation'''..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Good
|-
|'''Description of the tool/theory/concept'''|| Good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Really good
|-
|'''Relevance to curriculum'''|| Yes
|-
|'''References'''|| Good besides the issue you have. Let us fix it tomorrow in class.
|-
|'''Other'''|| "Mother of all models". In general or is it within communication?
|}

Talk:Types of activities

2019-02-18T21:51:41Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| -
|-
|'''Language'''|| -
|-
|'''Description of the tool/theory/concept'''|| -
|-
|'''Purpose explanation'''|| -
|-
|'''Title of the Wiki'''|| -
|-
|'''Relevance to curriculum'''|| -
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Anstract is missing so I cannot give you feedback. What is the purpose of the article?
|}

Talk:Types of activities

2019-02-18T21:51:25Z

==Feedback on Abstract:==

{|
|'''Text clarity'''|| -
|-
|'''Language'''|| -
|-
|'''Description of the tool/theory/concept'''|| -
|-
|'''Purpose explanation'''|| -
|-
|'''Title of the Wiki'''|| -
|-
|'''Relevance to curriculum'''|| -
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-
|'''Other'''|| Anstract is missing so I cannot give you feedback. What is the purpose of the article?
}

Talk:Benefits Realization Management as a key driver of Project Management Effectiveness

2019-02-18T21:46:25Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Really good
|-
|'''Description of the tool/theory/concept'''|| Really good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good
|-
|'''Relevance to curriculum'''|| Yes
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|}

Talk:Benefits Realization Management as a key driver of Project Management Effectiveness

2019-02-18T21:08:38Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Really good
|-
|'''Description of the tool/theory/concept'''|| Really good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|}

Talk:Benefits Realization Management as a key driver of Project Management Effectiveness

2019-02-18T21:08:09Z

Ebkh: /* Feedback on Abstract: */

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Really good
|-
|'''Description of the tool/theory/concept'''|| Really good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
}

Talk:Benefits Realization Management as a key driver of Project Management Effectiveness

2019-02-18T21:01:00Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| Really good |- |'''Language'''|| Really good |- |'''Description of the tool/theory/concept'''|| Really good |- |'''Purpose ..."

==Feedback on Abstract:==

{|
|'''Text clarity'''|| Really good
|-
|'''Language'''|| Really good
|-
|'''Description of the tool/theory/concept'''|| Really good
|-
|'''Purpose explanation'''|| Really good
|-
|'''Title of the Wiki'''|| Good
|-
|'''References'''|| Remember to make correct references. Here are some guidelines from DTU Library: https://www.bibliotek.dtu.dk/english/servicemenu/find/reference_management/references
|-

Talk:Cash flow and milestone payments

2019-02-18T13:07:38Z

Ebkh: Created page with "==Feedback on Abstract:== {| |'''Text clarity'''|| |- |'''Language'''|| |- |'''Description of the tool/theory/concept'''|| |- |'''Purpose explanation'''|| |- |'''Title of..."

==Feedback on Abstract:==

{|
|'''Text clarity'''||
|-
|'''Language'''||
|-
|'''Description of the tool/theory/concept'''||
|-
|'''Purpose explanation'''||
|-
|'''Title of the Wiki'''||
|-
|'''References'''||
|}

User:S190056

2019-02-15T13:30:17Z