Page 1 of 7 School of Science ISYS 1106 Software Engineering Project Management Team-Based Assignment
Assessment Type: In a group of 5-6 (no individual submissions will be accepted). Assignment: Submit online via Canvas → Assignments → Team-based Assignment → Team-based Assignment. Clarifications/updates may be made via announcements/relevant discussion forums. Contributions Form: Submit online via Canvas → Assignments → Team-based Assignment → Contributions Form. Each student 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, 24 May 2020 (Sunday of Week 11). Unless special consideration has been granted, the late penalty is 10% of the total mark for the assessment per business day late for up to 5 business days late (so the maximum late penalty is 50%). Submissions more than 5 days late are not accepted. Presentation: During Week 12, i.e., 25 – 29 May 2020. No presentation = no marks. Due date for the Contributions Form submission: 23:59, 31 May 2019 (Sunday of Week 12).
Weighting: 25 points (worth 25% of the total score)
1. Overview For this assignment, assume that you are a Scrum team working on a software development project. The scenario was inspired by a real industrial project contacted previously in collaboration between RMIT and an industrial partner. The scenario presented below covers a large system. Not all of its features are required to be implemented within the assignment, but they all have to be covered in Project Charter and Product Backlog as that will determine the timeline of the project, if it were to happen in real life. You will be writing code to create the software along with the important project management documents. Some specific details on the software/product are not known at the start, these will emerge during the project. This is very close to real life projects. You must register your group using the Microsoft Excel (Guidelines will be provided in Canvas → Announcements). The deadline for registration is Sunday 22 March, 17:00 (Sunday of Week 3). No registration == No submission. Page 2 of 7 Scenario: Consider a start-up focusing on production of diaries with customizable design. They would like to have an application to support online sales of the client’s products, where the admit interface is provided as a web-application, and the client interface is provided as iOS and Android apps. However, they also happy to consider an option where both interfaces are provided as web-application, but in this case the web application for Customer must be responsive. The start-up would like that any customer can • see all the currently available parameters of customization, when they create a diary: paper color, theme/color of the cover, type of paper (plain, lined, or dotted), customizable text on the cover; • make a purchase using PayPal and credit cards; • select delivery options (standard and express, only Australia-wide); • see the history of their purchases; and • provide feedback that will be visible to other customers. The start-up also would like that their admins can • edit all parameters of customization as well as their current availability, • create accounts for new admins as well as deactivate admin and customer users, • see the information on all clients and their purchases (including delivery options), • generate reports on the overall purchases – on weekly and monthly basis, • moderate the feedback if necessary. When you are working on the 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 Assignment folder, or • come to the Assignment feedback sessions – these will be held during week(s) 7 – 11. Please prepare your questions for the session properly, as this is planned not as pre-check of your work before you submit, 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. This is where your team will get together and decide which features are to be completed in the sprint. The subsequent sprint planning meetings will also need to focus on carry over from the previous sprints. • At the end of each sprint you are to produce potentially shippable product and corresponding Scrum artefacts. • Sprint 1: Weeks 6+7, Sprint 2: Weeks 8+9, Sprint 3: Weeks 10+11 3) Each of the sprint you will require to have: • Sprint planning notes • Sprint backlog • Sprint retro notes • Potentially shippable product as well as update your burn-down chart. The first three items are easy to produce as they will pdf documents (based on Word and Excel templates) however the proof of potentially shippable product is a bit tricky: Whatever you produce at the end of the sprint, keep those files separate in a directory and when you start the new sprint, make a copy of those files and work on the new set of copied files, i.e., DO NOT overwrite the set of files from the earlier sprint. If you do, there will be no proof of what you produced at the end of the sprint. We also encourage you to use github for version control. Page 3 of 7 2. Assessment Criteria This 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 different approaches. 3. Ability to provide references where due. 4. Meeting deadlines. 5. Seeking clarification from your “supervisor” (tutor) when needed via discussion forums. 3. Learning Outcomes This 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 team projects • 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 and Methodologies; Software Development Life Cycles – From Waterfall to Agile; Software Engineering Fundamentals; Software Requirements Engineering as basis for Project Management; Hybrid methodologies; Planning and Scheduling; Risk and Issues Management; Quality Assurance; Change Management; Release Management; Service Delivery and Support; The Team Dynamic; Collaboration and Communication skills; Organisations, People and Culture • CLO 5: Apply critical analysis, problem solving, and team facilitation skills to software engineering project management processes using real-world scenarios. 4. Assessment details