IT Project's Outcome: Identify Causes

Identifying Success and Failure Causes for an IT Project and Selecting a Project Management Methodol

Answered

Preparation

You are expected to keep a reflective journal recording what you have learned (including your reflections) in your classes, in your study

Groups and, most importantly, as part of your self-directed study (your own research). Your research should also consist of locating and critically reviewing peer reviewed articles related to this topic.

The scenario from assessment 1 is also to be used for this assessment.

Using your reflective journal, peer reviewed literature and other sources, write a report addressing the following “user story”As an IT project manager, I will identify and analyse the potential causes of success/failure of my IT project (scenario), so that I can clearly justify how the selected project management methodology could help addressing them.

Note Your discussion should specifically relate to your scenario. A mere theoretical discussion with no reference to your scenario will be awarded no more than 25% marks.

Length

1,500 words (excluding references and diagrams), with 10% tolerance.

Late submission will receive penalty mark according to Wintec policy.

Assessment Criteria – Report	Weighting	Exemplar (5)	Excellent (4)	Good (3)	Needs Improvement (2)	Poor (1)	Non-existent (0)
Description and adequacy of selected project/scenario	mandatory
Potential causes of success identified and analysed	20%	Potential causes of success exemplary identified and analysed	Potential causes of success fully identified and analysed	Potential causes of success identified and analysed	Potential causes of success poorly identified and analysed	Potential causes of success not analysed	Potential causes of success not identified
Potential causes of failure identified and analysed	20%	Potential causes of failure exemplary identified and analysed	Potential causes of failure fully identified and analysed	Potential causes of failure identified and analysed	Potential causes of failures poorly identified and analysed	Potential causes of failure not analysed	Potential causes of failure not identified
Selection and justification of project management methodology	10%	Selected PM methodology exemplary justified	Selected PM methodology fully justified	Selected PM methodology justified	Selected PM methodology poorly justified	PM methodology selected but not justified	PM methodology not selected and justified
Justification of how selected project management methodology could help addressing identified causes of success/failure	20%	How selected PM methodology could help addressing identified causes of success/failure exemplary justified	How selected PM methodology could help addressing identified causes of success/failure fully justified	How selected PM methodology could help addressing identified causes of success/failure justified	How selected PM methodology could help addressing identified causes of success/failure poorly justified	How selected PM methodology could help addressing identified causes of success/failur e not justified	PM methodology not selected
Synthesis of information sources and quality of sources cited	10%	Exemplar quantity/quality of reputable sources	Excellent quality/quantity of reputable references used	Good quality/quantit y of reputable references used	Poor quality/quantity of reputable references used	Poor quality/quant ity of references used	No (reputable) references used
Grammar, spelling and punctuation	5%	Exemplar use of grammar, spelling and punctuation	Excellent use of grammar, spelling and punctuation	Good use of grammar, spelling and punctuation	Regular use of grammar, spelling and punctuation	Poor use of grammar, spelling and punctuation	Extremely poor use of grammar, spelling and punctuation
Correct use of APA referencing	5%	Exemplar use of APA referencing	Excellent use of APA referencing	Good use of APA referencing	Regular use of APA referencing	Poor use of APA referencing	No use of APA referencing
Structure, length and professional presentation of the report	10%	Exemplar structure/ length/presentati on	Excellent structure/ length/presentati on	Good structure/ length/presentati on	Regular structure/ length/presentati on	Poor structure/ length/presentati on	Extremely poor structure/ length/presentati on
TOTAL MARK

This assessment is worth 35% of your final grade. Please note that this is an individual assignment although you are encouraged to learn in study groups, collaboration in terms of the planning and writing of this report is not permitted.

Keywords: <insert your own keywords here, separated by commas. Typically, from 2 to 4>

<The first section should be named Introduction. Naming of the remaining sections is at your discretion. The last section of the article should be a reference list. The purpose of introduction is to introduce the topic to the reader as well as to present the remaining sections of the article>. Finalize this section by presenting which sections are still to come and briefing the content in each one>.

2. <Name your own section(s) and subsections>

<Always include text between a section in its subsections>. <As an example, for this assignment, you can start introducing/presenting the company and project of your scenario (although you may want to use a new section for this). After that, how about a section to identify and analyse the potential causes of success/failure of your IT project. After, expose the selected project management methodology and why have you selected it. Do not forget to include how the methodology helps addressing the causes> How many sections (and subsections)? It is up to you: it is your article, remember?>

Get instant help from 5000+ experts for