<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>http://13.50.150.85/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=S133654</id>
	<title>DTU ProjectLab - User contributions [en-gb]</title>
	<link rel="self" type="application/atom+xml" href="http://13.50.150.85/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=S133654"/>
	<link rel="alternate" type="text/html" href="http://13.50.150.85/index.php/Special:Contributions/S133654"/>
	<updated>2026-07-14T13:48:14Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.3</generator>
	<entry>
		<id>http://13.50.150.85/index.php?title=Talk:Agile_Project_Management_with_SCRUM&amp;diff=52474</id>
		<title>Talk:Agile Project Management with SCRUM</title>
		<link rel="alternate" type="text/html" href="http://13.50.150.85/index.php?title=Talk:Agile_Project_Management_with_SCRUM&amp;diff=52474"/>
		<updated>2018-02-21T10:10:36Z</updated>

		<summary type="html">&lt;p&gt;S133654: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Abstract Feedback==&lt;br /&gt;
Text Clarity; Ok.&lt;br /&gt;
&lt;br /&gt;
Language; Ok.&lt;br /&gt;
&lt;br /&gt;
References; missing references related to the standards.&lt;br /&gt;
&lt;br /&gt;
In general the abstract is ok, when developing the article don&#039;t forget to elaborate the article based in the sections recomended&lt;br /&gt;
in the point 5, Individual Assignment of the Course handbook and check the Reference Reading material for the Wiki Assignment and Project Work.&lt;br /&gt;
&lt;br /&gt;
==Feedback 1 | Reviewer Name: Cetin Arslan ==&lt;br /&gt;
&lt;br /&gt;
===Question 1===&lt;br /&gt;
&lt;br /&gt;
Quality of the summary:&lt;br /&gt;
 &lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 1===&lt;br /&gt;
Firstly, there are some minor spelling errors all over the text, which can be easily improved e.g. includes instead include or &amp;quot;new product development Game&amp;quot;. &lt;br /&gt;
Secondly, while reading the section to Scrum Process, although the process itself is well described, it would make it understandable of the process itself would be connected to an &amp;quot;example project&amp;quot; in order to give a better description. Third, for me as reader it would be interesting which old-school&#039; project management approaches are meant and described. Fourth, I dont know whether it is necessary to describe the given table again, as all the information is clearly understandable. Fifth, it would be interesting to know, whether the approach is still used in todays industries or was changed and improved for todays needs as it was defined in the 1990s. &lt;br /&gt;
&lt;br /&gt;
===Question 2===&lt;br /&gt;
&lt;br /&gt;
Structure and logic of the article:&lt;br /&gt;
&lt;br /&gt;
Is the argument clear?&lt;br /&gt;
&lt;br /&gt;
Is there a logical flow to the article?&lt;br /&gt;
&lt;br /&gt;
Does one part build upon the other?&lt;br /&gt;
&lt;br /&gt;
Is the article consistent in its argument and free of contradictions?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 2===&lt;br /&gt;
The article has a understandable structure and logic. In some points in the article it would be better to implement small examples in order to make it easier for an unexperienced user. &lt;br /&gt;
The arguments itself are clear as the process itself, also the benefits und limitations of the tool are explained. Further suggestions are given under Question 1. &lt;br /&gt;
&lt;br /&gt;
===Question 3===&lt;br /&gt;
&lt;br /&gt;
Grammar and style:&lt;br /&gt;
&lt;br /&gt;
Is the writing free of grammatical and spelling errors?&lt;br /&gt;
&lt;br /&gt;
Is the language precise without unnecessary fill words?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 3===&lt;br /&gt;
The article itself contains of small spelling errors in nearly every chapter, which the author will surely correct in the second phase. The grammar is nearly without any mistake, and the language used is professional. &lt;br /&gt;
&lt;br /&gt;
===Question 4===&lt;br /&gt;
&lt;br /&gt;
Figures and tables:&lt;br /&gt;
&lt;br /&gt;
Are figures and tables clear?&lt;br /&gt;
&lt;br /&gt;
Do they summarize the key points of the article in a meaningful way?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 4===&lt;br /&gt;
It is very nice that the author build his own tables and figures. Unfortunately the figure seems to be a little blurred. &lt;br /&gt;
Further i would maybe implement the table also as a jpeg file which maybe was created by word or excel which would give a nicer look. &lt;br /&gt;
I would also put in the missing source of the information provided in the table.&lt;br /&gt;
&lt;br /&gt;
===Question 5===&lt;br /&gt;
&lt;br /&gt;
Interest and relevance:&lt;br /&gt;
&lt;br /&gt;
Is the article of high practical and / or academic relevance?&lt;br /&gt;
&lt;br /&gt;
Is it made clear in the article why / how it is relevant?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
===Answer 5===&lt;br /&gt;
The article provides a practical relevance due to its connections to businesses. Examples from businesses using it today would make it even more relevant. Also academic examples would strengthen the article.&lt;br /&gt;
&lt;br /&gt;
===Question 6===&lt;br /&gt;
&lt;br /&gt;
Depth of treatment:&lt;br /&gt;
&lt;br /&gt;
Is the article interesting for a practitioner or academic to read?&lt;br /&gt;
&lt;br /&gt;
Does it make a significant contribution beyond a cursory web search?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 6===&lt;br /&gt;
The article gives a good understandable read. As it is written in a quite professional way it may be to difficult to read for somebody not related to this field. &lt;br /&gt;
Beyond a normal google reason it provides all nearly all necessary information a article with max 3000 words can provide. Suggestions of Question 1 can still further improve it. &lt;br /&gt;
&lt;br /&gt;
===Question 7===&lt;br /&gt;
&lt;br /&gt;
Annotated bibliography:&lt;br /&gt;
&lt;br /&gt;
Does the article properly cite and acknowledge previous work?&lt;br /&gt;
&lt;br /&gt;
Does it briefly summarize the key references at the end of the article?&lt;br /&gt;
&lt;br /&gt;
Is it based on empirical data instead of opinion?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 7===&lt;br /&gt;
Good use of date and citations. Quotes inside the article strengthen the authors logic.&lt;br /&gt;
&lt;br /&gt;
==Feedback 2 | Reviewer Name: Lars From-Hansen ==&lt;br /&gt;
&lt;br /&gt;
Quality of the summary:&lt;br /&gt;
Very good and well annotated. &lt;br /&gt;
Does the summary make the key focus, insights and/or contribution of the article clear?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
I have no suggestions for improvement.&lt;br /&gt;
&lt;br /&gt;
Question 2 · TEXT&lt;br /&gt;
Structure and logic of the article:&lt;br /&gt;
Good structure that is easy to follow.&lt;br /&gt;
Is the argument clear?&lt;br /&gt;
Yes&lt;br /&gt;
Is there a logical flow to the article?&lt;br /&gt;
Yes&lt;br /&gt;
Does one part build upon the other?&lt;br /&gt;
Yes&lt;br /&gt;
Is the article consistent in its argument and free of contradictions?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
In the part about SCRUM meetings it would be nice to clarify who attends the Product planning meeting - only the project team or are stakeholders like the customer attending too?&lt;br /&gt;
Answer 2&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 3 · TEXT&lt;br /&gt;
Grammar and style:&lt;br /&gt;
Good&lt;br /&gt;
Is the writing free of grammatical and spelling errors?&lt;br /&gt;
Yes&lt;br /&gt;
Is the language precise without unnecessary fill words?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
In the first sentence of the SCRUM Process paragraph it says sprinG backlog instead of sprint backlog.&lt;br /&gt;
Answer 3&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 4 · TEXT&lt;br /&gt;
Figures and tables:&lt;br /&gt;
Good&lt;br /&gt;
Are figures and tables clear?&lt;br /&gt;
Yes&lt;br /&gt;
Do they summarize the key points of the article in a meaningful way?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
Nothing.&lt;br /&gt;
Answer 4&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 5 · TEXT&lt;br /&gt;
Interest and relevance:&lt;br /&gt;
Good.&lt;br /&gt;
Is the article of high practical and / or academic relevance?&lt;br /&gt;
Yes&lt;br /&gt;
Is it made clear in the article why / how it is relevant?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
Answer 5&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 6 · TEXT&lt;br /&gt;
Depth of treatment:&lt;br /&gt;
Good&lt;br /&gt;
Is the article interesting for a practitioner or academic to read?&lt;br /&gt;
Yes&lt;br /&gt;
Does it make a significant contribution beyond a cursory web search?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
Answer 6&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 7 · TEXT&lt;br /&gt;
Annotated bibliography:&lt;br /&gt;
&lt;br /&gt;
Does the article properly cite and acknowledge previous work?&lt;br /&gt;
Yes&lt;br /&gt;
Does it briefly summarize the key references at the end of the article?&lt;br /&gt;
No&lt;br /&gt;
Is it based on empirical data instead of opinion?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
Summarize the references&lt;br /&gt;
Answer 7&lt;br /&gt;
Answer here&lt;/div&gt;</summary>
		<author><name>S133654</name></author>
	</entry>
	<entry>
		<id>http://13.50.150.85/index.php?title=Talk:User-Centered_Design&amp;diff=52472</id>
		<title>Talk:User-Centered Design</title>
		<link rel="alternate" type="text/html" href="http://13.50.150.85/index.php?title=Talk:User-Centered_Design&amp;diff=52472"/>
		<updated>2018-02-21T10:09:07Z</updated>

		<summary type="html">&lt;p&gt;S133654: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Abstract Feedback==&lt;br /&gt;
