Main Page
(→Wiki article requirements) |
(→Article Type 1: Explanation and Illustration of a Method) |
||
| Line 51: | Line 51: | ||
The articles are expected to adhere to the following structure: | 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 | + | * ''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 | + | * ''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 | + | * ''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. | + | * ''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 === | === Article Type 2: Description of a Relevant Case Study === | ||
Revision as of 11:32, 30 August 2015
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:Programme Management]].
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
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).
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
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}}
