DTU ProjectLab - User contributions [en-gb]

Articles Spring Term 2019

2019-02-18T21:20:51Z

Habib:

=Overview of 2019 Wiki articles=

{| class="wikitable sortable"
|+Spring Term 2019 Wiki Articles
|-
|13
|Evgenia
|Chatzivasileiou
|s182299
|[[Project Sponsorship]]
|-
|-
|13
|Theodoros
|Seremetakis
|s183272
|[[Investment portfolio management]]
|-
|5
|Federica
|Menti
|S182994
|[[Getting Things Done (David Allen)]]
|-
|-
|2
|Panagiotis
|Vounatsos
|PanosVoun
|[[Epistemic vs. Aleatory uncertainty]]
|-
|-
|9
|Jack
|Frain
|Fraino12345
|[[Stakeholder Management Processes in Projects]]
|-
|-
|14
|Alexandros
|Bellos
|AlexBellos
|[[Effective Brainstorming]]
|-
|-
|Group Number Pending
|Edoardo
|Braccini
|EdoBraa
|[[Benefits Realisation Management (BRM)]]
|-
|-
|Group Number Pending
|Andrea
|Könnecke
|Andrea Könnecke
|[[Shannon & Weaver Model for Communication]]
|-
|-
|Group 10
|Srdjan
|Gluhovic
|srdjangluhovic
|[[Project Scope Control Management]]
|-
|-
|11
|Casper
|Claudinger
|Casper
|[[Managing projects in a functional organization]]
|-
|-
|8
|Ronglian
|Wei
|Panda Lian
|[[Conceptual levels of competence]]
|-
|-
|4
|Jesper
|Wolters
|Wolters
|[[Resource allocation and crashing]]
|-
|-
|3
|Oliwia
|Sonia
|Lubiarz
|[[Meeting Management]]
|-
|-
|Group Number Pending
|Francisco
|Almirudis
|Frank Almirudis
|[[Scheduling: Critical path, PERT and Gantt]]
|-
|-
|Group Number Pending
|Bartlomiej
|Maciej
|Tyczynski
|[[Outcome, output, benefit]]
|-
|-
|16
|Brynja
|Benediktsdóttir
|Brynja Ben.
|[[The Periodic Table of Project Management]]
|-
|-
|16
|Jonina Thora
|Einarsdottir
|Jonina Thora
|[[Project Management Success Factors]]
|-
|-
|Group Number 5
|Pedro
|Lopes da Cunha
|PedroLopesCunha
|[[Project Management: Cost vs. Price]]
|-
|-
|Group Number Pending
|Sarantis
|Pavlidis
|Sarantis
|[[Types of activities]]
|-
|Group Number Pending
|Rikke
|Andersen
|RikkeA
|[[Cognitive Bias]]
|-
|-
|12
|Johan
|Hilsøe
|s154073
|[[Unidentified Risks]]
|-
|-
|Group Number Pending
|Mads
|Kronholm
|Mads Kronholm
|[[DMAIC]]
|-
|-
|Group 11
|Anne
|Dittmann
|Anne
|[[Organisational Design and Structures]]
|-
|-
|12
|Thea
|Pedersen
|Thea
|[[Agile One Page Project Management]]
|-
|-
|Group Number Pending
|Madalina
|Grigoras
|s186465
|[[Value to whom?]]
|-
|-
|4
|Martin
|Eberholst Carlsen
|Martineberholstcarlsen
|[[Project Initiation Management in construction]]
|-
|-
|6
|Rasmine
|Søgren
|s145320
|[[Outcome]]
|-
|-
|6
|Julie
|Rostgaard Andersen
|s123790
|[[Use of Business Model Canvas to Kickstart the project management]]
|-
|-
|Group Number Pending
|Dilan
|Casablanca
|Dilan Casablanca
|[[Prefabricated houses (industrial process)]]
|-
|5
|Sandro
|Pina
|SandroPina
|[[Create a pitch]]
|-
|-
|11
|Kristoffer
|Glahn
|s133378
|[[Vision statement]]
|-
|-
|Group Number Pending
|Maria Christina
|Prokou
|Mprokou
|[[Negotiation Skills]]
|-
|-
|3
|Habib (Seyed)
|Bahrami
|Habib
|[[Project Uniqueness]]
|-
|-
|12
|Amani
|Alabdullah
|s173307
|[[Integrated Project Delivery (IPD)]]
|-
|-
|12
|Andreas
|Riposati
|Ripo
|[[Basic estimation techniques]]
|-
|-
|10
|Mark
|Christiansen
|s152736
|[[Stephen Covey's seven principles]]
|-
|-
|6
|Signe
|Bjerrum
|s141886
|[[The Triple Constraint in Project Management]]
|-
|-
|9
|Sebastian
|Walther
|Sebastian
|[[Value Canvas in Projects]]
|-
|-
|9
|Keegan
|van Kooten
|Keegan
|[[Planning Poker for Improved Project Delivery]]
|-
|-
| 8
|Hagos Zeru
|Gide
|Trhas
|[[BIM as a project management tool on construction companies]]
|-
|-
|-
|-
|Group Number Pending
|William
|Durant
|Mangum
|[[Crisis Management when there is a Project Cost Overrun]]
|-
|-
|-
|9
|Shri Tejas
|Vedula
|Tehass 7
|[[The implementation of KPIs]]
|-
|-
|9
|Casper
|Gandil Qvortrup
|CasperGandil
|[[Application of Balanced Scorecard in Portfolio Management]]
|-
|-
|12
|Veronika Zsuzsanna
|Bankó
|Veronikabanko
|[[Determining Measurement Methods in Earned Value Management]]
|-
|-
|Group Number Pending
|Mercedes
|Hachmann
|Mercedes Hachmann
|[[Design Thinking]]
|-
|-
|Group 1
|Rasmus
|Bjerg
|Rasmusbjerg
|[[Cash flow and milestone payments]]
|-
|-
|Group Number Pending
|Moritz
|Gutheil
|MoritzGutheil
|[[Dan Pink on Motivation]]
|-
|-
|Group 5
|Giorgia
|Scartozzi
|GiorgiaS
|[[Resource-Constrained Critical Path Method]]
|-
|-
|Group 3
|Hannah
|Kürschner
|Hannah
|[[Projects integrating Sustainable Methods]]
|-
|-
|Group 17
|Daniel
|Vorting
|s141018
|[[Product family master plan]]
|-
|-
|Group 10
|André
|Condamine
|S173349
|[[Belbin's Team Roles]]
|-
|-
|7
|Kristine
|Kaulberg
|Kristbk
|[[Governance of Project Management]]
|-
|Group Number 17
|Sai Mahesh
|Nadukuru
|Sm nadukuru
|[[Process Planning and Cost Estimation]]
|-
|-
|7
|Gustav
|Josephsen
|Gustav Josephsen
|[[Potentials of Key Performance Indicators]]
|-
|-
|11
|Rikke Louise Kjær
|Knudsen
|RikkeK
|[[Milestones in Project Planning]]
|-
|-
|2
|Hedin
|Gunnarsstein Poulsen
|hedinp
|[[Resources]]
|-
|-
|3
|Isabel
|Wang
|isabel.w
|[[Benefits Realization Management as a key driver of Project Management Effectiveness]]
|-
|12
|Frederik
|Sørensen
|FTSN
|[[Hersey and Blanchard's Situational Leadership]]
|-
|4
|Simon
|Muurholm Hansen
|Muurholm
|[[Performance-based contracting]]
|-
|6
|Charles
|Hemmingsen
|s122801
|[[Programmification of work]]
|-
|17
|Alberto
|Tognon
|s172420
|[[Project Management in pharmaceutical industry]]
|-
|17
|Stefano
|Di Lenardo
|s190056
|[[A conceptual framework of sustainability in project management]]
|-
|5
|Arndt
|Oschinsky
|AJO
|[[The Project Charter]]
|-

|16
|Dana Rut
|Gunnarsdóttir
|s180289
|[[Project Management Reporting]]
|-

|-
|8
|Anna
|Shevchenko
|Anutka
|[[SAFe]]
|-

|-
|Group Number Pending
|Thomas
|Boel
|Morning
|[[Cost Control]]
|-

|-
|6
|Ole
|Moe
|s186359
|[[Prince2]]
|-

|-
|2
|Nikolaj
|Petersen
|s173344
|[[Managing habits in a project]]
|-

|-
|15
|Sofie
|Martinussen
|Sofie Martinussen
|[[Improve communication with active listening]]
|-

|-
|2
|Sophia
|Nielsen
|s114901
|[[Adaptive Project Management]]
|-

|-
|10
|Costanza
|Sesti
|Costanza Sesti
|[[Systems Theory in Project Management]]
|-
|-
|-
|7
|Mathias
|Steuch
|Msteuch
|[[SMART goals - A Project Manager Tool]]
|-
|-
|-
|16
|Marie
|Bukkholm
|s182741
|[[Resource breakdown structure]]
|-
|-
|16
|Karina
|Kindingstad
|Karina
|[[Benefits of systems engineering]]
|-
|-
|16
|Robert
|Kjønås
|RobertK
|[[Human behaviors in scheduling]]
|-
|-
|8
|Bashir
|Isse
|BJI
|[[Decision-making]]
|-
|-
|15
|Andreas
|Tuxen
|S153408
|[[Requirements management using SysML]]
|-

Project Uniqueness

2019-02-18T21:15:31Z

Habib: Created page with "==Abstract== Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a pr..."

==Abstract==
Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as:

“A project consists of a '''unique''' set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”<ref name="ISO">ISO-21500, 2013.</ref>.

Furthermore, the Project Management Institute (PMI) defines a project as:

“A project is a temporary endeavor undertaken to create a '''unique''' product or service”. <ref name="PMBOK"> Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th Edition, 2013.</ref>

Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”. In short the "Volume vs Variety" <ref name="HARVEY"> Harvey Maylor, Project Management, 4th Edition, 2010, page 7-9.</ref> of processes in a project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted in this article subject to the benefits and challenges of having a unique project vs. a non-unique project. Furthermore, the article briefly considers the uniqueness of programs and portfolios, and how they are different to the uniqueness of projects.

==The Big Idea==

==Applications==

==Limitations==

==References ==
<references/>

== Annotated bibliography ==
Harvey Maylor, '''Project Management''', 4th Edition, 2010, page 7-9.

Uniqueness of a project

2019-02-18T21:13:30Z

Habib: Replaced content with "This article is allowed to be deleted."

This article is allowed to be deleted.

Talk:Project Life Cycle in Industrial Engineering

2018-02-19T22:30:00Z

Habib:

==Abstract Feedback==
Text Clarity; Ok.

Language; Ok.

References; Ok.

In general the abstract is ok, but try avoid a too generic article, when developing the article don't forget to elaborate and describe the relevance for a Project Manager.

Try to find other relevant references and see if there are new approaches.

==Feedback 1 | Reviewer name: ''Ugur Erman''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
''The different points of the abstract are clear and there is a reference to one of the mandatory references (PMBOK guide). My main concern with the abstract is that it might sound a bit generic and it can be difficult to see how it is relevant for a project manager (the topic itself is relevant and the rest of the article shows relevance).''

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
''The argument is clear and I like the flow of the article, especially in the Big Idea section where the author splits the article into theory, example, theory, example etc. The flow also makes sure that one part builds upon the other. I find the article consistent in its argument and free of contradictions.''

''One suggestion I will make is that a more is written and discussed in the '''Applications''' and '''Limitations''' sections.''

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
''I find the language precise and without unnecessary fill words. I did not really find grammatical and spelling error. The only thing I will suggest is that more commas are inserted in the text as it will make it easier to read.''

''I did however notice in the section about '''Planning: Organizing and preparing''' that something can be changed. The author lists several points and in point 3 where several planning softwares are mentioned, there are three dots (...) just after OpenProj. I am not certain whether the dots are written as a way of saying etc. but if they are, I will suggest that etc. or among others (or something like that) is written.''

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
''There are no tables but 2 figures. Both figures have decent sizes and while the text in figure 1 can be read, the text in figure 2 is blurry. I will suggest that both figures (especially figure 2) are self-explanatory, meaning that the figures should be described a bit more in depth in the text just under the figure.''

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
''The article is definitely relevant and it is made clear multiple times that a project manager can make use of the tools described in the article.''

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
''The article is interesting for a practitioner or academic and I think it makes several points about several things. The author has also shown critical thinking e.g. in the section where the planning software has been discussed.''

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
''The article does properly cite and acknowledge previous work and key references are summarized at the end. One thing I will suggest is that a little more is written about the references listed in the '''Annotated Bibliography''' section.''

==Feedback 2 | Reviewer name: ''Seyed (Habib) Bahrami''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
The summary is ok. The topic that the article discusses has a good and relevant focus on project/program/portfolio. However, it may be a bit too wide/generic topic.

Personally, I would like to have a clear overview of what the article discusses, which is not explained. As a reader I miss phrases like "This article discusses..." or "firstly bla bla bla is considered, secondly bla bla is considered" and so on, so the reader knows what to expect from the article.

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
The argument of the article is clear, but there is not a good flow. Again, as a reader I become confused when it is not clearly defined what the following section is about - the article suddenly jumps into theory, before explaining that it wats to do that.

I like however the fact that theory and examples are separated.

Furthermore, I suggest that the bullet-points in the "Initiation" and "Planning" sections are expanded into a whole text. This will help to keep the structure of the article concise and it binds the single pieces of the text together.

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
I did not find any major grammatical and spelling errors. The language is ok and does not contain unnecessary fill words.

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
Figures should generally be self-explanatory. The two figures used in the article are good, but the article does not refer to the figures in the text. Thus the reader will never be referred to the figures and they may be neglected.

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
The topic that the article discusses is highly relevant for any project manager. The project life cycle is a topic that has a high practical relevance, and it is stated several times in the article why it is relevant.

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
The article is very interesting and a project management-practitioner or -academic will inevitably work with the topic "Project Life Cycle". But since the topic is so generic this article/deliverable is not a [[significant]] contribution beyond a cursory web search - The topic of "Project Life Cycle" is discussed thoroughly in many project management textbooks and webpages. However, dealing with the Project Life Cycle is a relevant practice for all project managers.

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
The article cites and acknowledges previous work, and refers even to other APPPM wiki pages which I liked. In Annotated Bibliography there has been referred to the PMBOK as a book that explains in details the Life Cycle Model, but it doesn't say where (which chapter/page(s)). Remember to put references in the figures as well.

Talk:Why, How, What (The Golden Circle Model)

2018-02-19T16:08:47Z

Habib:

==Abstract Feedback==
Text Clarity; Ok.

Language; Ok.

References; missing references related to the standards

The abstract describes the use of the golden circle in organizations, try to develop the article thinking in the project organization and find relevant literature.

Annotated bibliography is a list of articles, books or documents followed by a briefly descriptive and evaluative paragraph, what you have under your ''annotated bibliography'' section are ''references''.

==Feedback 1 | Reviewer name: ''Baptiste Hubert''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
''Answer here''

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
''Answer here''

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
''Answer here''

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
''Answer here''

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
''Answer here''

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
''Answer here''

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
''Answer here''

==Feedback 2 | Reviewer name: ''Seyed (Habib) Bahrami''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
Overall, yes. The abstract is clear, concise and summarises the focus of the article. I like the three bullet points. However, you could shortly add the relationship between the Golden Circle Model and the human brain in here as well, because that is really exciting.

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
The argument is clear, and there is a logical flow and good setup to the article (assuming that the application and limitation will also be considered). One part does build upon another, especially the comparison of the Golden Circle Model and the human brain. The article (as it is now) is consistent in its argument and does not have contradictions.

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
A small typo in the section Big Idea: "In his model, SInek explains something he...", you mean Sinek.

Apart from that I found no grammatical and spelling errors. There were places where I would place an extra comma, but that does not necessarily make the text incorrect. The language is clear, concise and comprehensible. I have no further improvements.

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
The two figures are good to have in order to understand the points that you make, but figures should be self-explanatory. Explain in the figure text what the figure represents.

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
The topic that the article discusses is not a topic that all Project managers (assuming the topic is written in the project level, and not program or portefolio level) MUST know, and even though many project managers do not necessarily use the modelthey complete the project successfully. However, it is a very exciting topic, and a knowledge in this matter will undeniably be interesting and relevant for a project manager, because, as stated in the article, having a strong WHY helps establishing a strong vision, which can help with the motivation of the project team.

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
Yes, the article is very interesting for a practitioner or academic to read. Since it is a topic that is not included in many project, program or portfolio textbooks it will make a significant contribution to have it explained here. However, the depth of treatment could be better if the topic revolved more about project management. Perhaps include more examples.

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
The annotated bibliography is empty, but in references the article proporly cite and acknowledge previous work.

If you could find more relevant references, aside from Simon Sinek, it would be more empirical and better.

Talk:Why, How, What (The Golden Circle Model)

2018-02-19T15:56:19Z

Habib:

==Abstract Feedback==
Text Clarity; Ok.

Language; Ok.

References; missing references related to the standards

The abstract describes the use of the golden circle in organizations, try to develop the article thinking in the project organization and find relevant literature.

Annotated bibliography is a list of articles, books or documents followed by a briefly descriptive and evaluative paragraph, what you have under your ''annotated bibliography'' section are ''references''.

==Feedback 1 | Reviewer name: ''Baptiste Hubert''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
''Answer here''

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
''Answer here''

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
''Answer here''

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
''Answer here''

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
''Answer here''

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
''Answer here''

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
''Answer here''

==Feedback 2 | Reviewer name: ''Seyed (Habib) Bahrami''==
===Question 1 · TEXT===
'''Quality of the summary:'''

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

===Answer 1===
Overall, yes. The abstract is clear, concise and summarises the focus of the article. I like the three bullet points. However, you could shortly add the relationship between the Golden Circle Model and the human brain in here as well, because that is really exciting.

===Question 2 · TEXT===
'''Structure and logic of the article:'''

Is the argument clear?

Is there a logical flow to the article?

Does one part build upon the other?

Is the article consistent in its argument and free of contradictions?

What would you suggest to improve?

===Answer 2===
The argument is clear, and there is a logical flow and good setup to the article (assuming that the application and limitation will also be considered). One part does build upon another, especially the comparison of the Golden Circle Model and the human brain. The article (as it is now) is consistent in its argument and does not have contradictions.

===Question 3 · TEXT===
'''Grammar and style:'''

Is the writing free of grammatical and spelling errors?

Is the language precise without unnecessary fill words?

What would you suggest to improve?

===Answer 3===
A small typo in the section Big Idea: "In his model, SInek explains something he...", you mean Sinek.

Apart from that I found no grammatical and spelling errors. There were places where I would place an extra comma, but that does not necessarily make the text incorrect. The language is clear, concise and comprehensible. I have no further improvements.

===Question 4 · TEXT===
'''Figures and tables:'''

Are figures and tables clear?

Do they summarize the key points of the article in a meaningful way?

What would you suggest to improve?

===Answer 4===
The two figures are good to have in order to understand the points that you make, but figures should be self-explanatory. Explain in the figure text what the figure represents.

===Question 5 · TEXT===
'''Interest and relevance:'''

Is the article of high practical and / or academic relevance?

Is it made clear in the article why / how it is relevant?

What would you suggest to improve?

===Answer 5===
The topic that the article discusses is not a topic that all Project managers (assuming the topic is written in the project level, and not program or portefolio level) MUST know, and even though many project managers do not necessarily use the modelthey complete the project successfully. However, it is a very exciting topic, and a knowledge in this matter will undeniably be interesting and relevant for a project manager, because, as stated in the article, having a strong WHY helps establishing a strong vision, which can help with the motivation of the project team.

===Question 6 · TEXT===
'''Depth of treatment:'''

Is the article interesting for a practitioner or academic to read?

Does it make a significant contribution beyond a cursory web search?

What would you suggest to improve?

===Answer 6===
''Answer here''

===Question 7 · TEXT===
'''Annotated bibliography:'''

Does the article properly cite and acknowledge previous work?

Does it briefly summarize the key references at the end of the article?

Is it based on empirical data instead of opinion?

What would you suggest to improve?

===Answer 7===
''Answer here''

Uniqueness of a project

2018-02-13T13:17:06Z

Habib:

Uniqueness of a project

2018-02-13T10:26:31Z

Habib:

==Abstract==
Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as:

“A project consists of a '''unique''' set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”<ref name="ISO">ISO-21500, 2013.</ref>.

Furthermore, the Project Management Institute (PMI) defines a project as:

“A project is a temporary endeavor undertaken to create a '''unique''' product or service”. <ref name="PMBOK"> Project Management Institute, '''A Guide to the Project Management Body of Knowledge (PMBOK® Guide)''', 5th Edition, 2013.</ref>

Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”. In short the "Volume vs Variety" <ref name="HARVEY"> Harvey Maylor, '''Project Management''', 4th Edition, 2010, page 7-9.</ref> of processes in a project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted in this article subject to the benefits and challenges of having a unique project vs. a non-unique project. Furthermore, the article briefly considers the uniqueness of programs and portfolios, and how they are different to the uniqueness of projects.

==The Big Idea==

==Applications==

==Limitations==

==References ==
<references/>

Uniqueness of a project

2018-02-13T00:12:50Z

Habib:

==Abstract==
Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as:

“A project consists of a '''unique''' set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”<ref name="ISO">ISO-21500, 2013.</ref>.

Furthermore, the Project Management Institute (PMI) defines a project as:

“A project is a temporary endeavor undertaken to create a '''unique''' product or service”. <ref name="PMBOK"> Project Management Institute, '''A Guide to the Project Management Body of Knowledge (PMBOK® Guide)''', 5th Edition, 2013.</ref>

Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”. In short the "Volume vs Variety" <ref name="HARVEY"> Harvey Maylor, '''Project Management''', 4th Edition, 2010, page 7-9.</ref> of processes in a project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted in this article subject to the benefits and challenges of having a unique project vs. a non-unique project. Furthermore, the article briefly considers the uniqueness of programs and portfolios, and how they are different to the uniqueness of projects.

==The Big Idea==

==Applications==

==Limitations==

==Annotated bibliography==
<references/>

Uniqueness of a project

2018-02-12T23:57:55Z

Habib:

==Abstract==
Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as:

“A project consists of a '''unique''' set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”<ref name="ISO">ISO-21500, 2013.</ref>.

Furthermore, the Project Management Institute (PMI) defines a project as:

“A project is a temporary endeavor undertaken to create a '''unique''' product or service”. <ref name="PMBOK"> Project Management Institute, '''A Guide to the Project Management Body of Knowledge (PMBOK® Guide)''', 5th Edition, 2013.</ref>

Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”.

In short the "Volume vs Variety" <ref name="HARVEY"> Harvey Maylor, '''Project Management''', 4th Edition, 2010, page 7-9.</ref> of processes in the project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted subject to the benefits and challenges of having a unique project vs. a non-unique project.

==The Big Idea==

==Applications==

==Limitations==

==Annotated bibliography==
<references/>

Articles Spring Term 2018

2018-02-06T13:00:55Z

Habib: /* Overview of 2018 Wiki articles */

{| class="wikitable"
|+ '''Disclaimer!
|-
|''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 term carefully before starting your wiki article.''
|}

Please complete this table with your group number, full name, username and the title of your article.

To create more lines in the table click '''Edit''' and use the following code to create more lines in the table and replace the example text with your own information:

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
|-
|Group Number
|First Name
|Last Name
|Username
|Link to Article
|-
</pre>
Create a direct link by making square brackets ([[ ]]) around the title such as [[Title]]

The straight lines ( | ) create columns and the straight line with a dash ( |- ) creates a new row in the table.

( |} ) is only used at the very end to finish the coding for the table.

=Overview of 2018 Wiki articles=

{| class="wikitable sortable"
|+June 2017 Wiki Articles
|-
!Group number
!First name
!Second name
!User name
!Link to article
|-
|GN
|FN
|SN
|UN
|[[Name of your Wiki Article]]
|-
|GN
|Hoda
|Vazirinasab
|hoda.vn
|[[Agile project management]]
|-
|-
|3
|David
|Moya Perrino
|David Moya Perrino
|[[Risk Management in Renewable Energy Projects]]
|-
|3
|Sofie
|Melchior Karlson
|s133606
|[[Belbin's team roles]]
|-
|GN
|Sebastian
|Graff Daugaard
|Daugaard
|[[Dealing with conflict in project management]]
|-
|2
|Mehdi
|Abounnasr
|s176504
|[[Project monitoring methods]]
|-
|GN
|Briet
|Hjaltalin
|Briet
|[[Project governance]]
|-
|GN
|Jonas
|Heiberg Larsen
|JonasHL
|[[Risk Management Overview]]
|-
|GN
|Kornpong
|Mahitthiburin
|Akorno
|[[Financial appraisal of project proposals]]
|-
|GN
|Gudmundur
|Hermannsson
|gudmundur
|[[Project Scope Management]]
|-
|GN
|Ína Salome
|Sturludóttir
|Ina
|[[Project scope statement]]
|-
|GN
|Kevinth
|Balasubramaniam
|Kxviinth
|[[Future Workshop]]
|-
|GN
|Davide
|Sartori
|DSartori
|[[Hoshin Kanri]]
|-
|GN
|Julia
|Hoesel
|s172365
|[[Design Thinking]]
|-
|2
|Baptiste
|Hubert
|BaptisteH
|[[Project Management: Life Cycle in Industrial Engineering]]
|-
|GN
|Mint
|Rasmussen
|s133819
|[[Risk Management in Construction Projects]]
|-
|GN
|Vincent
|Oriot
|s172793
|[[Project sponsor]]
|-
|GN
|Torbjørn
|Aleksandersen
|Taleksandersen
|[[Virtual Team Management]]
|-
|GN
|Ragnhildur
|Ragnarsdottir
|Ragnhildur
|[[Brainstorming technique]]
|-
|GN
|Anne
|Dittmann
|Anne
|[[Scheduling: Critical path, PERT, Gantt]]
|-
|1
|Julianna
|Apli
|s172414
|[[Ideation tools]]
|-
|GN
|Hildur
|Gudmundsdottir
|S172763
|[[Contracting and procurement]]
|-
|1
|Christopher
|Søndergaard
|s140234
|[[;-)]]
|-
|GN
|Casper Geertz
|Christensen
|S136445
|[[SWOT]]
|-
|GN
|Demir
|Durovic
|DemirDurovic
|[[Multicultural teams: opportunities and challenges]]
|-
|GN
|Lorenz
|Sieferle
|s172691
|[[Agile Project Management with SCRUM]]
|-
|GN
|Jonas Greaker
|Sjøen
|s173562
|[[Integrated Design Process (IDP)]]
|-
|-
|2
|Seyed (Habib)
|Bahrami
|Habib
|[[Uniqueness of a project]]
|-

Articles Spring Term 2018

2018-02-06T13:00:24Z

Habib: /* Overview of 2018 Wiki articles */

{| class="wikitable"
|+ '''Disclaimer!
|-
|''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 term carefully before starting your wiki article.''
|}

Please complete this table with your group number, full name, username and the title of your article.

To create more lines in the table click '''Edit''' and use the following code to create more lines in the table and replace the example text with your own information:

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
|-
|Group Number
|First Name
|Last Name
|Username
|Link to Article
|-
</pre>
Create a direct link by making square brackets ([[ ]]) around the title such as [[Title]]

The straight lines ( | ) create columns and the straight line with a dash ( |- ) creates a new row in the table.

( |} ) is only used at the very end to finish the coding for the table.

=Overview of 2018 Wiki articles=

{| class="wikitable sortable"
|+June 2017 Wiki Articles
|-
!Group number
!First name
!Second name
!User name
!Link to article
|-
|GN
|FN
|SN
|UN
|[[Name of your Wiki Article]]
|-
|GN
|Hoda
|Vazirinasab
|hoda.vn
|[[Agile project management]]
|-
|-
|3
|David
|Moya Perrino
|David Moya Perrino
|[[Risk Management in Renewable Energy Projects]]
|-
|3
|Sofie
|Melchior Karlson
|s133606
|[[Belbin's team roles]]
|-
|GN
|Sebastian
|Graff Daugaard
|Daugaard
|[[Dealing with conflict in project management]]
|-
|2
|Mehdi
|Abounnasr
|s176504
|[[Project monitoring methods]]
|-
|GN
|Briet
|Hjaltalin
|Briet
|[[Project governance]]
|-
|GN
|Jonas
|Heiberg Larsen
|JonasHL
|[[Risk Management Overview]]
|-
|GN
|Kornpong
|Mahitthiburin
|Akorno
|[[Financial appraisal of project proposals]]
|-
|GN
|Gudmundur
|Hermannsson
|gudmundur
|[[Project Scope Management]]
|-
|GN
|Ína Salome
|Sturludóttir
|Ina
|[[Project scope statement]]
|-
|GN
|Kevinth
|Balasubramaniam
|Kxviinth
|[[Future Workshop]]
|-
|GN
|Davide
|Sartori
|DSartori
|[[Hoshin Kanri]]
|-
|GN
|Julia
|Hoesel
|s172365
|[[Design Thinking]]
|-
|2
|Baptiste
|Hubert
|BaptisteH
|[[Project Management: Life Cycle in Industrial Engineering]]
|-
|GN
|Mint
|Rasmussen
|s133819
|[[Risk Management in Construction Projects]]
|-
|GN
|Vincent
|Oriot
|s172793
|[[Project sponsor]]
|-
|GN
|Torbjørn
|Aleksandersen
|Taleksandersen
|[[Virtual Team Management]]
|-
|GN
|Ragnhildur
|Ragnarsdottir
|Ragnhildur
|[[Brainstorming technique]]
|-
|GN
|Anne
|Dittmann
|Anne
|[[Scheduling: Critical path, PERT, Gantt]]
|-
|1
|Julianna
|Apli
|s172414
|[[Ideation tools]]
|-
|GN
|Hildur
|Gudmundsdottir
|S172763
|[[Contracting and procurement]]
|-
|1
|Christopher
|Søndergaard
|s140234
|[[;-)]]
|-
|GN
|Casper Geertz
|Christensen
|S136445
|[[SWOT]]
|-
|GN
|Demir
|Durovic
|DemirDurovic
|[[Multicultural teams: opportunities and challenges]]
|-
|GN
|Lorenz
|Sieferle
|s172691
|[[Agile Project Management with SCRUM]]
|-
|GN
|Jonas Greaker
|Sjøen
|s173562
|[[Integrated Design Process (IDP)]]
|-
|-
|GN
|Seyed (Habib)
|Bahrami
|Habib
|[[Uniqueness of a project]]
|-

Uniqueness of a project

2018-02-06T12:57:22Z

Habib: Created page with "==Abstract== Here you will write your draft for your wiki article, include at least 1 reference. After add your abstract down in this page there is three buttons: Save page ..."

==Abstract==
Here you will write your draft for your wiki article, include at least 1 reference. After add your abstract down in this page there is three buttons:

Save page
Show preview
Show changes

This buttons are self explanatory, but I recommend to in this first time to press the "show preview" button so you will see the initial changes in your wiki page.

For more information, go to the "help" button on the left column of the page

Articles Spring Term 2018

2018-02-06T12:50:36Z

Habib:

{| class="wikitable"
|+ '''Disclaimer!
|-
|''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 term carefully before starting your wiki article.''
|}

Please complete this table with your group number, full name, username and the title of your article.

To create more lines in the table click '''Edit''' and use the following code to create more lines in the table and replace the example text with your own information:

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
|-
|Group Number
|First Name
|Last Name
|Username
|Link to Article
|-
</pre>
Create a direct link by making square brackets ([[ ]]) around the title such as [[Title]]

The straight lines ( | ) create columns and the straight line with a dash ( |- ) creates a new row in the table.

( |} ) is only used at the very end to finish the coding for the table.

=Overview of 2018 Wiki articles=

{| class="wikitable sortable"
|+June 2017 Wiki Articles
|-
!Group number
!First name
!Second name
!User name
!Link to article
|-
|GN
|FN
|SN
|UN
|[[Name of your Wiki Article]]
|-
|GN
|Hoda
|Vazirinasab
|hoda.vn
|[[Agile project management]]
|-
|-
|3
|David
|Moya Perrino
|David Moya Perrino
|[[Risk Management in Renewable Energy Projects]]
|-
|3
|Sofie
|Melchior Karlson
|s133606
|[[Belbin's team roles]]
|-
|GN
|Sebastian
|Graff Daugaard
|Daugaard
|[[Dealing with conflict in project management]]
|-
|2
|Mehdi
|Abounnasr
|s176504
|[[Project monitoring methods]]
|-
|GN
|Briet
|Hjaltalin
|Briet
|[[Project governance]]
|-
|GN
|Jonas
|Heiberg Larsen
|JonasHL
|[[Risk Management Overview]]
|-
|GN
|Kornpong
|Mahitthiburin
|Akorno
|[[Financial appraisal of project proposals]]
|-
|GN
|Gudmundur
|Hermannsson
|gudmundur
|[[Project Scope Management]]
|-
|GN
|Ína Salome
|Sturludóttir
|Ina
|[[Project scope statement]]
|-
|GN
|Kevinth
|Balasubramaniam
|Kxviinth
|[[Future Workshop]]
|-
|GN
|Davide
|Sartori
|DSartori
|[[Hoshin Kanri]]
|-
|GN
|Julia
|Hoesel
|s172365
|[[Design Thinking]]
|-
|2
|Baptiste
|Hubert
|BaptisteH
|[[Project Management: Life Cycle in Industrial Engineering]]
|-
|GN
|Mint
|Rasmussen
|s133819
|[[Risk Management in Construction Projects]]
|-
|GN
|Vincent
|Oriot
|s172793
|[[Project sponsor]]
|-
|GN
|Torbjørn
|Aleksandersen
|Taleksandersen
|[[Virtual Team Management]]
|-
|GN
|Ragnhildur
|Ragnarsdottir
|Ragnhildur
|[[Brainstorming technique]]
|-
|GN
|Anne
|Dittmann
|Anne
|[[Scheduling: Critical path, PERT, Gantt]]
|-
|1
|Julianna
|Apli
|s172414
|[[Ideation tools]]
|-
|GN
|Hildur
|Gudmundsdottir
|S172763
|[[Contracting and procurement]]
|-
|1
|Christopher
|Søndergaard
|s140234
|[[;-)]]
|-
|GN
|Casper Geertz
|Christensen
|S136445
|[[SWOT]]
|-
|GN
|Demir
|Durovic
|DemirDurovic
|[[Multicultural teams: opportunities and challenges]]
|-
|GN
|Lorenz
|Sieferle
|s172691
|[[Agile Project Management with SCRUM]]
|-
|GN
|Jonas Greaker
|Sjøen
|s173562
|[[Integrated Design Process (IDP)]]
|-
|-
|GN
|Seyed Habib
|Bahrami
|Habib
|[[Uniqueness of a project]]
|-