Text Clarity; Ok.&lt;br /&gt;
&lt;br /&gt;
Language; Ok.&lt;br /&gt;
&lt;br /&gt;
References; missing references&lt;br /&gt;
&lt;br /&gt;
In general the abstract is ok, when developing the article don&#039;t forget to reference the article and try connect with the content of course.&lt;br /&gt;
&lt;br /&gt;
Try to see if you can connect with the PM ISO 21500.&lt;br /&gt;
&lt;br /&gt;
==Feedback 1 | Reviewer Name: Lorenz Sieferle==&lt;br /&gt;
&lt;br /&gt;
===Question 1===&lt;br /&gt;
&lt;br /&gt;
Quality of the summary:&lt;br /&gt;
 &lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 1===&lt;br /&gt;
&lt;br /&gt;
In general the summary is good and clearly understandable. There are some spelling mistakes e.g. it is &#039;Life&amp;quot; instead of &amp;quot;live&amp;quot;. Furthermore if you use the abbreviation UCD for User-centered Design, it is necessary to introduce it in parenthesis the first time. Furthermore, you mention that UCD consists out of 5 steps but you don&#039;t name them at all. At least the name of the steps should be mentioned at this point. &lt;br /&gt;
&lt;br /&gt;
===Question 2===&lt;br /&gt;
&lt;br /&gt;
Structure and logic of the article:&lt;br /&gt;
&lt;br /&gt;
Is the argument clear?&lt;br /&gt;
&lt;br /&gt;
Is there a logical flow to the article?&lt;br /&gt;
&lt;br /&gt;
Does one part build upon the other?&lt;br /&gt;
&lt;br /&gt;
Is the article consistent in its argument and free of contradictions?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 2===&lt;br /&gt;
&lt;br /&gt;
So far, the article is quite logic but as there is just the abstract this question can&#039;t be answered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Question 3===&lt;br /&gt;
&lt;br /&gt;
Grammar and style:&lt;br /&gt;
&lt;br /&gt;
Is the writing free of grammatical and spelling errors?&lt;br /&gt;
&lt;br /&gt;
Is the language precise without unnecessary fill words?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 3===&lt;br /&gt;
&lt;br /&gt;
The text is clearly understandable and easy to read. However, there are some spelling mistakes like mentioned above (life instead of live). In addition there are some really long sentence which are followed by really short sentence. Try to keep it uniform and that the writing style is consistent throughout the whole text. &lt;br /&gt;
&lt;br /&gt;
===Question 4===&lt;br /&gt;
&lt;br /&gt;
Figures and tables:&lt;br /&gt;
&lt;br /&gt;
Are figures and tables clear?&lt;br /&gt;
&lt;br /&gt;
Do they summarize the key points of the article in a meaningful way?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
===Answer 4===&lt;br /&gt;
&lt;br /&gt;
So far the text does not consist any figures and tables. &lt;br /&gt;
&lt;br /&gt;
===Question 5===&lt;br /&gt;
&lt;br /&gt;
Interest and relevance:&lt;br /&gt;
&lt;br /&gt;
Is the article of high practical and / or academic relevance?&lt;br /&gt;
&lt;br /&gt;
Is it made clear in the article why / how it is relevant?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
===Answer 5===&lt;br /&gt;
&lt;br /&gt;
The relevance of the article is quite clear explained in the abstract and its clearly highlighted why it is important for project manager to consider this method.  &lt;br /&gt;
&lt;br /&gt;
===Question 6===&lt;br /&gt;
&lt;br /&gt;
Depth of treatment:&lt;br /&gt;
&lt;br /&gt;
Is the article interesting for a practitioner or academic to read?&lt;br /&gt;
&lt;br /&gt;
Does it make a significant contribution beyond a cursory web search?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 6===&lt;br /&gt;
&lt;br /&gt;
As since now just the abstract is uploaded it is not possible to answer the questions.&lt;br /&gt;
&lt;br /&gt;
===Question 7===&lt;br /&gt;
&lt;br /&gt;
Annotated bibliography:&lt;br /&gt;
&lt;br /&gt;
Does the article properly cite and acknowledge previous work?&lt;br /&gt;
&lt;br /&gt;
Does it briefly summarize the key references at the end of the article?&lt;br /&gt;
&lt;br /&gt;
Is it based on empirical data instead of opinion?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
===Answer 7===&lt;br /&gt;
&lt;br /&gt;
There is no annotated bibliography yet. Furthermore, the recommended references of the course are not implemented yet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Feedback 1 | Reviewer Name: Lars From-Hansen==&lt;br /&gt;
&lt;br /&gt;
User-Centered Design&lt;br /&gt;
Quality of the summary:&lt;br /&gt;
Very good. &lt;br /&gt;
Does the summary make the key focus, insights and/or contribution of the article clear?&lt;br /&gt;
Yes&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
I have no suggestions for improvement.&lt;br /&gt;
Answer 1&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 2 · TEXT&lt;br /&gt;
Structure and logic of the article:&lt;br /&gt;
Seems good.&lt;br /&gt;
Is the argument clear?&lt;br /&gt;
&lt;br /&gt;
Is there a logical flow to the article?&lt;br /&gt;
&lt;br /&gt;
Does one part build upon the other?&lt;br /&gt;
&lt;br /&gt;
Is the article consistent in its argument and free of contradictions?&lt;br /&gt;
&lt;br /&gt;
What would you suggest to improve?&lt;br /&gt;
&lt;br /&gt;
Answer 2&lt;br /&gt;
Answer here&lt;br /&gt;
&lt;br /&gt;
Question 3 · TEXT&lt;br /&gt;
Grammar and style:&lt;br /&gt;
Good&lt;br /&gt;
&lt;br /&gt;
Is the writing free of grammatical and spelling errors?&lt;br /&gt;
Yes&lt;br /&gt;
Is the language precise without unnecessary fill words?&lt;br /&gt;
Yes&lt;/div&gt;</summary>
		<author><name>S133654</name></author>
	</entry>
	<entry>
		<id>http://13.50.150.85/index.php?title=Articles_Spring_Term_2018&amp;diff=47855</id>
		<title>Articles Spring Term 2018</title>
		<link rel="alternate" type="text/html" href="http://13.50.150.85/index.php?title=Articles_Spring_Term_2018&amp;diff=47855"/>
		<updated>2018-02-12T19:28:52Z</updated>

		<summary type="html">&lt;p&gt;S133654: /* Overview of 2018 Wiki articles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ &#039;&#039;&#039;Disclaimer!&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;The requirements for the articles written in previous Terms (2014, 2015, 2016, Jun 2017, 2017) were not the same as for Spring Term 2018. Please make sure you read the requirements for your own fall/spring term carefully before starting your wiki article.&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please complete this table with your group number, full name, username and the title of your article.&lt;br /&gt;
&lt;br /&gt;
To create more lines in the table click &#039;&#039;&#039;Edit&#039;&#039;&#039; and use the following code to create more lines in the table and replace the example text with your own information:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap; &lt;br /&gt;
white-space: -moz-pre-wrap; &lt;br /&gt;
white-space: -pre-wrap; &lt;br /&gt;
white-space: -o-pre-wrap; &lt;br /&gt;
word-wrap: break-word;&amp;quot;&amp;gt;&lt;br /&gt;
|-		&lt;br /&gt;
|Group Number&lt;br /&gt;
|First Name&lt;br /&gt;
|Last Name&lt;br /&gt;
|Username&lt;br /&gt;
|Link to Article&lt;br /&gt;
|-&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Create a direct link by making square brackets ([[ ]]) around the title such as [[Title]]&lt;br /&gt;
&lt;br /&gt;
The straight lines ( | ) create columns and the straight line with a dash ( |- ) creates a new row in the table.&lt;br /&gt;
&lt;br /&gt;
( |} ) is only used at the very end to finish the coding for the table.&lt;br /&gt;
&lt;br /&gt;
=Overview of 2018 Wiki articles=&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|+Spring Term 2018 Wiki Articles&lt;br /&gt;
|-&lt;br /&gt;
!5&lt;br /&gt;
!Radoslaw Tomasz&lt;br /&gt;
!Tyczynski&lt;br /&gt;
!Radoslaw&lt;br /&gt;
![[Time Management]]&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Ioannis&lt;br /&gt;
|Papadantonakis&lt;br /&gt;
|Giannis&lt;br /&gt;
|[[Work Breakdown Structure]]&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Konstantinos&lt;br /&gt;
|Terzakis&lt;br /&gt;
|s161563&lt;br /&gt;
|[[Programming a project with the CPM]]&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Hoda&lt;br /&gt;
|Vazirinasab&lt;br /&gt;
|hoda.vn&lt;br /&gt;
|[[Agile project management]]&lt;br /&gt;
|-		&lt;br /&gt;
|3&lt;br /&gt;
|David&lt;br /&gt;
|Moya Perrino&lt;br /&gt;
|David Moya Perrino&lt;br /&gt;
|[[Risk Management in Renewable Energy Projects]]&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Sofie&lt;br /&gt;
|Melchior Karlson&lt;br /&gt;
|s133606&lt;br /&gt;
|[[Belbin&#039;s team roles]]&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Jan&lt;br /&gt;
|Talas&lt;br /&gt;
|jantalas&lt;br /&gt;
|[[Roles and responsibilities]]&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Sebastian&lt;br /&gt;
|Graff Daugaard&lt;br /&gt;
|Daugaard&lt;br /&gt;
|[[Dealing with conflict in project management]]&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Nikolaj&lt;br /&gt;
|Justsen&lt;br /&gt;
|s123742&lt;br /&gt;
|[[Vico Office as a project management tool]]&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Mehdi&lt;br /&gt;
|Abounnasr&lt;br /&gt;
|s176504&lt;br /&gt;
|[[Project monitoring methods]]&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Briet&lt;br /&gt;
|Hjaltalin&lt;br /&gt;
|Briet&lt;br /&gt;
|[[The Framework of Project Governance]]&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Jonas&lt;br /&gt;
|Heiberg Larsen&lt;br /&gt;
|JonasHL&lt;br /&gt;
|[[Risk Management Overview]]&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Kornpong&lt;br /&gt;
|Mahitthiburin&lt;br /&gt;
|Akorno&lt;br /&gt;
|[[Financial appraisal of project proposals]]&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Gudmundur&lt;br /&gt;
|Hermannsson&lt;br /&gt;
|gudmundur&lt;br /&gt;
|[[Project Scope Management]]&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Ína Salome&lt;br /&gt;
|Sturludóttir&lt;br /&gt;
|Ina&lt;br /&gt;
|[[Project scope statement]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Kevinth&lt;br /&gt;
|Balasubramaniam&lt;br /&gt;
|Kxviinth&lt;br /&gt;
|[[Future Workshop]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Davide&lt;br /&gt;
|Sartori&lt;br /&gt;
|DSartori&lt;br /&gt;
|[[Hoshin Kanri]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Julia&lt;br /&gt;
|Hoesel&lt;br /&gt;
|s172365&lt;br /&gt;
|[[Design Thinking]]&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Baptiste&lt;br /&gt;
|Hubert&lt;br /&gt;
|BaptisteH&lt;br /&gt;
|[[Project Life Cycle in Industrial Engineering]]&lt;br /&gt;
|-	&lt;br /&gt;
|8&lt;br /&gt;
|Mint&lt;br /&gt;
|Rasmussen&lt;br /&gt;
|s133819&lt;br /&gt;
|[[Risk Management in Construction Projects]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Vincent&lt;br /&gt;
|Oriot&lt;br /&gt;
|s172793&lt;br /&gt;
|[[Project sponsor]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Torbjørn&lt;br /&gt;
|Aleksandersen&lt;br /&gt;
|Taleksandersen&lt;br /&gt;
|[[Virtual Team Management]]&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Ragnhildur&lt;br /&gt;
|Ragnarsdottir&lt;br /&gt;
|Ragnhildur&lt;br /&gt;
|[[Brainstorming technique]]&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Anne&lt;br /&gt;
|Dittmann&lt;br /&gt;
|Anne&lt;br /&gt;
|[[Scheduling: Critical path, PERT, Gantt]]&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Julianna&lt;br /&gt;
|Apli&lt;br /&gt;
|s172414&lt;br /&gt;
|[[Ideation tools]]&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Hildur&lt;br /&gt;
|Gudmundsdottir&lt;br /&gt;
|S172763&lt;br /&gt;
|[[Contracting and procurement]]&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Christopher&lt;br /&gt;
|Søndergaard&lt;br /&gt;
|s140234&lt;br /&gt;
|[[;-)]]&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Casper Geertz&lt;br /&gt;
|Christensen&lt;br /&gt;
|S136445&lt;br /&gt;
|[[SWOT]]&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Demir&lt;br /&gt;
|Durovic&lt;br /&gt;
|DemirDurovic&lt;br /&gt;
|[[Managing multicultural teams]]&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Lorenz&lt;br /&gt;
|Sieferle&lt;br /&gt;
|s172691&lt;br /&gt;
|[[Agile Project Management with SCRUM]]&lt;br /&gt;
|-		&lt;br /&gt;
|12&lt;br /&gt;
|Jonas Greaker&lt;br /&gt;
|Sjøen&lt;br /&gt;
|s173562&lt;br /&gt;
|[[Integrated Design Process (IDP)]]&lt;br /&gt;
|-&lt;br /&gt;
|-		&lt;br /&gt;
|2&lt;br /&gt;
|Seyed (Habib)&lt;br /&gt;
|Bahrami&lt;br /&gt;
|Habib&lt;br /&gt;
|[[Uniqueness of a project]]&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Jonas&lt;br /&gt;
|Samuelsen&lt;br /&gt;
|Jonas Samuelsen&lt;br /&gt;
|[[Risk Register Analysis]]&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Johannes&lt;br /&gt;
|Eckert&lt;br /&gt;
|Johannes&lt;br /&gt;
|[[Waterfall vs. Lean Project Management]]&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Tobias&lt;br /&gt;
|Andersen&lt;br /&gt;
|Tobias&lt;br /&gt;
|[[Belbin Team Roles]]&lt;br /&gt;
|-		&lt;br /&gt;
|5&lt;br /&gt;
|Oliver Adam Mølskov&lt;br /&gt;
|Bech&lt;br /&gt;
|Oliver.amb&lt;br /&gt;
|[[Data Management]]&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Ugur&lt;br /&gt;
|Erman&lt;br /&gt;
|Ugur&lt;br /&gt;
|[[Why, How, What (The Golden Circle Model)]]&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Nina&lt;br /&gt;
|Bernhoft&lt;br /&gt;
|Nina&lt;br /&gt;
|[[Managing groups for high performance]]&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Julie&lt;br /&gt;
|Laursen&lt;br /&gt;
|Julie&lt;br /&gt;
|[[Meeting strategies]]&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Ole&lt;br /&gt;
|Schwiethal&lt;br /&gt;
|s172276&lt;br /&gt;
|[[Project governance framework]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|12&lt;br /&gt;
|Marianne&lt;br /&gt;
|Delp&lt;br /&gt;
|Marianne&lt;br /&gt;
|[[Choosing by Advantages (CBA)]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|4&lt;br /&gt;
|Christian&lt;br /&gt;
|Pedersen&lt;br /&gt;
|S093223&lt;br /&gt;
|[[Communication Management Strategy]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|12&lt;br /&gt;
|Lukasz&lt;br /&gt;
|Marczuk&lt;br /&gt;
|s172569&lt;br /&gt;
|[[Cash flow &amp;amp; payment milestones ]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|6&lt;br /&gt;
|Rikke&lt;br /&gt;
|Husum&lt;br /&gt;
|s170446&lt;br /&gt;
|[[Coaching - Project Manager as Change Agent]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Simen Michael Dilling&lt;br /&gt;
|Hjelseth&lt;br /&gt;
|SimenHjelseth&lt;br /&gt;
|[[Integrated Concurrent Engineering]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Katja Kimmer&lt;br /&gt;
|Larsen&lt;br /&gt;
|Katja&lt;br /&gt;
|[[Organizational structures]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Ida&lt;br /&gt;
|Smidt&lt;br /&gt;
|idasmidt&lt;br /&gt;
|[[Lean Approach to Scheduling in Construction Projects]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Walther&lt;br /&gt;
|Emil Eriksen&lt;br /&gt;
|Walther Emil Eriksen&lt;br /&gt;
|[[Value Proposition Canvas]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Rasmus Peter&lt;br /&gt;
|Østerlund&lt;br /&gt;
|R4smus&lt;br /&gt;
|[[Key Performance Indicators (KPI)]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Daniel Alejandro&lt;br /&gt;
|Campos Rivera&lt;br /&gt;
|Daniel Campos&lt;br /&gt;
|[[Business Analytics in Civil Engineering Projects]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|Matthew&lt;br /&gt;
|Wells&lt;br /&gt;
|Matthew Wells&lt;br /&gt;
|[[Line Balancing - Yamazumi Chart Method]]&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Ignasi&lt;br /&gt;
|Girones Cadiz&lt;br /&gt;
|&lt;br /&gt;
|[[Work Breakdown Structure]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|Ellen &lt;br /&gt;
|Trovåg Amundsen&lt;br /&gt;
|ellentam&lt;br /&gt;
|[[Beyond the Triple Constraints]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Joachim Schou&lt;br /&gt;
|Larsen&lt;br /&gt;
|Joachim Schou Larsen&lt;br /&gt;
|[[Power, politics and stakeholder management]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Benedek &lt;br /&gt;
|Zajkas&lt;br /&gt;
|Benedek Zajkas&lt;br /&gt;
|[[Scrum vs. Waterfall Methodology]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Gustavo&lt;br /&gt;
|Pagliari Valerio dos Santos&lt;br /&gt;
|s176056&lt;br /&gt;
|[[Negotiation skills from the PM&#039;s perspective]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Natalia&lt;br /&gt;
|Krygier&lt;br /&gt;
|Natalia Krygier&lt;br /&gt;
|[[Behaviors in scheduling]]&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Argyro&lt;br /&gt;
|Soumpourlou&lt;br /&gt;
|s170073&lt;br /&gt;
|[[Cross-cultural Management]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|13&lt;br /&gt;
|Andrzej&lt;br /&gt;
|Kubik&lt;br /&gt;
|s172608&lt;br /&gt;
|[[Different sides of Project Management Scheduling]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|2&lt;br /&gt;
|Lima&lt;br /&gt;
|Parhiz&lt;br /&gt;
|s134639&lt;br /&gt;
|[[Essential Managerial Tasks]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|4&lt;br /&gt;
|Harald&lt;br /&gt;
|Hersted&lt;br /&gt;
|s145067&lt;br /&gt;
|[[Human resource management]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|5&lt;br /&gt;
|Sarah&lt;br /&gt;
|Bourdiaux Terp&lt;br /&gt;
|Sarah&lt;br /&gt;
|[[The Sprint Methodology in Agile Project Management]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|1&lt;br /&gt;
|Jonathan&lt;br /&gt;
|Nøddeskov Clifford&lt;br /&gt;
|S142556&lt;br /&gt;
|[[Roadmapping]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|9&lt;br /&gt;
|Erna Gudny&lt;br /&gt;
|Aradottir&lt;br /&gt;
|ErnaGudny&lt;br /&gt;
|[[SMART Goals]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|5&lt;br /&gt;
|Klaudia Edyta&lt;br /&gt;
|Onyszkiewicz&lt;br /&gt;
|Onysz&lt;br /&gt;
|[[Project Team Roles and Responsibilities]]&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Aksel&lt;br /&gt;
|Watson&lt;br /&gt;
|S175507&lt;br /&gt;
|[[Managing start-ups in Unregulated Markets]]&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Alice&lt;br /&gt;
|Allouche&lt;br /&gt;
|Alice&lt;br /&gt;
|[[Meetings Management]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Susan&lt;br /&gt;
|Tyrell&lt;br /&gt;
|Styrell&lt;br /&gt;
|[[The Role of the Project Sponsor]]&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|10&lt;br /&gt;
|Casper&lt;br /&gt;
|Stroem&lt;br /&gt;
|S172043&lt;br /&gt;
|[[Business Case]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|7&lt;br /&gt;
|Cetin&lt;br /&gt;
|Arslan&lt;br /&gt;
|Arslance&lt;br /&gt;
|[[User-Centered Design]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|13&lt;br /&gt;
|Piotr&lt;br /&gt;
|Mieszalo&lt;br /&gt;
|PiotrMieszalo&lt;br /&gt;
|[[Resources loading, leveling and crashing]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|6&lt;br /&gt;
|Mads&lt;br /&gt;
|Grøndal&lt;br /&gt;
|s123666&lt;br /&gt;
|[[Value Analysis]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|6&lt;br /&gt;
|Emma&lt;br /&gt;
|Balstrup Klinke Hansen&lt;br /&gt;
|s134181&lt;br /&gt;
|[[Kotter&#039;s 8- Step Change Model]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|8&lt;br /&gt;
|David&lt;br /&gt;
|Baldursson&lt;br /&gt;
|s162284&lt;br /&gt;
|[[Supply chain management in construction]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|3&lt;br /&gt;
|Nikoleta&lt;br /&gt;
|Kolitsopoulou-Maridaki&lt;br /&gt;
|s162461&lt;br /&gt;
|[[Roles and responsibilities of program manager]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|7&lt;br /&gt;
|Magnus&lt;br /&gt;
|Held&lt;br /&gt;
|s133656&lt;br /&gt;
|[[Failure Mode and Effects Analysis in Various Project Stages]]&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-		&lt;br /&gt;
|77&lt;br /&gt;
|Lars&lt;br /&gt;
|From-Hansen&lt;br /&gt;
|s133654&lt;br /&gt;
|[[Brainstorming as a risk identification method]]&lt;br /&gt;
|-&lt;/div&gt;</summary>
		<author><name>S133654</name></author>
	</entry>
	<entry>
		<id>http://13.50.150.85/index.php?title=Brainstorming_as_a_risk_identification_method&amp;diff=47851</id>
		<title>Brainstorming as a risk identification method</title>
		<link rel="alternate" type="text/html" href="http://13.50.150.85/index.php?title=Brainstorming_as_a_risk_identification_method&amp;diff=47851"/>
		<updated>2018-02-12T19:25:33Z</updated>

		<summary type="html">&lt;p&gt;S133654: Created page with &amp;quot; == Abstract ==  Brainstorming has a broad range of applications with one of them being as a risk identification technique. Risk identification in a project, program or portfo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Abstract ==&lt;br /&gt;
&lt;br /&gt;
Brainstorming has a broad range of applications with one of them being as a risk identification technique. Risk identification in a project, program or portfolio lays the foundation of the risk analysis. It is therefore very important to identify as many possible risks as possible to end up with a complete analysis. &lt;br /&gt;
The goal of brainstorming in risk identification is to gain a thorough list of risks. To gain a comprehensive list of risks it is important to involve the right stakeholders in the brainstorm. This would normally be the project team itself with aid of external experts, who have relevant insight. [1]&lt;br /&gt;
A facilitator, who ensures the brainstorm is performed correctly and motivates all participants to engage in the brainstorm, should lead the brainstorm. The facilitator can pick different brainstorming techniques depending on other risk identification methods chosen, the number of participants and time available. &lt;br /&gt;
The brainstorm should produce a broad range of more or less unorganized ideas for risks depending on the brainstorming technique. The ideas need to be categorized, grouped and connected to be useful for the further risk analysis. This can be done either as a part of the brainstorming session or by the facilitator. &lt;br /&gt;
In the following article brainstorming as a risk identification method will be discussed. The article will provide information on how to use brainstorming and how to modify the brainstorm so it suits the needs of the individual risk management process.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1.  Project Management Institute, Project Management: A guide to the Project Management Body of Knowledge, (2013)&lt;/div&gt;</summary>
		<author><name>S133654</name></author>
	</entry>
</feed>