Enlightenment Essay Example | Topics and Well Written Essays - 500 words

Enlightenment - Essay Example Three modernists, Nietzsche, Freud, and Kafla, will show how personal feeling or interpretation dictated the modernist period in contrast to an enlightenment point of reality. Friedrich Nietzsche was a German philosopher. Nietzsche promoted nihilism by proclaiming â€Å"God is dead† (Morgan, 36). Instead of interpreting God as an all powerful creator, Nietzsche believed God was used to create a society of morality without a purpose. While an individual from the enlightenment might reason that God and morality must exist for society to function smoothly, Nietzsche believed morality needed to be examined without the excuse of God. Nietzsche’s reality was looking into philosophical arguments that are still up for debate to this day. Unlike the reasoning of the enlightenment age, Nietzsche’s views are debatable. They cannot be proven beyond a shadow of a doubt. Franz Kafka was a modernist writer. He was born in Germany. Instead of using reasoning in reality, Kafka wrote stories that today would be considered science fiction. An example is The Metamorphosis. In this story, Kafka had a traveling salesman turn into a huge insect (Kafka). An Enlightenment influenced thinker would never think of this plot, because humans cannot turn into huge insects. Kafka would have probably responded to this line of thinking by replying â€Å"not yet†. Modernists believe that not everything can be explained by human reasoning yet. The modernist keeps theorizing until the day their thoughts are proven. However the modernist does not stop thinking just because they cannot prove their theories. Sigmund Freud was a German doctor that pioneered psychoanalysis and psychotherapy. He theorized that every human has an id, ego, and superego. Freud also laid out different theories about human development like the anal complex, Oedipus complex, penal envy, and so forth. All of these theories, at the time, could not be proven. Today they cannot be proven, but the

IT Systems Planning and Acquisition Essay Example | Topics and Well Written Essays - 750 words

IT Systems Planning and Acquisition - Essay Example However, usually later in execution of the project, the stakeholders or beneficiary organization may require some additional or different software modules or deliverables as defined in the project scope document, this phenomenon referred as scope creep. â€Å"Scope creep refers to the change in a project's scope after the project work has started. Typically, the scope expands by the addition of new features to an already approved feature list. As a result, the project drifts away from its original purpose, timeline, and budget.† (Alexandrou, 2011). In 2011, the Baker and Greer provided guidelines and shared the top 8 best practices for minimizing and avoiding scope creep of the project. I do agree that by implementing the guidelines of the Baker and Greer, the project manager may minimize the scope creep but the guidelines should more be refined and expanded in order to avoid or eliminate the scope creep of a project. In this document I would discuss the guidelines provided by the Baker and Greer, analyze them critically and would add the best practices or guidelines provided by other great authors along with the rationale. ... There are certain reasons for the scope creep have been identified include poor requirements analysis, involving the users in the later phases of the project, ignoring the convolution of the project, change control lacking and Gold plating. Some more reasons include miscommunication with customer, insincere customer with an unwavering policy of value for free, week project management methodology and resources (Vandermilt, 2011). It is pertinent to mention here that the Baker and Greer have not taken into account some of the reasons of scope creep in their guidelines that are mentioned above. Therefore, in order to avoid or minimizing the guidelines may be expanded and enhanced by including a plan for scope creep, getting formal signoff from the customer, document change control, reviewing the similar projects and lesson learnt reports, using standards for project management and certified project management professionals (Bellanca, 2010). Scope creep rises from commencement of the pro ject due to ambiguous planning. Therefore, it would be recommended to develop a plan for scope creep in which rules for handling the scope creep would be mentioned. Scope creep should be handled from the beginning to an end of the project through prescribed change control document. Change control refers to variation to the business processes, user or the technical requirements once sign-off has been taken place on the project scope document. Scope creep happens more repeatedly when formal sign-off the stakeholders have not signed off the project scope document. A number of business cultures evades the actual signing-offs the project scope document, due to the fear of responsibility ambiguous and incomplete requirements.