Moon Skirt Grab 98 units

　　　　98 points of the month skirt capture tile Team

　　　　　　　　　　　　　　　　--Software engineering team cooperation project

* Team profile : The team is a young and dynamic team.

* Team members Introduction :

　　　　　Captain Zhang Zhijie :3116005203 Style: lead the team to overcome one difficulty after another, solve one problem after another, a king

Role: Product manager.

Good at: JAVA,

　　　　　　　　　　　　　　　　　A word declaration: Rookie fly not high, but I want to carry team!

Jiang: 3116005180 Style: The team in the Yan value,

Proficient in Java, can independently

Role: UI Design

　　　　　　　　　　　　　　　　　　　　A statement: Rookie flying is not high, but also to get up early to find worms to eat.

Liu Yuegui Group: 3116005189 style: Elegant architecture, concise code Refining,

Good: Java

Role: Background development.

　　　　　　　　　　　　　　　　　　　　　A word declaration: Rookie fly not high, then jump away

Chen Junhao: 3116005173 style: Low profile

Good Technology: Reverse analysis

　　　　　　　　　　　　　　　　　　　　　　　　　　Programming Interest: Python

Soft worker role: development

　　　　　　　　　　　　　　　　　　　　　A statement: Rookie fly is not high, but still want to fly

Zhu Jiandong: 3116005209 style: Small white

Interest: Java, is trying to learn from the team of the big boys.

Role: The product is tested.

　　　　　　　　　　　　　　　　　　　A word declaration: Rookie fly not high, then fly lower

* Team Project Description:

Project name: A Wolf in the wind

Description: This is a pixel RPG game

* Team Feature Description

The team are very young and energetic lad, we rely on the king, meet with this, want to do a passable project, to sacrifice our play King and lost time.

* Group photo

* Topic Requirements

• Establish the team selection, and then each team will need to write a description of what the system is to be done, the expected number of users.
• Based on the content of the topic selection of the real, usable, valuable (with feelings as the addition of sub-items) objectives to be elaborated separately.
• Establish and initially familiarize yourself with the team's collaborative approach to git. Subsequent code and documentation for the project will be managed incrementally through Coding.net. Implement versioning and incremental management of documents.
• Create a git repository for your team project right away.

* 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 is 20N, where n is the number of teams. After Alpha/beta, the team divided the (20N) to each person according to their own rules, which is "team contribution points".
Requirements: Please read the "People, performance and professional ethics" chapter of the textbook, and then the team opens a seminar to discuss the allocation rules for team contribution points. Each person scores a natural number, and each person's score cannot be the same. Please write a team blog detailing how each team's members plan to help the team complete the task, as well as the allocation rules for team contribution points.

Difficulties encountered and their solutions

• Difficulty Description:
• What have you tried to do:
• Whether to resolve:
• What you have learned:

* Design Program Flow

Cond

* Key Code

Cond

* Test Run

Cond

* Project Summary

Cond

Moon Skirt Grab 98 units