Get Instant Help From 5000+ Experts For
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing:Proofread your work by experts and improve grade at Lowest cost

And Improve Your Grades
myassignmenthelp.com
loader
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Guaranteed Higher Grade!
Free Quote
wave
Scrum/Agile Development Assessment Model and Teamwork

Industrial Practice-based Model

Firstly, the model is based on industrial practice; this means that when you enter the workplace you will have had some experience of Scrum/Agile development.

Secondly, working in teams you will have fellow students around you as a peer support network. Thirdly, you will have regular meetings with your tutor to claim marks. The regular meetings are an opportunity not only to show off your work but also to find errors/misconceptions, find solutions and obtain guidance on how to take your work to the next level.

To understand the assessment model there are some key concepts we need to cover.

  • Team Work
  • The Product Backlog
  • The Scrum Master
  • 5-minute sprint meetings
  • 10-minute sprint meetings
  • Scrum meetings
  • The Friday Blog Entry
  • eGrid and Logbook

Team Work

Team work is not group work! The typical model for group work involves a couple of group members who do all of the work, one student does nothing and then at the final assessment everybody is awarded the same grade. Clearly this is not fair!

The primary function of working in a team is to provide peer support (as is the case in the workplace). Within a team, skills are typically unevenly distributed. Some members may have skills in analysis and design; other may have skills in software development. Clearly you don’t need to be completing each other’s work but you are strongly encouraged to help each other when support is needed.

At the start of the module you will be organised into teams of four members. Your team will be given an ID this ID will identify your meeting schedule for the entire module (see Assessment Schedule on Page 4).

It is the role of the team to ensure that each team member is working on different topics for the assessment.

Team Engagement

To obtain the highest marks for team engagement you and your team must be seen to be actively engaging with the work for the module. This means, for full marks, you need to be attending classes, engaging with the work and showing evidence of work completed out of class.

Teams may be modified at any point during the module by your tutor.

Each week of the module you will be involved in a team meeting, there are two types of meeting, a Scrum meeting and a Sprint meeting. The meetings will alternate roughly every two weeks, again note the Assessment Schedule (page 4) for your meetings based on your team ID.

Meetings are subject to standard University regulations. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. If you have good reason to miss a meeting make sure you contact your tutor in good time and also provide appropriate evidence e.g. a Doctor’s note.

Team Work vs Group Work

The Product Backlog

The product backlog put simply is a to-do list of what work needs to be completed in order to complete the project. As a team it is wise to draw this up so that each member knows what needs to be done next. The backlog will need to be updated on a regular basis as you learn new things. The backlog is not submitted as a deliverable but your tutor may want to look at it over the year.

For each sprint you should take turns in taking on the role of Scrum Master. It is the responsibility of the Scrum Master to ensure that the process is followed correctly. The Scrum Master is not the boss! As Scrum Master you need to make sure that each team member is on the same page of the work. They need to make sure that team members are aware of significant deadlines and that the product backlog is being dealt with in an efficient, timely and fair manner. The Scrum master needsto be in their role for an entire sprint from initial Scrum meeting to the week ending of the 5-minute sprint meeting.

Sprint Meetings

A sprint is a time limited period of activity (typically 2 – 4 weeks) where items from the product backlog are completed.

At the end of each sprint your team will be involved in a sprint meeting with your tutor.

For a sprint meeting your whole team needs to be in attendance. Each team member will meet individually with your tutor to claim provisional marks for work completed so far. This meeting is an opportunity to seek feedback on work completed and gain ideas and inspiration from your tutor. At each sprint meeting you need to have on screen your Friday blog entries completed to date (see below for addition details) and your work open in Visual Studio. Do not wait until your sprint meeting starts to open your work, time spent doing this count as part of your 5-minutes. There are two types of sprint meeting; 5-minute and 10-minute.

These meetings provide an opportunity to obtain provisional marks and feedback on work currently in development. If your work is either very poor or incomplete, it doesn’t matter. Now is the time to gain positive guidance on how to improve what you have done so far. If you have already obtained provisional marks for some work at a previous meeting and have now made improvements to the work you have the opportunity to claim a higher grade. Do remember though that you only have 5 minutes for the meeting. It is therefore not a good idea to concentrate on a single small component for all of the meetings to the expense of the other components. Aim to obtain feedback on a range of different components. 5-minute sprint meetings will take place during the 2nd part of your Online Practical timetabled session.

Once the series of 5-minute sprints is over, you will hand in the work via the normal mechanisms (Turnitin etc). You will then have opportunity to obtain final grades and feedback during your team’s 10-minute sprint meetings.

10-minute sprint meetings take place after the work has been formally submitted after the Easter break in weeks 29 and 30 with week 31 being used as an overflow if required. This means that any issues with the work at this point may not be fixed, the marks awarded are final.

Rather than running in the second part of your online Practical timetabled session, the 10-minute sprints will take place during the full 2 hour online timetabled practical sessions. The 1-hour face to face timetabled labs will also be converted to online Practical timetabled sessions and also used for the 10-minute sprint meetings.

When the time comes for your 5-minute sprint meeting, you will typically have two blog entries for review by your tutor. These blog entries need to be on-screen and ready for your tutor to review. Any blog entries that are posted after the deadline of the previous Friday will not be considered as part of the sprint meeting and will be subject to the normal rules for submission of late submission. Each blog entry should contain but not be limited to the following sections.

  • Date, deadline time and week number for the blog entry
  • Discussion of progress made
  • Difficulties you have faced
  • Work you plan to undertake next
  • Attendance and minutes of team meetings
  • Peer review out of five of each team member’s performance for the sprints so far  Make sure you use appropriate headings in the blog to make sure the sections are clear.

Each blog entry is subject to a word count of 125 words (+-10%). Items marked * above do not contribute to the final word count. It is probably a good idea to create your blog entry in Word first and then paste it into the Blog to submit. Do not attach the Word document. You will be shown where how to submit your blog in one of your online practical sessions prior to week 3.

support
Whatsapp
callback
sales
sales chat
Whatsapp
callback
sales chat
close