” ISYS 1108编程 写作、 辅导Java，C++，Python编程School of ScienceISYS 1108Software Engineering Project ManagementTeam-Based Assignment: Part 2Assessment Type: In a group of 5-6 (no individual submissions will be accepted).Assignment artefacts, except Sprint planning and retro notes: Submit online via Canvas Assignments Team-basedAssignment, Part 2. Clarifications/updates may be made via announcements/relevant discussion forums.Contributions Form: Submit online via Canvas Assignments Team-based Assignment Contributions Form. Eachstudent will receive a Final mark based on a final mark for the project and their individual contribution.Due date for the Assignment submission: 23:59, 18th October 2020 (Sunday of Week 12).Unless special consideration has been granted, the late penalty is 10% of the total mark for the assessment per businessday late for up to 5 Business days late (so the maximum late penalty is 50%). Submissions more than 5 days late are notaccepted.Due date for the Contributions Form submission: 23:59, 18th October 2019 (Sunday of Week 12).Weighting: 40 points (worth 30% of the total score, i.e., 1 point = 1% of the total score)1. OverviewIn this assignment, you continue Working in the same team and on the same scenario as you did in Team-based Assignment, Part 1.When you start working on the team-Based assignment:1) If you have questions on the assignment tasks and/or the corresponding course material, you might bring these questions to weekly feedback sessions held by lecturer, or post them in the discussion board Written Group Assignment folder, or come to the Assignment feedback sessions.Please prepare your questions for the session properly, as this is planned not as pre-check of your work before yousubmit, but as opportunity to answer your questions on the material and to clarify your doubts.2) Your team must perform 3 Sprints to complete the software development. Here is what needs to be done: Each sprint must start With a sprint planning meeting. To start Sprint 1 properly, you need to have a complete ProductBacklog (you can refine it over the Sprints 1-3). This is where your team will get together and decide which features areto be completed in the sprint. The subsequent sprint planning meetings will also need to focus on carry over from theprevious sprints. At the end of each sprint you are to produce potentially shippable product and corresponding Scrum artefacts. Sprint 1: Weeks 7+8, Sprint 2: Weeks 9+10, Sprint 3: Weeks 11+12Page 2 of 5ISYS 1108作业 写作、 辅导Java，C++，Python编程3) Each of the sprint you will require to have: Sprint planning notes Sprint backlog Sprint retro notes Potentially shippable product (including all the test cases)as well as update your burn-down chart and product backlog.The first three items are easy to Produce as they will pdf documents (based on Word and Excel templates) however theproof of potentially shippable product is a bit tricky: Whatever you produce at the end of the sprint, keep those filesseparate in a directory and when you start the new sprint, make a copy of those files and work on the new set of copiedfiles, i.e., DO NOT overwrite the set of files from the earlier sprint. If you do, there will be no proof of what you producedat the end of the sprint.We also encourage you to use github for version control.2. Assessment CriteriaThis assessment will determine your ability to:1. Follow Scrum methodology to manage a software development project, also using project management tools.2. Create corresponding Scrum artefacts and write relevant documentation by recalling concepts taught in class,understanding and applying concepts relevant to solution, analysing components of the problem, evaluating differentapproaches.3. Ability to provide references where due.4. Meeting deadlines.5. Seeking clarification from your supervisor (tutor) when needed via discussion forums.3. Learning OutcomesThis assessment is relevant to the following Course Learning Outcomes (CLOs): CLO 1: Illustrate a working knowledge of how to plan, execute and close projects to required standards CLO 2: Use a range of Proprietary and non-proprietary project management tools to carry out and report on your teamprojects CLO 3: Use project management frameworks that ensure successful outcomes CLO 4: Analyse and apply critical project management concepts, such as: Why Projects Fail; Project Governance andMethodologies; Software Development Life Cycles From Waterfall to Agile; Software Engineering Fundamentals; SoftwareRequirements Engineering as basis for Project Management; Hybrid methodologies; Planning and Scheduling; Risk andIssues Management; Quality Assurance; Change Management; Release Management; Service Delivery and Support; TheTeam Dynamic; Collaboration and Communication skills; Organisations, People and Culture CLO 5: Apply critical analysis, problem solving, and team facilitation skills to software engineering project managementprocesses using real-world Scenarios.4. Assessment detailsNote: Please ensure that you have read sections 1-3 of this document before going further.Marking Guide: Please check the marking rubrics on the last page.Page 3 of 5Important:1) Each of the documents Will also be marked for its professional presentation and writing standards.2) Only artefacts submitted in Canvas within the ZIP file will be considered for marking. Any artefacts uploaded to externalresources (e.g., Google Drive) or links to ClickUp, github, etc. cannot be considered for marking.Your group must submit ONE zipped file. The Following directory structure must be used to create file system for submission: Product Backlog (use the provided template, submit in PDF format) Sprint Backlogs for Sprints 1, 2, and 3 (use the provided template, submit in PDF format) Burn-down chart (use the provided template, submit in PDF format) 3 demo-videos, presenting the shippable product increments of each sprint and the corresponding flow over the three sprints,as well as challenges faced by group and how were they solved Video on how the team selected their DoD and performed testing according to it, with examples One PDF file, where the following documents are collected together (use the provided template, create PDFs of each Word file,and then glue them together): Sprint Planning Notes for Sprint 1, Sprint Retro Notes for Sprint 1, Sprint Planning Notes for Sprint 2, Sprint Retro Notes for Sprint 2, Sprint Planning Notes for Sprint 3, and Sprint Retro Notes for Sprint 3. Sprint 1 Product (a directory containing all code of the potentially shippable product at the end of the sprint) Test cases and results of testing:o in the case of manual testing a spread sheet containing all test cases to test the Product developed within Sprint1 and the corresponding test Results (use the provided template, submit in PDF format);o in the case of automated testing corresponding code and videos of its execution. Sprint 2 Product Test cases and results of testing Sprint 3 Product Test cases and results of testingIn the case you prefer to use ClickUp for this project, you have to create a directory containing ClickUp screeshots of your board,which cover all elements that present product and sprint backlogs (instead of submitting the corresponding templates). Yourbacklogs will be marked based on these screenshots only, so failure to provide all required data might lead to losing marks for thecorresponding rubrics.5. Referencing guidelinesWhat: This is a group Assignment and all submitted contents must be your own. If you have used sources of information other thanthe contents directly under Canvas Modules, you must give acknowledge the sources and give references using IEEE referencingstyle.Where: Add a code comment near the work to be referenced and include the reference in the IEEE style.How: To generate a valid IEEE style reference, please use the citethisforme tool if unfamiliar with this style. Add the detailedreference before any relevant code (within code comments).6. Submission formatIt is the responsibility of each student in the team ton check the files are submitted correctly. Please verify that your submission iscorrectly submitted by downloading what you have submitted to see if the files include the correct contents.Submit one .zip file online via Canvas Assignments Team-based Assignment, Part 2 Team-based Assignment 2.Page 4 of 57. Academic integrity and plagiarism (standard warning)Academic integrity is about honest presentation of your academic work. It means acknowledging the work of others whiledeveloping your own insights, knowledge and ideas. You should take extreme care that you have: Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e. directly copied),summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods, Provided a reference list of the publication details so your reader can locate the source if necessary. This includes materialtaken from Internet sites.If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the workand ideas of another Person without appropriate referencing, as if they were your own.RMIT University treats plagiarism as a very serious offence constituting misconduct. Plagiarism covers a variety of inappropriatebehaviours, including: Failure to properly document a source Copyright material from the internet or databases Collusion between studentsFor further information on our policies and procedures, please refer to the University website.8. Assessment declarationWhen you submit work electronically, you agree to the assessment declaration.Page 5 of 59. Rubric/assessment criteria for markingExcellent Good Needs improvement InadequateProduct (max. 6 points)3 shippable product increments thatshould be done According to the DoD(evidence of performed testing shouldbe provided)6 pointsThree potentially shippable productincrements have been successfullydemonstrated. Each increment is done wrt.DoD, corresponding testing resultsdemonstrated.4 pointsSomething was amiss, read markers notes.Overall you did a good job, reasonable testingresults demonstrated. You could have missedout on – one of Potentially shippable productincrement.2 pointsLots of improvement needed. Pleaseread markers notes.0 pointsYou did not cover any of the requisitepoints. You have not demonstrated anyof the shippable product(s)Demos (max. 9 points)3 demo-videos, presenting the shippableproduct increments of each sprint andthe corresponding flow over the threesprints, as well as challenges faced bygroup and how were they solved.9 pointsThree potentially shippable productincrements have been successfullydemonstrated by video-demos (4-5 minuteseach), the flow of increments is clear, thescenarios are well selected.6 pointsGood in Most regards. Missing few points,please check markers remarks.3 pointsLots of improvement needed. Pleaseread markers notes.0 pointsYou have missed the point. There areeither too many mistakes (in which caseplease read markers comments) ORthis has not been submitted.Product Backlog(max. 5 points)It will be checked for – its completeness -logic and context (does it make sense?)and, – professional layout5 pointsExcellent in All regards. The document iscomplete, contextual and cohesive. It makessense and reflects the work demonstratedby the team in demo-videos.3.5 pointsGood in most regards. Missing few points,please check markers remarks.2 pointsThere are a lot of issues here startingwith the misplaced content, obvious lackof completeness with respect to thescenario. Some of what you have writtenseems out of context and place.0 pointsYou have missed The point. There areeither too many mistakes (in which caseplease read markers comments) ORthis has not been submittedSprint Backlogs(max. 6 points)3 sprint backlogs. It will be checked for -its completeness – logic and context(does it make sense?) and, – professionallayout6 pointsExcellent in all regards. The document iscomplete, contextual and cohesive. It makessense and reflects the work demonstratedby the team in demo-videos.4 pointsGood in most regards. Missing few points,please check markers remarks. Always checkthe final submission for layout, spell check andredundant/missing information.2 pointsThere are a lot of issues here startingwith the misplaced content, obvious lackof Completeness in terms of content.Some of what you have written seemsout of context and place.0 pointsYou have missed the point. There areeither too many mistakes (in which caseplease read markers comments) ORthis has not been submittedQuality Assurance (max. 8 points)Video on how the team selected theirDoD and performed testing according toit, with examples8 pointsExcellent in all regards. The video (7-10minutes) demonstrate reasonablejustification of the selected DoD as well ashow exactly each of the performed testingtypes was conducted.5 pointsGood in Most regards. Missing few points,please check markers remarks.3 pointsMissing justification for selected DoD, orthe video does not cover all testingtypes, or the video is much longer /shorter then requested.0 pointsYou have missed the point. There areeither too many mistakes (in which caseplease read markers comments) ORthis has not been submitted.Sprint planning and retrospective(max. 6 points)Notes for each sprint. It will be checkedfor – its completeness – logic and context(does it make sense?) and, – professionallayout6 pointsExcellent in all regards. The documents arecomplete, Contextual and cohesive. It makessense and reflects the work demonstratedby the team in demo-videos.4 pointsGood in most regards. Missing few points,please check markers remarks. Always checkthe final submission for layout, spell check andredundant/missing information.2 pointsThere are a lot of issues here startingwith the misplaced content, obvious lackof completeness in terms of content, orsome notes are missing. Some of whatyou have written seems out of contextand place.0 pointsYou have Missed the point. There areeither too many mistakes (in which caseplease read markers comments) ORthis has not been submitted如有需要，请加QQ：99515681 或邮箱：99515681@qq.com
“
添加老师微信回复‘’官网 辅导‘’获取专业老师帮助，或点击联系老师1对1在线指导。
