Talk:The Role of Program Management in an Organisational Change

From apppm
Revision as of 23:48, 25 November 2014 by S132463 (Talk | contribs)

Jump to: navigation, search

Contents

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.

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.
  • Are all pictures free of copyright?
  • References should be done in wiki style references and with appropriate annotation of source (author(s), year, journal name, etc.).
    • <ref name=RefName>Information here. This is what can be found in the bottom.</ref>
    • You can reference to the same by using the "RefName" like this: <ref name=RefName></ref>. 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 [[Category:Uncertainty]]. This should just be added somewhere in the wiki-code. Maybe as the very last.

"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.

Change management

  • Good easily understandable chapter, with relevant information.

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.

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".


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?


Conclusion

  • No comments
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox