Talk:Four Stages of Team Development
From apppm
(Difference between revisions)
(→REVIEW by Liclawio) |
(→REVIEW by Liclawio) |
||
| Line 7: | Line 7: | ||
*Beside the overview of the theory. How can it be applied? Which lessons are to be learned, or perhaps traps/pitfalls to be avoided, and how? | *Beside the overview of the theory. How can it be applied? Which lessons are to be learned, or perhaps traps/pitfalls to be avoided, and how? | ||
**How can it be related to project- program- or portfolio management? | **How can it be related to project- program- or portfolio management? | ||
| − | *Figures/tables could be included into the context of the writing. Also difficult to figure, whether they are own figures/tables, or taken from somewhere, and in that case whether usage is ok. | + | |
| − | *The link to reference 1 currently seems to be malfunctioning. | + | *Figures/tables could be included into the context of the writing. Also difficult to figure, whether they are own figures/tables, or taken from somewhere, and in that case whether usage is ok. <span style="color: red">The table is taken from the article I refer to in Reference 1, whose link seems to not be working |
| + | *The link to reference 1 currently seems to be malfunctioning. <span style="color: red">It is a pdf download link, although that wasn’t the problem. I had colon (:) just after the link and that was why it wasn’t working. I have put also the main page where that article can be found | ||
*In general very good spelling and language. | *In general very good spelling and language. | ||
**A few places with strange sentence cutoffs. Seems like something is missing to the sentence (fx. “It is now when members are more committed to seek the team’s objectives and when their competences are higher.”). | **A few places with strange sentence cutoffs. Seems like something is missing to the sentence (fx. “It is now when members are more committed to seek the team’s objectives and when their competences are higher.”). | ||
| − | **It could be a good idea to consider whether the article should be written in British English, or American English, and sticking to the decision. US English will be without the letter u in behavior (similar with colour, flavour etc), where UK English in general use the letter s in places where US will use z (recognise, organise, realise, centralise etc.) | + | **It could be a good idea to consider whether the article should be written in British English, or American English, and sticking to the decision. US English will be without the letter u in behavior (similar with colour, flavour etc), where UK English in general use the letter s in places where US will use z (recognise, organise, realise, centralise etc.) <span style="color: red">I tried to write the article in British English, but those words are always a problem to me. I already changed them into UK English |
| − | **The word “which” does appear a lot, also a few places where it could perhaps make sense to replace with other wordings (fx. “which the structure is and which goals they will seek”) | + | **The word “which” does appear a lot, also a few places where it could perhaps make sense to replace with other wordings (fx. “which the structure is and which goals they will seek”) <span style="color: red">I’m aware of it, but I just can’t find another way to say it |
| + | |||
| + | <span style="color: red">Thank you very much for reviewing my article. It really helped a lot | ||
Revision as of 20:43, 25 November 2014
REVIEW by Liclawio
- In general, a very nice setup of wikipage. Seems like proper use of the wiki platform.
- Nice structure overview, short concise sentences and paragraphs making it easy to read.
- Decent length of article. Would not have any harm in a bit further extensions here and there
- Concise overview of the theory on the field. However, the context of the article seems to be built on some extensive theory. References to these could be good, so the reader has the possibility to get more in depth with the underlying theory.
- Beside the overview of the theory. How can it be applied? Which lessons are to be learned, or perhaps traps/pitfalls to be avoided, and how?
- How can it be related to project- program- or portfolio management?
- Figures/tables could be included into the context of the writing. Also difficult to figure, whether they are own figures/tables, or taken from somewhere, and in that case whether usage is ok. The table is taken from the article I refer to in Reference 1, whose link seems to not be working
- The link to reference 1 currently seems to be malfunctioning. It is a pdf download link, although that wasn’t the problem. I had colon (:) just after the link and that was why it wasn’t working. I have put also the main page where that article can be found
- In general very good spelling and language.
- A few places with strange sentence cutoffs. Seems like something is missing to the sentence (fx. “It is now when members are more committed to seek the team’s objectives and when their competences are higher.”).
- It could be a good idea to consider whether the article should be written in British English, or American English, and sticking to the decision. US English will be without the letter u in behavior (similar with colour, flavour etc), where UK English in general use the letter s in places where US will use z (recognise, organise, realise, centralise etc.) I tried to write the article in British English, but those words are always a problem to me. I already changed them into UK English
- The word “which” does appear a lot, also a few places where it could perhaps make sense to replace with other wordings (fx. “which the structure is and which goals they will seek”) I’m aware of it, but I just can’t find another way to say it
Thank you very much for reviewing my article. It really helped a lot
