联系方式

  • QQ:99515681
  • 邮箱:99515681@qq.com
  • 工作时间:8:00-23:00
  • 微信:codinghelp

您当前位置:首页 >> C++C++

日期:2020-10-09 10:20

School of Science

ISYS 1108

Software Engineering Project Management

Team-Based Assignment: Part 2

Assessment 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-based

Assignment, Part 2. 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, 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 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.

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. Overview

In 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 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. To start Sprint 1 properly, you need to have a complete Product

Backlog (you can refine it over the Sprints 1-3). 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 7+8, Sprint 2: Weeks 9+10, Sprint 3: Weeks 11+12

Page 2 of 5

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 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.

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

Note: 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 5

Important:

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 external

resources (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 Sprint

1 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 testing

In 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). Your

backlogs will be marked based on these screenshots only, so failure to provide all required data might lead to losing marks for the

corresponding rubrics.

5. Referencing guidelines

What: This is a group assignment and all submitted contents must be your own. If you have used sources of information other than

the contents directly under Canvas → Modules, you must give acknowledge the sources and give references using IEEE referencing

style.

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 detailed

reference before any relevant code (within code comments).

6. Submission format

It is the responsibility of each student in the team ton check the files are submitted correctly. Please verify that your submission is

correctly 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 5

7. Academic integrity and plagiarism (standard warning)

Academic integrity is about honest presentation of your academic work. It means acknowledging the work of others while

developing 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 material

taken 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 work

and 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 inappropriate

behaviours, including:

? Failure to properly document a source

? Copyright material from the internet or databases

? Collusion between students

For further information on our policies and procedures, please refer to the University website.

8. Assessment declaration

When you submit work electronically, you agree to the assessment declaration.

Page 5 of 5

9. Rubric/assessment criteria for marking

Excellent Good Needs improvement Inadequate

Product (max. 6 points)

3 shippable product increments that

should be done according to the DoD

(evidence of performed testing should

be provided)

6 points

Three potentially shippable product

increments have been successfully

demonstrated. Each increment is done wrt.

DoD, corresponding testing results

demonstrated.

4 points

Something was amiss, read marker's notes.

Overall you did a good job, reasonable testing

results demonstrated. You could have missed

out on - one of potentially shippable product

increment.

2 points

Lots of improvement needed. Please

read marker's notes.

0 points

You did not cover any of the requisite

points. You have not demonstrated any

of the shippable product(s)

Demos (max. 9 points)

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.

9 points

Three potentially shippable product

increments have been successfully

demonstrated by video-demos (4-5 minutes

each), the flow of increments is clear, the

scenarios are well selected.

6 points

Good in most regards. Missing few points,

please check marker's remarks.

3 points

Lots of improvement needed. Please

read marker's notes.

0 points

You have missed the point. There are

either too many mistakes (in which case

please read marker's comments) OR

this 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 layout

5 points

Excellent in all regards. The document is

complete, contextual and cohesive. It makes

sense and reflects the work demonstrated

by the team in demo-videos.

3.5 points

Good in most regards. Missing few points,

please check marker's remarks.

2 points

There are a lot of issues here starting

with the misplaced content, obvious lack

of completeness with respect to the

scenario. Some of what you have written

seems out of context and place.

0 points

You have missed the point. There are

either too many mistakes (in which case

please read marker's comments) OR

this has not been submitted

Sprint Backlogs

(max. 6 points)

3 sprint backlogs. It will be checked for -

its completeness - logic and context

(does it make sense?) and, - professional

layout

6 points

Excellent in all regards. The document is

complete, contextual and cohesive. It makes

sense and reflects the work demonstrated

by the team in demo-videos.

4 points

Good in most regards. Missing few points,

please check marker's remarks. Always check

the final submission for layout, spell check and

redundant/missing information.

2 points

There are a lot of issues here starting

with the misplaced content, obvious lack

of completeness in terms of content.

Some of what you have written seems

out of context and place.

0 points

You have missed the point. There are

either too many mistakes (in which case

please read marker's comments) OR

this has not been submitted

Quality Assurance (max. 8 points)

Video on how the team selected their

DoD and performed testing according to

it, with examples

8 points

Excellent in all regards. The video (7-10

minutes) demonstrate reasonable

justification of the selected DoD as well as

how exactly each of the performed testing

types was conducted.

5 points

Good in most regards. Missing few points,

please check marker's remarks.

3 points

Missing justification for selected DoD, or

the video does not cover all testing

types, or the video is much longer /

shorter then requested.

0 points

You have missed the point. There are

either too many mistakes (in which case

please read marker's comments) OR

this has not been submitted.

Sprint planning and retrospective

(max. 6 points)

Notes for each sprint. It will be checked

for - its completeness - logic and context

(does it make sense?) and, - professional

layout

6 points

Excellent in all regards. The documents are

complete, contextual and cohesive. It makes

sense and reflects the work demonstrated

by the team in demo-videos.

4 points

Good in most regards. Missing few points,

please check marker's remarks. Always check

the final submission for layout, spell check and

redundant/missing information.

2 points

There are a lot of issues here starting

with the misplaced content, obvious lack

of completeness in terms of content, or

some notes are missing. Some of what

you have written seems out of context

and place.

0 points

You have missed the point. There are

either too many mistakes (in which case

please read marker's comments) OR

this has not been submitted


版权所有:留学生程序网 2020 All Rights Reserved 联系方式:QQ:99515681 电子信箱:99515681@qq.com
免责声明:本站部分内容从网络整理而来,只供参考!如有版权问题可联系本站删除。