Aim The purpose of this coursework assignment is to allow you to demonstrate your understanding of the practical application of the knowledge, concepts and principles of IT project management.
Learning Outcome 1. Developing a project plan by using any open source software for project management APP.
Learning Outcome 2. Conducting the Risk Analysis.
Learning Outcome 3. Discuss the Quality and Validation issues which are relevant to the selected project.
Learning Outcome 4. Constructing Work Breakdown structure.
Appendix (Page No:5) sets out a requirements scenario that you can use to do your project or you can create your project along similar lines but in this case you need to submit your project requirements scenario to the Module Leader/ Tutor by email by 06-05-2021.
You will construct a detailed project plan which includes the following sections: project introduction, project organisation, risk analysis, quality assurance, work breakdown, resources, scheduling analysis. Y ou will provide a brief description of legal issues in relation to the project. Each student should submit his/her coursework on CCELearn. You are required to confirm your project with module tutor before you start work on the assignment. (Word limit: (4000 +-10%) )
Contents of the Project Plan
The coursework project plan should have an appropriate front cover sheet that includes the group members' names, the title of the project, the project stream. There should also be a table of contents and the pages of the report (including appendices) should be clearly numbered. The plan itself should include the following sections, which should be clearly numbered and labelled. The sections should be written in a clear narrative style with supporting diagrams, where appropriate (some of which may be incorporated as appropriate appendices).
This should include an explanation to the background of the project and a summary of the initial scope of the project. This scope should include a clear outline of the aims and objectives of the project, identification of stakeholders including details of the intended target audience, details of the main envisaged functionality of the project, any specific non-functional requirements, the expected implementation environment, project timeline, budget and limitation. You should create a stakeholder register in this section.
This should include a discussion and presentation of the proposed systems life cycle you intend to use in carrying out the project. This discussion should provide a clear analysis of the specific characteristics of the project in relation to the intended systems lifecycle and should provide a clear justification for your choice of systems life cycle. This section should also include basic details of the organisation of your project team and the allocation (with some basic description) of the specific project roles, the organisational structure type and the reporting dependencies which this organisation will use. You should create an organisation diagram and software development diagram in this section.
This section should be a detailed discussion and analysis of the risk areas you feel are applicable to your project. You should create a risk register and the analysis should cover all of the main areas of risk, i.e. Project Risks, Product/Technical Risks and Business Risks. Each risk area should be discussed and assessed in turn, the main risks need to be identified and your risk management strategies are presented. If you feel that any particular risk area is not applicable or not significant to your project, then you should present a justification of that in your risk analysis discussion. (p.s. should identify at least 5 main risks)
This section should discuss the Quality and Validation issues which are relevant to your project. For example, the quality plan should discuss the main quality factors that are most appropriate to your development and detail the quality procedures and standards you intend to use within the project's development. You should outline the testing strategy you intend to use for testing and validation (of both functional and non-functional requirement aspects) in your project.
Professional (legal) issues
An Assessment of the Legal Issues applicable to your project topic: Include an assessment of your project in relation to relevant professional (legal) issues (citing relevant Oman Royal Decrees and international statutes is critical and required). For example, you should consider each aspect of the software law covered in this module and analyse its applicability to the project as a released product
e.g. Intellectual Property Law, Internet Law, Law of Privacy, Copyright Law, WIPO Convention of the United Nations, etc).
Projects Falling into Development Traps
Examine why most international development projects fall into development traps and ultimately run the risk of failure in Asia or Middle East. Your discussions should suggest how you would deal with methodology, accountability, capability and culture challenges on your projects.
Resource Requirements, Work Breakdown and Project Schedule
Hardware and Software Resource Requirements:
• This should detail the hardware and software requirements for both project development and project operation, once the project is ‘released' for use. It should also give details of the necessary hardware/software skills required by the project team. This section should also detail the staff development plans in terms of acquiring any specific skills identified here.
• You should also include
- An estimated cost breakdown of the hardware and software requirements and staff resources.
- An estimated overall project budget for your project.
This should describe the breakdown of the project into detailed and hierarchical sets of activities (i.e. Work Package Specifications), including milestones/deliverables for each. In the main body of the document you should include the Work Breakdown Structure Chart and for each identified activity the main body of the document should give a description of the activity and the names of the deliverables/milestones. The detailed set of Work Package Specifications should be placed in an appendix in the document.
Using Microsoft Project Professional 2016 or another project management tool such as Computer Aided Project Management (CAPM)/JIRA/Wrike etc., produce a Gantt chart/burndown chart for your project showing the planned schedule of activities on your project. This should describe the dependencies between the activities, the estimated time (and timing) required and the allocation of resources (including people) to the activities. Work breakdown structure codes (WBS) should be shown if you use a Gantt chart to manage your project. Screenshots of the Gantt chart should be provided in your group report.
Precision and consistent style are vital for good descriptions and documentation. The marks you will receive for the other sections too will be affected by the extent to which they can be clearly understood. For this coursework please adhere to the following rules:
• All text - Black only (do not use any other colour); Arial or Times Roman; Text size 11 point; Line spacing - Single.
• Left and right justification
• Headings: L1 - 13 point, bold; L2 - 12 point, bold; L3 - 11 point, bold.
• Place Level 1 Headings on a new page
• Diagram labels: "Figure X: Nice Picture" (below diagram), "Table Y: Nice Table" (above diagram), numbered, titled, centred, bold
• Cross-reference and explain the detail of all diagrams e.g. Figure A shows .., Table Y shows...
• Use a Spelling and Grammar Checker with English (UK) as default setting
• Table of Contents
• Page numbers (bottom right).