Big Horse Monkey Team-team work

Big Horse Monkey

Players

• Huang 3116005138

Style: Stimulating battlefield bombs Wang Zhong Wang

Good Technology: JAVA,98K,M4,AWM

Programming Interest: Javaweb background development

The desired soft worker role: development

A word declaration: Eat more vegetables, less drink soup

• Huang Yucheng 3116005137

Style: Xiao Gu wai Gao

Good Technology: PHP python Adcarry

Programming Interest: Python operations

The desired soft worker role: development

A statement: Old duck vermicelli Soup

• Huang 3116005136

Style: A little white in line to drink soup

Expertise: Python

Programming Interest: Python number one

The desired soft worker role: PM

A statement: Drink the soup and it's finished.

• Cai Haijie 3116005127

Style: 2kol Rodman

Good Technology: Java Android

Programming Interest: Android

The desired soft worker role: development

A statement: Soup is hot to drink

• Li Shu 3116005141

Style: The king of rap rhymes with Monsters

Good Technology: JavaScript

Programming Interest: Front end

The desired soft worker role: development

A statement: Drink more soup

Team Project

Simple version of web and app for imitation chat

Team Features

Gather is a piece of excrement, scattered is the stars

Team Planning

6th Week	1. team teams, team blogs
	2. Team presentation, member presentation, role assignment, selection of topics
	3. Develop team planning arrangements, Team contribution sub-rules
7th Week	1. Requirements Specification Sheet
	2. Prototype design, team members estimate task difficulty and learn the necessary techniques
	3. Coding specification Complete, platform environment set up, preliminary construction
8th Week	1. Prototype improvement (to demonstrate the prototype to the target user and further understand the requirements)
	2. Architecture design, WBS, team members estimate the time required for their respective tasks
	3. Test Plan
9th Week	1. Team Project Alpha Task assignment schedule
	2.7 consecutive days of Alpha Agility Sprint, 7 daily Scrum meeting blog + code submission
10th Week	1. User feedback + test plan improvement
	2. Team Alpha Stage Personal summary
	3. Team Project Alpha Blog: Release notes, test reports, presentation blogs, project management
11th Week	1. Team Project Alpha Blog: Post-mortem analysis
	2. One person on each team must leave and look for the next team to accept. The team sent out blogs announcing the departure and acceptance of the members.
12th Week	1. Team Project Beta Task Assignment plan, introducing new members
	2.7-day Beta Agile Sprint, 7 daily Scrum meeting blog + code submission
13th Week	1. Team Project Beta Blog: Release notes, test reports, show blogs
	2. Team Beta Stage Personal summary
14th Week	1. Team Project Beta Blog: Post-mortem analysis, announcing the contribution of each person
15th Week	1. The team summarizes the whole stage, analyzes the user data, and organizes the documents to ensure that the future team can take over.

team member Performance evaluation method

member Performance = Team score + Individual team contribution points

After the project Alpha and Beta review, the team gets a project score (each member will get the same score as part of their original score). Team members of different efforts, to achieve a different degree of goal, to help peers pay different, it will be in the "Team contribution points" on the distinction. The sum of all contribution points isn, where n is the number of the team. after the Alpha/beta , the team divided the (N) to each person according to their own rules , which is "team contribution points".

Big Horse Monkey Team-team work