Talk:Creating a positive culture around failure in project management

From apppm
Jump to: navigation, search

reviewed by Saeh0803

To start with I would place the Introduction in the beginning of the document, followed by a table of content and please add some more sentences in introduction to describe the topic :) I miss introduction of your topic..

long sentences, make them a bit shorter :)

Over all i like your topic and your article, your English is understandable.. some part is very short, maybe you can describe a bit more, so it gives sense for reader. (if it is possible)


I hope you can use my comments best of luck

Thank you, hereby done

Sube - Review

Greetings

Congratulation! you have wrote a wiki style article:) Thank you ;)

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:)

Good idea! I will definitely integrate this

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

That is a good question and i see that i failed to mention is, so i will put it in limitations (that i also thought was lacking something, so thanks!)


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. 

Yea, i didn't know we were ment to move this, but great! I found out how to do it.


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!

I see what you're saying. I will take it into account..


Acceptance of failure

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

I found it, done


Learn from your mistakes

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

That is a great idea. I will try


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

Well i think this misunderstanding comes from a spelling error. Hereby corrected and FFE is used Caption.


The original Spiral Model

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

Check


Adaption of the Spiral Model

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

You're right


Visualized testing and prototyping area

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

Check


Discussion of the method

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

"Check"


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":)

Super

Nice article:) Hope you can make use of my recommendations... Good Luck Have Fun! Tak for hjælpen!

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox