Assessment 2 IFN711 Industry Project Plan
Assessment 2: IFN711-Industry Project Plan
Industry Project Plan: Week 5 (Sunday, the 29th
of March 2020 by 11:59pm)
Select and apply the appropriate project
management approach to design and deliver a sophisticated IT system within a team
environmentDemonstrate project management skills including
Estimation, planning, execution, monitoring & closing for a group IS/IT projectDemonstrate professional skills and ethical
Detailed Project Plan report (approximately 3000 words)
Submit to Blackboard as instructed
The Project Plan (PP) is a critical Project Management (PM) deliverable that will help you and your team’s project’s success. You and your team must work towards a high-quality PP. The PP is an assessable item and you will receive feedback. Please refer to the attached Marking Guide (see Appendix A) and ensure that the submitted plan covers all assessed criteria elements.
Your team will need to deliver IT artefacts that will address a specific company’s requirements or an industry wide problem. The main outcome of the project is the development of an artefact, which must be communicated explicitly in your plan. In the industry-oriented projects, students are expected to plan and execute a set of activities to deliver an IT artefact. This is normally in the form of;
- creating a new application or service or
- modifying an existing app or service (e.g. an application, or a framework, or a tool, etc.) or
- experiment and discuss the results of emerging technology for addressing a business need.
Your project assessment outcomes will need to be informed by the knowledge gained in your MIT units (using either research literature, industry-based case studies, white papers or advanced units’ knowledge) so that your team can justify your choices. This will be a key consideration in the assessment to substantiate your design, development and implementation choices and validate your project outcomes.
Requirements for the Project Plan submission
While each project will be unique, your Project Plan should include the following elements as a minimum. You should discuss other items for inclusion with the project’s supervisor (tutor). In section 3 your team will need to choose an appropriate Project Management (PM) approach for your industry project. You will justify your choice in this document. Once you have chosen a PM approach you must use the appropriate techniques related to that PM approach. In section 5 we have specified a WBS and Gantt chart technique in addition to the appropriate technique for your PM approach. The WBS is a well-established technique to track activity-based contributions assigned to each member of the team. These techniques will provide you with the data for subsequent assessments namely Individual journals and peer assessment components of the final report.
Please include the heading ‘ Project Plan’, project title, all group member details, project number, and project supervisor (tutor) name, and a brief description of what will be the final IT artefact your team’s project will deliver in week 13. The final artefact will vary based on your major and the specific needs of an industry project.
Some of the potential artefacts are design artefacts, development artefacts, technology testing results, algorithms, new technologies experiments, enterprise architecture proposals, enterprise systems developments/enhancements, network/security protocols enhancements, process standardisation/improvements/transformations and any other type of IT artefacts that are relevant to your major.
Should be concise and descriptive. Be precise enough to suggest the nature and scope of the project and concise enough to be referred to quickly and easily. Your team can consider the reuse of the title given by industry partner in the project information brief given in week 3 tutorials.
In this section, the Project Plan (PP) will need to describe,
- A brief of the industry/company associated with your team’s project
- Aim of the project: What is the business problem, need, improvement, or opportunity that your project’s artefact will address when implemented.
- Objectives: The list of specific measurable assignable real and time (SMART) outcomes (i.e. IS/IT artefacts) that your project will deliver in 13 weeks.
- Potential impact (i.e. significance) to the business: This will outline the anticipated business benefits (competitive advantage, or growth potential or operational efficiencies or innovation) to be realized by the industry/business partner organization.
Some additional advice on writing specific contents for this section:
- The main purpose of the introduction is to provide the necessary background or context of your project.
- The introduction should be written in language that explains clearly and succinctly the problem to be investigated or a new opportunity that your team intends to explore and experiment with.
- Minimize highly technical language at the intro level, since that may or may not align with the real needs of the projects.
- Focus on the purpose of the project, its importance and the rationale for undertaking it.
- Be succinct and concise – you will have the opportunity to expand on these later in the document.
- When describing the significance of the project, it needs to demonstrate the knowledge gained from reading the relevant literature or advanced units’ knowledge. It should also indicate how it can solve a problem or create value with a digital solution.
2 Describe your project Scope
The scope will include the Functional, Non-Functional requirements and Deliverables (Artefacts).
In this section, you will need to show What is the scope of your project in terms of
- Identify and define what is in scope, out of scope, and what’s not yet clear and can be considered as scope risks.
- Based on your selected Project Management approach use the appropriate techniques.
- Provide complexity and effort Estimations for the list of requirements
Your team will also need to list the set of intermediary outcomes that will need to be delivered to meet the final artefact delivery in week 13.
3 Select and apply your chosen Project Management approach
- You should choose and use one of the Agile project management approach (DSDM or SCRUM or any other Agile framework that you are familiar with). Alternately, you are welcome to use the traditional waterfall PM approach.
- Based on the PM approach adopted, you must justify as to why this approach is the best fit for your given industry project.
- Your need to explain how you have adapted and customised the chosen PM approach to successfully deliver your project management deliverables and project artefacts.
- All project management deliverables should be specific and aligned with your Industry project.
4 Explain your team’s solution
In this section, you will need a minimum of two diagrams as well as a detailed explanation of why you have adopted this solution to address the business need. This solution will vary depending upon your major as well as the specific scope for your project. Your team will need to demonstrate the knowledge gained from your advanced units of the major as well as any current successful case studies from the industry. You will choose an industry project appropriate high-level diagrams to model how your solution will address the business need and its stakeholders.
You will identify potential technology solutions. A clear justification for technology choices which is evidenced by the critical analysis and sound problem-solving skills by your team. You will propose one of the technologies with justification.
5 Create a schedule of intermediate and final deliverables
In this section, you will develop a schedule using an appropriate technique for your PM approach. In addition to this, you will create a Work breakdown structure (WBS) and Gantt chart. This schedule will be used as the baseline to measure project progress.
In this section, you should provide a detailed timeline of deliverables for your project. Note that the project methodology and the overall project management aspects (from sections 3 and 4), should be well integrated across a detailed weekly delivery schedule.
Create a Work breakdown structure (WBS) and Gantt chart;
- Outline the activities and deliverables
across each week and plot these on the timeline.
- Your proposed tasks should cater to delivering all deliverables.
- Consider interrelationships (especially dependencies) between different components of the project.
- Allocate your team as resources within
- What is important to demonstrate here is that you have a plan of action to complete the work required for your project over the set period
- Please be reminded that your team will have 8 weeks left after you submit the project plan in week 5
(Note: The more detailed your schedule, the easier it will be for you to monitor and control your project. This section of the project plan will become your roadmap for tracking and monitoring your project progress in the remaining period. This section should also help the individual members of your team to explain their specific roles and contributions in their week 4 individual plan video as well as for the reflections in their individual journal assignments)
6 Manage your communications and risks
Clearly describe how you will maintain the essential communications across ALL the different stakeholders during the project. The communication plan should address who, what, where, when and how questions related to all stakeholder communications during the project progress and closure. A RACI table related to the life cycle activities of your chosen PM approach can be useful tool for the communication plan.
- You must include your planned meetings with academic supervisors.
- you must include your planned interactions with industry partners where applicable.
- Briefly outline the communication strategies put in place and make sure that supervisors have approved this
- Your communication plan should also integrate planned feedback rounds to support quality assurance in your project deliverables
(Consider using a tabular summary to present an overview of the communication plans proposed for the project)
You must identify potential project risks and determine mechanisms to avoid or manage these risks.
- Consider the risks that could accompany the project, their likelihood and impact, and the measures you will take to minimize these risks.
- Think broadly about the term ‘risk’. For example, a very real risk for many students is ‘timeline slippage’, where the timeline may not be adhered to. Consider the likelihood that risks such as this will occur and their potential impact, should they occur. Risks could be at the team level or the individual student level or the industry project level.
- In consultation with the project supervisor (tutor) identify the line of tolerance. For all risks above the line of tolerance, provide a mitigation strategy.
- Provide a risk analysis matrix including mitigation strategies.
(Consider using a tabular summary to present an overview of the communication plans proposed for the project)
7 Estimate your costs
Project Costs: Estimate your project budget and procurement of resources. Include an appropriately formatted financial spreadsheet to present the budget. Specify how much the project will cost and clarify cost elements like:
- Breakdown of cost estimates including the costs for people and other resources (example project expenses like hardware/software licenses, travel expenses, etc.;) – You are welcome to refer to Industry standards relevant to your type of projects. Where needed please use reasonable estimates.
- If you intend to include any contingency budget (based on the overall risks for your project), please clearly indicate how much and what for the contingencies will be used.
8 Elaborate your controls and team contracts
Explain the specific controls your team will implement for your team’s project to demonstrate how you will monitor and execute the project. Describe how as a team you will ensure your project is on track to deliver the final artefact promised in the plan. Based on your selected Project Management approach describe the techniques used to manage each of the following.
- The trade-off between the project variables scope, time, costs and/or features.
- Ensuring the quality of the artefacts during the execution of the project.
- Tracking and reporting of your project progress with your project supervisor (tutor).
All teams must include a team contract sheet for the Project Plan submission as an Appendix. The team contract includes both team level working agreements as well as an individual’s planned contributions to deliver the project artefact. All members of the team should sign this, and a soft copy of the team contract must be enclosed in your submission. Essay typer
all the works that you have cited in your project plan using APA 6th
reference style. It is recommended that a tool like ENDNOTE is used. See https://www.library.qut.edu.au/research/toolkit/referencing/
for further details. Please refer to QUT’s Citewrite http://www.citewrite.qut.edu.au/
as well for further details about Referencing.
Appendix A: Marking criteria for the Project Plan
IFN711 CRITERIA SHEET for PROJECT Plan (Assessment 2)
|Criterion||Marks||7 (~85%-100%)||6 (~75%-84%)||5 (~65%-74%)||4 (~50%-64%)||Fail (~0%-49%)|
|Introduction (1)||3||Background of the Industry/partner and the problem/ opportunity proposed to be addressed is described precisely with concise contentThe anticipated results and outcomes are clearly stated, illustrating how they will impact diverse stakeholders.||Background of the Industry/partner and the problem/ opportunity proposed to be addressed are described completely with elaborated analysis content The anticipated results and outcomes are stated, with some description of how they will impact diverse stakeholders.||Background of the Industry/partner and the problem/ opportunity proposed to be addressed are described correctly but with some related contentAnticipated results and outcomes are stated but lack clarity. Also, how the results/ outcomes will impact diverse stakeholders is not addressed.||Background of the Industry/partner and the problem/ opportunity proposed to be addressed are described as given by the partner with limited analysis The project aims and objectives and scope may not be appropriate or clearly stated.Very minimalistic description of the anticipated results and outcomes. How they will impact diverse stakeholders is not addressed at all.||Background of the Industry/partner and the problem/ opportunity proposed to be addressed are not described appropriately or at all. The anticipated results and outcomes are not stated at all.|
|Project Management Activities (3,6,7,8) & Team Contracts (Refer to Appendix B)||4||The most suitable PM approach is adopted comprehensively along with clear justification and alignment for the given scope and deliverablesAll key stakeholders for the project are identified and their involvement in the project is clearly definedA clear and effective communication plan is provided.Potential risks and/or ethical considerations are identified, and effective mitigation strategies are providedA team contract is included with a comprehensive operating guideline for the team Completed Industry partner engagement document and Individual member level skills & planned contributions list with Signatures||An appropriate PM approach is adopted clearly along with some justification and alignment for the given scope and deliverablesMost of the key stakeholders for the project are identified and their involvement in the project is clearly defined.A clear and appropriate communication plan is provided.Potential risks and ethical issues have been acknowledged and addressed. A team contract is included with all team members’ Skills Lists & Signatures Completed Industry partner engagement document and a team contract is included simple operating guidelines for team members level member’s Skills, planned contributions but no signatures||A PM approach is adopted clearly along with limited justification and alignment for the given scope and deliverablesSome key stakeholders of the project identified, but their involvement is not fully explored.A communication plan is provided but may be missing some items.Some but not all potential risks and ethical issues are acknowledged but may not be fully addressed.Completed Industry partner engagement document and a team contract is included with only some members’ Skills & contributions & Signatures and some operating guidelines for the team||A PM approach is adopted partially along with no justification and/or alignment for the given scope and deliverablesSome stakeholders are identified; reasons for inclusion may not be provided and/or maybe inappropriate.A communication plan is provided but may not be appropriate or may be incomplete.Limited identification or discussion of potential risks and ethical issues. Completed Industry partner engagement document and a team contract are included which includes only some members’ skills or contributions elements. Signatures are missing||No evidence for any PM approach adoption.No consideration of the stakeholders for the project.No communication plan is provided, or the plan is inappropriate. Risks and ethical issues are not considered or there are significant gaps. Completed Industry partner engagement document and a team contract is not included or missing all 3 elements (Skills, intended contributions & signatures) for some members|
|Scope, Deliverables, Solution, Delivery & Implementation Plan (2,4,5)||10||The project aims, objectives, scope and/or outcomes are clearly defined, well focused and fully aligned with the business needs.A brief overview of the project approach with sound justification is provided.The proposed digital solution is highly appropriate to the aims and objectives of the project, with clear alignment of the solution approach. The project plan is detailed and clearly presented, outlining all relevant milestones and evidencing an achievable program of work. Weekly/ fortnightly deliverables are very clearly articulated and presented using a Gantt chart or equivalent representation of work planned for the remaining weeks.||The project aims, objectives, scope and/or outcomes are clearly defined and appropriate.A brief overview of the project approach with some justification is provided.The project digital solution option or design is appropriate to the aims and objectives of the project and a basic justificationThe project plan is detailed and outlines all major milestones in an achievable program of work. Weekly/ fortnightly deliverables are clearly articulated and presented using a Gantt chart or equivalent representation of work planned for the remaining weeks||Appropriate aims, objectives, scope and/or outcomes are provided but may need further clarification. The solution approach is mentioned, but with little justification.The project solution is appropriate for the aims but not addressing all objectives or no justification given for the solution approachProject timelines and output are indicated but may require further explanation or may not be entirely appropriate. Weekly/ fortnightly deliverables are present but not very clearly articulated. An attempt to present the weekly tasks using a Gantt chart (or equivalent representation) – which is inaccurate or incomplete.||The project aims and objectives and scope may not be appropriate or clearly stated.The project deliverable artefacts are mentioned, but with no justification. The project solution lacks clarity and/or may not be the most appropriate for the project.Project timelines and output are provided but may not be clearly presented and/or may not be complete and/or may not be appropriate. Weekly/ fortnightly deliverables are only mentioned but not described at all, and there is no Gantt chart (or equivalent).||There are no aims or objectives, the scope for the project.The project deliverables are not mentioned at all The solution is not given addressed or is not appropriate for the project requirements.The delivery schedule is missing.|
Overall presentation and Team contract
|3||Language is skilfully constructed: unified, coherent, forceful, varied.The persuasive tone of writing styleThe paragraph structure effectively developed.No proof-reading errors.Exemplary professional appearance.||Language is fluent and coherent.The active tone of writing styleGrammar and spelling are accurate.A few proofreadings errorProfessional presentation.||Language mainly fluent, with some minor areas that may lead to confusion.The tone and style of writing are generally appropriate but maybe informal or conversational at times.Many Proof-reading errors and/or grammatical errorsNeat and tidy presentation.||Meaning apparent, but language not always fluent.Grammar and/or spelling contain errors.Inappropriate vocabulary, style or tone for professional writing.Unprofessional, untidy, or unattractive presentation.||Meaning unclear as grammar and/or spelling contains frequent errors.Disorganised or incoherent writing.|
Detailed Feedback Notes:
PROJECT MANAGEMENT METHOD APPLIED AND TEAM CONTRACT
PROJECT SCOPE, DELIVERABLES, SOLUTION & DELIVERY PLAN
OVERALL PRESENTATION OF THE DOCUMENTED PROJECT PLAN:
Appendix B: Team Contract Template
Team Level Social Contract: Please give 5 to 8 principles that your team will follow to ensure collaboration and successful outcomes from your project. (Please refer to Social Contract Development Activity from the tutorials)
Individual team Member’ Skills, Planned Contributions and Signatures
|Name of Team Member||Skills||Planned Contributions to the Project Activities||Signatures|