Third Sprint and course design 617

1. This cycle is relatively short, or according to the previous sprint process requirements, backlog-Kanban-Burndown chart-Daily stand, etc., and reflected on the blog.

2. Demo time: June 2016 21 pm

The demonstration can refer to the graduation design reply, which contains two parts:

Project presentation, which summarizes the project, team, development process, etc.

Run demos, implement functions, business, user feedback, and more.

Hope that the group carefully prepared to come up with the best lineup of the best state, show a semester of study and work results.

3. Software Engineering Semester Summary

Each student publishes a blog, to this semester's study, the project practice carries on the review, the analysis and the summary. The TA said he hoped everyone would give feedback on his work in order to improve it.

4. Course Design for next semester

• Completed the "Law of construction" reading notes.
• Publish our apps/websites to real users and collect feedback.
• Continue with the current project and do at least two full sprints.
• Score according to the code uploaded by GitHub and the content submitted by the blog.
• Make our app/website a better place.
• Continue to operate, as a representative of the university period.
• If a group wants to change the topic, it needs approval.
• Our deadlines will be in the next semester, but you can make use of the summer vacation ahead of time and continue to improve.

----------------------------------------------------------------------------------------------------

Third Sprint and course design 617