Teamwork 6

Deadline:

The Alpha version displays
the profiles and personal blog addresses of team members, as well as the team's source code repository address.
Liu Yanghang: 201521123026 (leader)
Chen Wenjun: 201521123047
Lin Tingyi: 201521123031 Zheng
Zixi: 201521123045
Ding Shule: 201521123024 Ranking
of contributions of team members (from big to small, no parallel)

Team 8-day Alpha sprint stand-up meeting Blog link summary (collection post)
The team can make an MVP (Minimum Viable Product) version, as long as the core functions (such as user registration, password retrieval, these non-core functions can be omitted). It can also allow teams to demonstrate rapid prototyping solutions to potential users for feedback

If we want to do software engineering, we should have a little bit of engineering: (1) The goal of the team project, the expected typical users, the expected functional description, and where is the expected number of users? (2) How does the team's product meet the needs of users? (3) What goals has the team accomplished during the Alpha stage? (4) How do the members of the team work together? What are the lessons learned? (5) How does the team manage the project? (6) How does the team balance time/quality/resources to complete the task on schedule? (7) The actual progress of the team project (copy the burndown chart in the scrum process), and the released function (copy the release document). Explain how the burndown chart of scrum truly reflects the state of the project in project management? Or do burndown charts beautify the state? (8) What aspects need to be improved in the Beta stage? Please give an outlook for the next stage.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326428484&siteId=291194637