Talk:Creating a positive culture around failure in project management

From apppm
(Difference between revisions)
Jump to: navigation, search
(→‎reviewed by Saeh0803: new section)
 
(→‎Sube - Review: new section)
Line 2: Line 2:
  
 
dfkdlfkld
 
dfkdlfkld
 +
 +
== Sube - Review ==
 +
 +
Greetings
 +
 +
Congratulation! you have wrote a wiki style article:)
 +
 +
First of all, I think your writing skills are very sufficient, all text is readable and make sense! Which is very nice...
 +
 +
Secondly, I believe that the combination of topics your chose is relevant and I see the purpose, eventhough it havent been tried out in practice:)
 +
 +
Thirdly, NOTE that the review text will flow out of screen to the right hand side... I do not know how to fix this!
 +
 +
Nevertheless, I have made you some recommendations on how I believe the article can improve.
 +
 +
General Guidelines;
 +
* Quotes are hidden in the text, maybe make them Italic, so they stand out from the normal text. Btw, you got a lot of quotes which I think is good:)
 +
* As a reader im wondering, which organisations benefits from the methodology you describe? Can any organisation benefit from this, or is it more innovation oriented organisation? - maybe in the limitation of the method. I know you write the method is for projects managers - but are there any other limitations... 
 +
----
 +
'''Start''':
 +
* When I am entering the page, the first thing I see is a table of contents. I think it would be beneficial if you peptalked the topic a bit before the content is presented. That way around, as a reader you make more sense of the table of content, and know why this topic is even relevant.
 +
* You could add the Article Category there aswell, maybe in the end.
 +
----
 +
'''Introduction'''
 +
* I believe this section is more like "Research Area" or "Scope". I feel like an introduction is more about the topic and the reason why it is relevant - You could make a abstract/intro to intreak the reader and then rename the Introduction.
 +
* Where are the Embracing Failure Key values? It sounds interresting:) I cannot find them!
 +
 +
----
 +
'''Acceptance of failure'''
 +
* Minor thing: I wondered who Cass was, untill it maked sense, Cassidy. Might want to edit Cass to Cassidy.
 +
 +
----
 +
'''Learn from your mistakes'''
 +
* Consider some general writing about Single and Double Loop learning...
 +
 +
----
 +
'''How is embracing failure used'''
 +
* I think you might want to descibe what the Fuzzy Front End is all about, I kind of get it, but I am not sure...
 +
* Revisit this sentence; Embracing Failures role in the Fuzzy Front End of a project The first stages of a project or the planning part of a program are identified as the Fuzzy Front End (FFE), which hold a lot of importance in the execution of the project.
 +
* Remember Fuzzy Front End, some parts it is fuzzy front end. - Maybe use the FFE - but personally I belive Fuzzy Front End sounds good:)
 +
* Make sure you do this; "This has also served as an inspiration to the thesis of the concrete implementation suggestions this article is presenting."
 +
----
 +
'''The original Spiral Model'''
 +
* Minor thing; Remember to make puncturemarks after each bulletpoint.
 +
 +
----
 +
'''Adaption of the Spiral Model'''
 +
* I think adaptation or application is more correct - do not kill me if I am wrong.
 +
 +
----
 +
'''Visualized testing and prototyping area'''
 +
* Visualized testing and prototype areas?
 +
* First sentence: Remove "from it".
 +
 +
----
 +
'''Discussion of the method'''
 +
* Nevertheless is in one word:)
 +
* Last section; long sentence...
 +
 +
----
 +
'''Conclusion'''
 +
* The start is klumpsy "It has in this article been tried... " - rewrite:) Maybe something like; "This article provides projects managers with a method to improve their blabla.."
 +
* Second section, revisit the whole sentence "...the Spiral Model should be able to help with in..." I get the point but make sure to visualise that it is a "indskudt sætning":)
 +
 +
 +
Nice article:) Hope you can make use of my recommendations... Good Luck Have Fun!

Revision as of 23:09, 25 November 2014

reviewed by Saeh0803

dfkdlfkld

Sube - Review

Greetings

Congratulation! you have wrote a wiki style article:)

First of all, I think your writing skills are very sufficient, all text is readable and make sense! Which is very nice...

Secondly, I believe that the combination of topics your chose is relevant and I see the purpose, eventhough it havent been tried out in practice:)

Thirdly, NOTE that the review text will flow out of screen to the right hand side... I do not know how to fix this!

Nevertheless, I have made you some recommendations on how I believe the article can improve.

General Guidelines; 

* Quotes are hidden in the text, maybe make them Italic, so they stand out from the normal text. Btw, you got a lot of quotes which I think is good:)
* As a reader im wondering, which organisations benefits from the methodology you describe? Can any organisation benefit from this, or is it more innovation oriented organisation? - maybe in the limitation of the method. I know you write the method is for projects managers - but are there any other limitations...

Start: 

* When I am entering the page, the first thing I see is a table of contents. I think it would be beneficial if you peptalked the topic a bit before the content is presented. That way around, as a reader you make more sense of the table of content, and know why this topic is even relevant.
* You could add the Article Category there aswell, maybe in the end.

Introduction 

* I believe this section is more like "Research Area" or "Scope". I feel like an introduction is more about the topic and the reason why it is relevant - You could make a abstract/intro to intreak the reader and then rename the Introduction. 
* Where are the Embracing Failure Key values? It sounds interresting:) I cannot find them!

Acceptance of failure 

* Minor thing: I wondered who Cass was, untill it maked sense, Cassidy. Might want to edit Cass to Cassidy.

Learn from your mistakes 

* Consider some general writing about Single and Double Loop learning...

How is embracing failure used 

* I think you might want to descibe what the Fuzzy Front End is all about, I kind of get it, but I am not sure... 
* Revisit this sentence; Embracing Failures role in the Fuzzy Front End of a project The first stages of a project or the planning part of a program are identified as the Fuzzy Front End (FFE), which hold a lot of importance in the execution of the project.
* Remember Fuzzy Front End, some parts it is fuzzy front end. - Maybe use the FFE - but personally I belive Fuzzy Front End sounds good:)
* Make sure you do this; "This has also served as an inspiration to the thesis of the concrete implementation suggestions this article is presenting."

The original Spiral Model 

* Minor thing; Remember to make puncturemarks after each bulletpoint.

Adaption of the Spiral Model 

* I think adaptation or application is more correct - do not kill me if I am wrong.

Visualized testing and prototyping area 

* Visualized testing and prototype areas?
* First sentence: Remove "from it".

Discussion of the method 

* Nevertheless is in one word:)
* Last section; long sentence...

Conclusion 

* The start is klumpsy "It has in this article been tried... " - rewrite:) Maybe something like; "This article provides projects managers with a method to improve their blabla.."
* Second section, revisit the whole sentence "...the Spiral Model should be able to help with in..." I get the point but make sure to visualise that it is a "indskudt sætning":)

Nice article:) Hope you can make use of my recommendations... Good Luck Have Fun!

Retrieved from "http://wiki.doing-projects.org/index.php?title=Talk:Creating_a_positive_culture_around_failure_in_project_management&oldid=3444"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox