Reference no: EM131186103

Assessment: Teamwork - Version Control - Static Review

Task-

Conceptually, Assignment 2 is fairly straightforward:

As a team, carry out a development task, then review and combine the contribution of each team member into a completed whole.

In practice there are a lot of steps in this process.

On a weekly basis:

1. Carry out your assigned development tasks using best practice version control within your individual branch.

2. Communicate as necessary and desirable with your team members.

3. Upload whatever you have completed to version control as evidence for evaluation of work items.

4. Attend the weekly iteration planning and assessment meeting. At the meeting present whatever you have done in the preceding week and evaluate it against the objective completion criteria specified in the iteration plan.

5. Create a plan for the next iteration, setting out individual tasks and objective completion criteria for the coming week. Divide work equitably between team members.

Finally:

1. When you have completed your development task, conduct a static code review. You will need to participate in code reviews for the other members in your team as well.

2. Merge your individually developed code with the code developed by other members of your team in the team version control repository.

3. Write a 'phase status assessment' in which you address the following questions:

1. Did the team achieve the development task set for the assignment? What issues arose in achieving the final result How did the team manage those issues?

2. What issues regarding communication did the team encounter? How were these issues addressed?

3. What issues regarding version control did the team encounter? How were these issues addressed?

4. What issues regarding the static code review did the team encounter? How were these issues addressed?

Tasks-

1. Teamwork

This part of the assignment monitors and measures your individual performance as a team member. It assumes that you have successfully completed the team management aspects of Assignment.

Distributed teamwork is difficult and inconvenient, and the essence of teamwork is compromise. You must make yourself available to participate in team meetings once a week at a time that is generally acceptable to a majority of team members, even if it is somewhat inconvenient to yourself. Negotiation is acceptable. Rigid insistence on personal preference is not. Make it happen. Use weekends if necessary. If you can't make it to a generally favoured time be prepared to explain your objections with substantive reasons. Reasons such as favourite televisions shows, or preferring to go out at that time are not acceptable.

2. Version Control

1. As a team, download the files provided for the assignment from the subject website, and establish a code baseline under version control. Use github or any other free publically accessible GIT repository. Make sure every member of the team has read/write access. Grant the lecturer full team member access, and post the URL in the team wiki.

3. Static Code Review

As a team, organise a set of tool assisted static code reviews to ensure each team member's code development is acceptable before allowing a merge with the main line of development.

Presentation

There are three aspects of presentation for this assignment:

1. The team wiki. This should contain:

i. Your team charter.

ii. The URL for the combined team repository (the main line of development)

iii. The URLs for the individual team members development branches.

iv. The URL to the push communication mechanism you select.

v. The minutes for each of the weekly team meetings.

vi. The weekly iteration planning and assessment reports.

2. The combined team version control repository. This should initially contain the provided code baseline, and eventually contain the results of merging each team members separate development.

3. Your individual development repository. This should initially contain the code baseline as branched from the team repository. Eventually it should contain a record of the successive commits you make during development, and finally the results of updating your branch from the central repository prior to code review and merge.

Attachment:- Assignment.rar