|
|
| (9 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | == S132463 Review ==
| |
| − | I really like your change management description. It is easily understandable and provides a good overview. Also the use of pictures is very good. In general I think this could be an interesting article, but it is still somewhat unclear here and there on what message you want to convey. However, it should be pretty easy to fix.
| |
| | | | |
| − | Answer:Thank you ok:)
| |
| − |
| |
| − | Things I think you should focus on in general are:
| |
| − | *It was fairly late I realized what the article actually talked about. Be very clear on what program management theory and frameworks add to the change management at an early stage of the article. It is somewhat unclear until the very end where the two management theories are finally combined.
| |
| − |
| |
| − | Answer: I have tried to fix this
| |
| − |
| |
| − | *Are all pictures free of copyright?
| |
| − |
| |
| − | Answer: I believe it is, since I reference to the author, and the books i use.
| |
| − |
| |
| − | *References should be done in wiki style references and with appropriate annotation of source (author(s), year, journal name, etc.).
| |
| − | **<nowiki><ref name=RefName>Information here. This is what can be found in the bottom.</ref></nowiki>
| |
| − | **You can reference to the same by using the "RefName" like this: <nowiki><ref name=RefName></ref></nowiki>. Be aware that Ref-names are case sensitive.
| |
| − | **Include </references> at the bottom of your page to get all reference information shown
| |
| − | *Include categories to your article (see front page here on the apppm.wiki). fx <nowiki>[[Category:Uncertainty]]</nowiki>. This should just be added somewhere in the wiki-code. Maybe as the very last.
| |
| − |
| |
| − | Answer: It was my plan to do right wiki-style references, now it is fixed, ty:)
| |
| − |
| |
| − | === "Introduction" ===
| |
| − | *The abstract is a good introduction. It however takes a couple of read-throughs before the combined use of change/program management is clear. Try to clearly state that program management is not used instead of change management, but used as a "platform" of initiatives/projects throughout the change process.
| |
| − | **The small introduction before is a bit strange. I suggest writing it together with the abstract, and removing the "abstract" name.
| |
| − |
| |
| − | Answer: I have tried to be more specific, I got your point ty:)
| |
| − |
| |
| − | === Change management ===
| |
| − | *Good easily understandable chapter, with relevant information.
| |
| − |
| |
| − | Answer: Check
| |
| − |
| |
| − | === Program management ===
| |
| − | *As with the introduction; be carefull not to see program management as a change-thing. I suggest you first define program management (as normally used/described), then go to describing why this is relevant in a change management context.
| |
| − | *The use of bold text below the box is not easily understandable. Maybe use a bullet form, areas (start line with ; for bold/headline, and : for explanation) or similar.
| |
| − |
| |
| − | Answer: I used both of these suggestions...
| |
| − |
| |
| − | === Tools and methods ===
| |
| − | *In general a good easy-to-get-overview chapter
| |
| − | *Again the use of bold text within chapters can seem distracting. I suggest bullets or similar for "lists".
| |
| − |
| |
| − | Answer: Bulletpoints Check:)
| |
| − |
| |
| − | === Application of Program Management in an Organisational Change ===
| |
| − | *I like the picture used for illustration of how program is interacting with change management
| |
| − | *Again, I feel you say that program management is a method for (only) change management. Is that what you want to convey?
| |
| − |
| |
| − | Answer: No it is not what I am trying to convey:) I fixed this...
| |
| − |
| |
| − | === Conclusion ===
| |
| − | *No comments
| |
| − |
| |
| − | == Maxatzi review ==
| |
| − |
| |
| − | I start with comments of each part and I finish with some general comments regarding the whole article.
| |
| − |
| |
| − | === Abstract ===
| |
| − |
| |
| − | *Within the summary section is the “Abstract” section, I think that it would be nice if these two were merged into one and change it a bit so it will have the logical flow that you follow in your article. Moreover, you could also describe briefly why/how the change management program would help during the organisational change (like you do in the conclusion of the article).
| |
| − |
| |
| − | Answer: I have tried to do so:) ty
| |
| − |
| |
| − | *At some point in the abstract you are using the 2nd person, which it would sound better if it was 3rd.
| |
| − |
| |
| − | Answer: I will do my best to fix this
| |
| − |
| |
| − | === Change Management ===
| |
| − |
| |
| − | *I liked the structure of the section, you started with the general model of change process focusing on the key steps of the change process and then connecting it with the survival of the fittest and closing with the challenges that a managers will face.
| |
| − |
| |
| − | Answer: Ok ty:)
| |
| − |
| |
| − | *I think that the Lewin’s model could be in a separate section with clear description on which step is every paragraph about and say that it is also shown in the figure. Maybe changing the introduction sentences into more positive? “The subject is simply too complex” is a sentence that makes me not want to use it! And “The most simplified way..” it would be better to be “one of the most simplified ways..” or something similar because it seems that we are 100% sure about this.
| |
| − |
| |
| − | p.s. if I’m not mistaken you miss explaining a bit the “Refreeze” step of the model.
| |
| − |
| |
| − | Answer: I used all of this...
| |
| − |
| |
| − | *Regarding the challenges that managers in charge of operation face, maybe you should spend one paragraph to explain in one sentence for each one why they are challenges, instead of just listing them and their references.
| |
| − |
| |
| − | Answer: I fixed it in a slightly different way, but ty for the notice:)
| |
| − |
| |
| − | === Program Management ===
| |
| − |
| |
| − | *Maybe the last paragraph with the definitions is a bit irrelevant as they are not used anywhere else in the text. I wouldn’t mind if it was not there for example!
| |
| − |
| |
| − | Answer: They are still there, for all readers to understand the concept.:)
| |
| − |
| |
| − | *PMI stands for Project Management Institute, right? Maybe you could say it just to be more clear for the reader.
| |
| − |
| |
| − | Answer: Check:)
| |
| − |
| |
| − | *I didn’t understand if the 5 domains that you describe are all necessary steps for the Program Management. It would be nice if you could describe a bit more some of them cause it seems like Program benefit management, program stakeholder engagement and program governance are not so important tools.
| |
| − |
| |
| − | Answer: I have chosen to keep the descriptions, hence it gives an overview of what PM have to offer.
| |
| − |
| |
| − | *You miss the !APPPM!SOMEONESTOPIC
| |
| − |
| |
| − | Answer: Ty, my internal references is now done:)
| |
| − |
| |
| − | === Application of Program Management ===
| |
| − |
| |
| − | *I would prefer to see the 4 stages clearly stated with bullet points or in different paragraphs. Being in the same paragraph seems a bit confusing.
| |
| − |
| |
| − | Answer: Check! ty
| |
| − |
| |
| − | *Somewhere you use 1st person (“I have chosen”).
| |
| − |
| |
| − | Answer: Fixed, that sentence is now refraced
| |
| − |
| |
| − | *This part was really well-structured, it was easy for me to follow your thoughts and your writing.
| |
| − |
| |
| − | Answer: ok ty
| |
| − |
| |
| − | === Conclusion ===
| |
| − |
| |
| − | *Simple, short and to the point. Not more than it should be!
| |
| − |
| |
| − | Answer: Bummelum
| |
| − |
| |
| − | === General comments ===
| |
| − |
| |
| − | *I thought that the article was more about the integration of methods of Change Management during an orgnisational change but after reading it I can say that it is more focused on the contribution of program management during this change. I don’t know if this was what you had in your mind but maybe the title should be a bit different like “The role of Program management in organizational change” or something similar. But since this is not possible if I'm right, you could just change a bit the abstract, saying that is referring to change management as a supportive activity.
| |
| − |
| |
| − | Answer: Great point! I would like to change the heading;/ I have updated the abstract
| |
| − |
| |
| − | *There are some spelling, grammar and syntax mistakes that makes the understanding a bit difficult at some points. Some sentences are too short without any verbs and some sentences start with “why” or “which” without being a question, which is fine and understandable when you are talking but when it is written is a bit confusing. I think it will be easy to identify them if you read it again carefully ;)
| |
| − |
| |
| − | Answer: Ok I will try to fix this.
| |
| − |
| |
| − | *I think that you should work a bit with the references. You use them in different ways and they look a bit inconsistent. At some points you have links, at others names of writers, at the end of the “Change Management” part you have a reference which doesn’t really fit there from my point of view, and the video didn’t work for me. Finally, most of your references seem to be websites where you don’t really know the writer.
| |
| − |
| |
| − | Answer: Done deal, and the video is working(wrong code:))
| |
| − |
| |
| − | *I liked your figures, they were all understandable and clear and I liked the way that you changed the “Key Steps in the Change Process” figure in the last part.
| |
| − |
| |
| − | Answer: Ty
| |
| − |
| |
| − | *I think that the article fits in the PPP management as it is a clear topic which interesting summary that provides an overall view of the importance of program management during the organisational change.
| |
| − |
| |
| − | Answer: Well that was nice:) ty
| |
