IT project management
PART 1: PROJECT MANAGEMENT SCENARIO (20%)
This part of the in-course assessment is intended to address Learning Outcomes 1, 2. For this part of the assessment, you are required to critically scope and author a project management case scenario which should contain sufficient appropriate detail for analysis and determination of an IT-related project management strategy, plan and toolset. This scenario could be fictitious or based on a real business need.Start with describing the business case and value(s) of the project, then add both qualitative and quantitative details to explain the scenario in more depth. The data might be used in the formulation of your plan or toolset. You can use appendices for finer details.
Word count for Part1: approx. 1,000 words (guideline only).
PART 2: PROJECT MANAGEMENT STRATEGY & PLAN (50%)
This part of the in-course assessment is intended to address Learning Outcomes 1, 2, 5, 6, 7. In this part of the assessment you will review, develop and defend a case for adopting a specific project management life cycle (PMLC) and develop a suitable project management plan. The aim is to demonstrate knowledge of alternative philosophies and project planning artefacts, critically evaluating which broad methodological approach (and toolset) would fit your described project scenario. It is therefore expected that you will analyse your scenario, compare and contrast project management approaches, then select the most appropriate ones for your scenario and justify your choices.
Word count for Part 2: approx. 2,000 words (guideline only).
PART 3: TOOLSET (30%)
This part of the in-course assessment is intended to address Learning Outcomes 3, 4. In this part of the submission you are required to employ a suitable toolset portfolio, demonstrating how the tools advocated would / could be applied to the given project management scenario. You may use live case data, plausible invented data, or an exemplar, illustrative presentation of critical tools in your toolset.
Word count for Part 3: approx. 300 words (guideline only),plus associated illustrations
Philosophies,
Tools & Technologies CIS4021-N
CIS4021_ICABriefV2
Philosophies, Tools & Technologies CIS4021-N CIS4021_ICABriefV2
Project Management Philosophies and Tools CIS4021-N
ICA Requirements
PART 1:
PROJECT MANAGEMENT SCENARIO (20%)
This part of the in-course assessment is intended to address Learning Outcomes 1, 2. For this part of the assessment, you are required to critically scope and author a project management case scenario which should contain sufficient appropriate detail for analysis and determination of an IT-related project management strategy, plan and toolset. This scenario could be fictitious or based on a real business need. Start with describing the business case and value(s) of the project, then add both qualitative and quantitative details to explain the scenario in more depth. The data might be used in the formulation of your plan or toolset. You can use appendices for finer details.
Word count for Part1: approx. 1,000 words (guideline only).
PART 2:
PROJECT MANAGEMENT STRATEGY & PLAN (50%)
This part of the in-course assessment is intended to address Learning Outcomes 1, 2, 5, 6, 7. In this part of the assessment you will review, develop and defend a case for adopting a specific project management life cycle (PMLC) and develop a suitable project management plan. The aim is to demonstrate knowledge of alternative philosophies and project planning artefacts, critically evaluating which broad methodological approach (and toolset) would fit your described project scenario. It is therefore expected that you will analyse your scenario, compare and contrast project management approaches, then select the most appropriate ones for your scenario and justify your choices.
Word count for Part 2: approx. 2,000 words (guideline only).
PART 3: TOOLSET (30%)
This part of the in-course assessment is intended to address Learning Outcomes 3, 4. In this part of the submission you are required to employ a suitable toolset portfolio, demonstrating how the tools advocated would / could be applied to the given project management scenario. You may use live case data, plausible invented data, or an exemplar, illustrative presentation of critical tools in your toolset.
Word count for Part 3: approx. 300 words (guideline only), plus associated illustrations
Finally, the presentation and construction of the documentation (Part 1, 2 and 3) is important and it is expected that you will include a table of contents, numbered headings and subheadings as well as a full list of references mirroring your in-text references or citations.
ICA Deliverables
The work you will submit must contain the three ICA parts
· your project management scenario
· your project management strategy and plan
· your selected toolset
Your deliverables must effectively describe the chosen project management scenario, select and justify a suitable Project Management Life Cycle (PMLC), construct an exemplary project plan and provide evidence of how your toolset will be applied within your project management strategy.
You will be required to submit only one MS Word document split into three chapters i.e. ‘Project scenario’, ‘Project management strategy and plan’ and ‘Selected toolset’. It is expected that identified management tools e.g. MS Project Critical Path Model, burn down charts, RACI schema as appropriate etc. will be pasted within this MS Word document.
PROJECT MANAGEMENT SCENARIO (20%)
|
Marks |
Characteristics |
|||
|
70 + |
90+ [professional | outstanding] A structured and detailed narrative of a plausible computing project scenario supported with quantitative and qualitative detail (possibly a live case study) 80+ [extensive | excellent] An excellent and structured description of a plausible project scenario supported with good contextual detail, both qualitative and quantitative 70+ [substantive] A structured and considered description of a plausible computing project scenario supported with feature specific details |
|||
|
60 – 69 |
[exemplary] A reasonable description of a plausible computing project scenario augmented with some exemplar details |
|||
|
50 – 59 |
[acceptable] A broad description of a plausible computing project scenario |
|||
|
40 – 49 |
[insufficient] Essentially a suitable title for a paper suggesting a plausible computing project scenario but requires much more extensive contextual details |
|||
|
< 40 |
Inadequate for this level of study |
PROJECT MANAGEMENT STRATEGY & PLAN (50%)
|
90 + [professional | outstanding] An exhaustive and detailed review of alternative approaches using a prescriptive evaluation schema to construct a well-defended, well-argued choice of PMLC supported with extensive referencing and research. (20 +). Exhaustive set of well-populated and integrated PM Plan components and documentation which exemplify the selected toolset. 80 – 89 [excellent | extensive] A range of approaches are critically reviewed to construct a defensible project management strategy and PMLC supported with good referencing and research (10+). Extensive set of suitably populated PM Plan components and documentation making use of appropriate tools 70 – 79 [substantive] A considered project management strategy model and PMLC is presented with some supporting research and argument. A substantive compilation of PM documentation is presented that could benefit from more careful integration and possibly a more expansive set of PM components. |
|
[exemplary]
A suitable overview of the overall project management strategy supported with a suitably discussed PMLC. A suitable, illustrative set of important PM Plan components and documentation |
|
[satisfactory] Demonstrates some knowledge of PMLCs and suggests an overall approach, but would benefit from much more considered analysis and evaluation of the scenario to justify choice of Strategy and PMLC to compile a defensible business case. Some of the primary PM Plan components are presented but it would benefit from consideration of a greater range of components and use of tools to populate the content. |
|
[insufficient]
Consideration of the overall strategy is very limited without adequate justification for choice of PMLC or overall strategy. Too few primary PM Plan components submitted or suitably populated to provide a feasible overall PM Strategy and Plan |
|
Wholly inadequate for this level of study |
TOOLSET SELECTION & APPLICATION (30%)
|
Mark |
|
| 90 + |
90+ [professional | outstanding]
A wide range of toolset has been critically applied to assist formulation of the PM Strategy and PM Plan components. The toolset makes extensive use of scenario data. 80+ [extensive | excellent] An excellent selection of tools is used to support the choice of PM Strategy and assist in developing the PM Plan components. 70+[substantive] A range of suitable tools is used to assist development of content for the PM Plan components making use of some scenario details and data. |
|
[exemplary]
Some suitable suggestions for a toolset portfolio are made, demonstrating knowledge of important project management tools and their application, but the portfolio would benefit from more careful integration with the suggested project management scenario. |
|
|
[satisfactory]
Makes a few suitable suggestions for a toolset portfolio, demonstrating a reasonable level of knowledge, but the submission would benefit from more considered research, application and integration with the PM Plan components and given scenario. |
|
|
[insufficient]
A few tools are considered in a somewhat incoherent fashion. The toolset portfolio would benefit from much more considered choice and application. |
Pete Dwyer 09/10/2018
Page 1
Pete Dwyer 09/10/2018 Page 1
Page 1