Main Page
(→Evaluation of Wiki Articles) |
(→Evaluation of Wiki Articles) |
||
| Line 85: | Line 85: | ||
The quality criteria used to evaluate the articles are: | The quality criteria used to evaluate the articles are: | ||
| − | * Quality of the summary: Does the summary make the key focus, insights and/or contribution of the | + | * Quality of the summary: Does the summary make the key focus, insights and/or contribution of the article clear? |
| − | article clear? | + | * 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? |
| − | * Structure and logic of the article: Is the argument clear? Is there a logical flow to the article? Does | + | * Grammar and style: Is the writing free of grammatical and spelling errors? Is the language precise without unnecessary fill words? |
| − | one part build upon the other? Is the article consistent in its argument and free of contradictions? | + | * Figures and tables: Are figures and tables clear? Do they summarize the key points of the article in a meaningful way? |
| − | * Grammar and style: Is the writing free of grammatical and spelling errors? Is the language precise | + | * 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? |
| − | without unnecessary fill words? | + | * 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? |
| − | * Figures and tables: Are figures and tables clear? Do they summarize the key points of the article in | + | * 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? |
| − | a meaningful way? | + | |
| − | * 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? | + | |
| − | * 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? | + | |
| − | * 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? | + | |
The process for developing the article is outlined in Figure 1: Process for Individual Assignment. There are a number of deliverables for the individual assignment (see class schedule for timing): | The process for developing the article is outlined in Figure 1: Process for Individual Assignment. There are a number of deliverables for the individual assignment (see class schedule for timing): | ||
Revision as of 17:20, 31 July 2016
Welcome to 42433 - Advanced Engineering Project, Program and Portfolio Management and thank you for your interest!
As this is a 10 ECTS course, there will be a significant portion of group work (analysing a real-life case together with a partner organization), as well as an individual assignment, in addition to the classroom lectures. The expectation with a 10 ECTS course is that you will spend 1 day per week on coursework, in addition to attending the class Tuesdays and Fridays.
Weeks 1-4 will be devoted to the individual assignment, which will focus on writing a Wiki-style article outlining either a project, program or portfolio management method (or concept or theory) or documenting a relevant case. The articles are expected to adhere to academic standards of rigor, clarity and referencing.
In the group assignment in weeks 5-13, you will be working together with a partner organization to analyze a particular project, program or portfolio management challenge. You will either provide detailed analytics to characterize the challenge, or develop recommendations for solutions. The groups have to identify their own partner organization - for example a company, NGO or government agency - that they will be working with. This will be done in parallel to the individual assignment in weeks 1-4. The results will be presented to the class and judged in week 13.
We are very excited about the course and are looking forward to welcoming you soon!
Best wishes for now,
Josef, Christian and Joana.
Contents |
Topics
Please add a couple of categories to your page, at least consider if the page falls into the category of
- Project Management
- Program Management, or
- Portfolio Management
and whether it relates to
- Complexity
- Uncertainty, or
- Human Behaviour
other categories could also be
- Lean program management
- Systems Engineering
- Agility
- ...
You can add categories to your page by typing in [[Category:''category name'']] e.g. [[Category:Program Management]].
Wiki article requirements
The individual assignment consists of writing a Wiki-style article outlining either a project, program or portfolio management tool, concept or theory or documenting a relevant case. The articles will become part of a DTU-Wiki on Advanced Project, Program and Portfolio Management and will serve as a resource to practitioners in industry and government, as well as future students. The best articles will be considered for publication in a handbook on the ISO 21900 Standard on Project Management.
The primary objective is that the article is relevant to project, program or portfolio management practitioners and can contribute to a growing body of knowledge in the area. All articles should be concise, sharp, insightful, academically sound and relevant to practitioners, and target a length of approximately 3,000 words, excluding annotated bibliography (see below).
Once you have chosen the topic for your article please go to this page: Articles Fall Term 2015 and complete the table following the instructions.
You can choose to work on one of two types of articles:
Article Type 1: Explanation and Illustration of a Method
The focus of a “method article” is on outlining a relevant project, program or portfolio management method (or concept, theory or tool). Examples are:
- Classic project, program or portfolio management methods, such as: Gantt Charts, Work Breakdown Structures, portfolio graphs, risk management, cost and schedule estimation methods, Key Performance Indicators, stakeholder matrices
- Key theories relevant to the management of projects, programs or portfolios, such as: theory of constraint, cognitive and decision making biases, communication theory, project management competencies, critical chain theory, or stages of team development.
The articles are expected to adhere to the following structure:
- Big idea: describe the tool, concept or theory and explain its purpose. The section should reflect the current state of the art on the topic
- Application: provide guidance on how to use the tool, concept or theory and when it is applicable
- Limitations: critically reflect on the tool/concept/theory. When possible, substantiate your claims with literature
- Annotated bibliography: Provide key references (3-10), where a reader can find additional information on the subject. Summarize and outline the relevance of each reference to the topic. (around 100 words per reference). The bibliography is not counted in the suggested 3000 word target length of the article.
Article Type 2: Description of a Relevant Case Study
The focus of this type of article is to tell the story of a specific project, program or portfolio. The description should not just be a general overview, but focus on an exciting, unusual or innovative aspect. Examples include new forms of collaboration, a specific method or practice that worked particularly well, an insightful stakeholder engagement, particular high level of performance etc.
The article should adhere to the following structure:
- Context: briefly describe the case and why it is insightful
- Challenge: explain the particular problem faced by the project, program or portfolio which led to the innovation.
- Solution: describe the innovative practice and why it was perceived to work
- Implication: Critical reflection on the case and its potential contribution to project, program and portfolio (e.g. when could it be used by others? Does it make us rethink any of the key concepts or common practices in project, program and portfolio? How?). When possible, substantiate your claims with literature
- Annotated bibliography: Provide key references (3-10), where a reader can find additional information on the subject. Summarize and outline the relevance of each reference to the topic. (around 100 words per reference). The bibliography is not counted in the suggested 3000 word target length of the article.
Evaluation of Wiki Articles
The quality criteria used to evaluate the articles are:
- Quality of the summary: Does the summary make the key focus, insights and/or contribution of the article clear?
- 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?
- Grammar and style: Is the writing free of grammatical and spelling errors? Is the language precise without unnecessary fill words?
- Figures and tables: Are figures and tables clear? Do they summarize the key points of the article in a meaningful way?
- 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?
- 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?
- 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?
The process for developing the article is outlined in Figure 1: Process for Individual Assignment. There are a number of deliverables for the individual assignment (see class schedule for timing):
- Abstract of the proposed article
- Version 1 of article for peer review
- 2-3 peer reviews of articles written by others
- Version 2 of article incorporating peer review received for own article
- Response to peer reviewers outlining how comments were addressed
- Evaluation of quality of peer review feedback, as well as evaluation of quality of “Version 2” of the articles you reviewed.
Link to Articles
Articles Fall Term 2016
On the following page you will find links to a table you need to fill out with all the articles from Fall Term 2015:
Articles Fall Term 2015
On the following page you will find links to all the articles from Fall Term 2015:
Articles Fall Term 2014
On the following page you will find links to all the articles from Fall Term 2014:
Practical
Consult the User's Guide for information on using the wiki software.
Go to Help or follow the link in the navigation bar to find instructions on basic configurations
Getting started
The followin links can help you some of the settings available - otherwise google your issue and write mediawiki, this will also results in a lot of hits on how to do different things
Create a Page
To create a page follow these steps: 1. Write the potential name of your page in the search box in the upper right hand corner 2. Press go 3a. If the page does not exist press the link to create the page 3b. If the page does exist have a look at the page,
- If the topic is what you wanted to write about, talk to Christian or Josef
- If the page is not the topic you wanted to cover design a new name for the page and go back to step 1
4. Start writing on the page, if you need assistance for the formatting, look below or go to the Help page
Formatting and adding items to your page
Text
- Text formatting link: Formatting
Images
- Images editing link: Images
- Code: [[File:example.jpg]]
Videos
- EmbedVideo editing link: Videos
- Code: {{#ev:youtube|video URL}}
- Code: {{#ev:youtube|video url|1000|right|Let eet GO|frame}}
