2016 Fuzhou University software engineering fifth to sixth team work-alpha stage Results Summary

1, the results of the operation results:

This alpha phase of team work is published as follows:

Table Description:

PE: Percent contribution

YS: Demo Rating (15 out of)

BK: Blog Rating (out of 15)

SH: Hindsight Link (out of 5)

P: Personal score

Personal score =0.7* Team score +0.3* Contribution ratio * Team SCORE * Team size

School Number	Constituencies	PE	Ys	Bk	Sh	Personal Score
031402606	606notconnected	16.00	13.50	14.00	4.00	31.122
031402631		18.00	13.50	14.00	4.00	32.256
031402618		16.00	13.50	14.00	4.00	31.122
031402632		16.00	13.50	14.00	4.00	31.122
031402629		18.00	13.50	14.00	4.00	32.256
031401433		16.00	13.50	14.00	4.00	31.122
031402410	Aruba	16.70	11.50	13.00	3.00	27.5165
031402408		16.70	11.50	13.00	3.00	27.5165
031402431		16.70	11.50	13.00	3.00	27.5165
031402428		16.70	11.50	13.00	3.00	27.5165
031402429		16.50	11.50	13.00	3.00	27.4175
031402409		16.70	11.50	13.00	3.00	27.5165
031402617	CLover	5.00	14.00	15.00	4.00	26.07
031402615		20.00	14.00	15.00	4.00	34.98
031402612		30.00	14.00	15.00	4.00	40.92
031402338		12.50	14.00	15.00	4.00	30.525
031402614		12.50	14.00	15.00	4.00	30.525
031402339		20.00	14.00	15.00	4.00	34.98
031402230	TAC Tank Team	17.00	12.50	11.00	4.00	26.2625
031402508		20.00	12.50	11.00	4.00	27.5
031402330		20.00	12.50	11.00	4.00	27.5
031402509		23.00	12.50	11.00	4.00	28.7375
031402224		20.00	12.50	11.00	4.00	27.5
031402324	Transcend	13.00	12.00	12.00	4.50	27.7305
031402317		13.00	12.00	12.00	4.50	27.7305
031402310		17.00	12.00	12.00	4.50	30.1245
031402340		17.00	12.00	12.00	4.50	30.1245
031402313		19.00	12.00	12.00	4.50	31.3215
031402327		11.00	12.00	12.00	4.50	26.5335
031402140		10.00	12.00	12.00	4.50	25.935
031402412	Noisy Starling (NO BUG)	16.70	14.50	13.00	3.00	30.5183
031402426		16.70	14.50	13.00	3.00	30.5183
031402402		16.70	14.50	13.00	3.00	30.5183
031402403		16.70	14.50	13.00	3.00	30.5183
031402401		16.50	14.50	13.00	3.00	30.4085
031402418		16.70	14.50	13.00	3.00	30.5183
031402337	All I'm saying is the team.	14.30	15.00	15.00	5.00	35.0105
031402209		15.10	15.00	15.00	5.00	35.5985
031402342		14.50	15.00	15.00	5.00	35.1575
031402304		14.30	15.00	15.00	5.00	35.0105
031402203		15.20	15.00	15.00	5.00	35.672
031402233		12.10	15.00	15.00	5.00	33.3935
031402341		14.50	15.00	15.00	5.00	35.1575
031402517	It's a fire.	3.00	13.50	13.50	4.00	23.653
031402515		14.00	13.50	13.50	4.00	30.814
031402505		23.00	13.50	13.50	4.00	36.673
031402504		14.00	13.50	13.50	4.00	30.814
031402524		14.00	13.50	13.50	4.00	30.814
031402511		23.00	13.50	13.50	4.00	36.673
031402516		9.00	13.50	13.50	4.00	27.559

2, Blog job scoring standard:

15 Out of

Link	Project	Score
Daily (10 minutes)	Stand-up meetings	1 minutes per day
	Yesterday's Progress
	There is a problem
	Schedule today
Test schedule (2 points)	Test schedule	0.5
	Tool selection and Application	0.5
	Use case documentation	0.5
	Test description	0.5
Summary (3 points)	Expected plan	0.5
	Practical experience	1
	Crew Division	0.5
	Next stage Outlook	0.5
	Other	0.5

3. Percentage of linear mappings

Map each student's total score from high to low linearly to the [50,100] interval, as shown in the following:

4, this homework reviews:

First, the special praise under the "I said the team" team, the team's PM is very strong, the blog beautifully written, informative, clear, and typesetting, not to give a full score of the words simply God forbid. Look at the blog there are members feeling because of the time to get, stay up time is the least, to the leader 031402304 points greatly praise, other team also reference reference this benchmark

The following is insufficient:

1, the automatic testing process is not enough attention

Many of the team's automation process is true, but the brother in the first job requirements of the second item, the clear requirements of the "sprint process to gradually expand automated testing work." However, many groups did not perform automated tests in the test session, either using manual tests instead or not testing at all. For example, in the Nobug team blog for a long while do not know how to carry out the test link, the collection of their logs did not summarize and test the link of the document, the TA said to find a good hard. The corresponding points are deducted in the test without meeting the requirements.

2. The importance of GitHub

One team finally realized the importance of GitHub in the last two days and criticized it here for a long time before, after all, the application of GitHub was emphasized. Eat a loss your wit, the elder brother to GitHub the targeted deployment of a small quiz, in the beta phase and do not travel

3. Job Page

In the team work interface, three teams did not click Submit jobs. There are two teams in the sixth team work did not submit, I would like to know if you are late submitted, at least read the blog page submission time is before the deadline, did not give 0 points, ta feel good regret.

5. Apologies

Here to everyone apologized, recently this period of time ta big history due to personal feelings caused by the results of the summary of the error delayed the team's performance summary, here self-criticism.

2016 Fuzhou University software engineering fifth to sixth team work-alpha stage Results Summary