Teamwork—beta Spring

Deadline

The deadline for this assignment is December 20, 2024, 23:59

1. Assignment Requirements

1.Blog Submissions

The following content is basically arranged in chronological order. Please arrange your time reasonably and do not concentrate multiple tasks into a certain period of time to complete intensively.

• 1 top-of-the-line collection of essays in the Beta stage, including links to all the following content
• 1 Specific requirements for the alpha phase problem summary essay (published before the start of the beta sprint and added to the collection of essays)
• 1 essay on "Preparing for Everything" (published before the start of the beta sprint and added to the collection of essays)
• 1 essay about the team's code standards
• 5 beta sprint essays.(Arrange a sprint until the end of the assignment during this assignment. Ensure that the essays released by the team are not published on the same day).
• 1 user usage survey report
• 1 Beta sprint summary essay
• Project classroom demonstration and defense
• Make defense PPT

During the Alpha sprint, many students experienced "learning by doing", learning a new programming language, learning Git, and learning to build a complete project. However, each group did not have a deep understanding of the meaning of "learning by doing" in software engineering and encountered many problems. Stop for a while, hold a summary meeting, and gain hindsight.

2.Improvements and new features are needed in the next phase.

• Team division of labor needs to be improved (regarding previous deficiencies, team collaboration and division of labor need to be strengthened and improved)
• Tool processes that need improvement (such as version control, testing tools, etc.)
• The planning and arrangement of all blogs, as well as the time planning of the sprint.
• Specific requirements for the sprint essay blog.

2.sprint blogs

The sprint blog is divided into two parts: scrum and PM report

1.SCRUM section

• Description of each member: achievements from yesterday’s stand-up meeting to the present (which task was completed, how much time was spent, and how much time is left), existing problems/difficulties encountered, and arrangements for the stand-up meeting from now to tomorrow. (can be listed in tabular form)
• If the team members' work is development work, they must have code check-in, and provide the Issue content and link/picture corresponding to the check-in record. (If missing, deduct 2 point from the sprint log that day)
• If the work of team members is testing and other work, it must have specific results, such as screenshots, test reports, etc. （If missing, deduct 2 point from the sprint log that day）
• A photo of the SCRUM meeting. The meeting photo should be real, unstaged photo of the daily sprint meeting. Faces can be covered to protect privacy.（If photos are reused, the sprint log will not be scored on that day.）

PM report

• Summarize the expected taskof the entire project (the expected time of all work or the total number of issues), the work that has been completed so far (the time it takes to complete the work or the number of issues that have been completed), and the remaining work (the expected time of the remaining work) or the number of remaining issues)
• Draw a burn-up chart to show the real situation
• Record the changes in the total amount of tasks, reflect how many things you have discovered during your work that you had not thought of before; (you can draw a chart)
• Latest running pictures/gifs/videos of appropriate project procedures/modules （If missing, deduct 2 point from the sprint log that day）

3.Beta Sprint Summary Essay Blog Specific Requirements

• Corresponds to the tasks set before the start of the sprint (functions to be improved and added). Use a table to display the completion status; for items that have not been completed, describe the specific degree of completion.
• In the "Problem Summary Essay in the Alpha Phase" and "Essay on Preparing for Everything" before the start of the sprint, your team set up some improvement plans. How was the completion of these plans?
• Runnable project links, project files, program QR codes, etc. If it is a mobile project such as a WeChat applet or APP, please pay attention to the corresponding online review mechanism, required time and other matters, and be sure to understand and prepare in advance.
• Running pictures, gifs or videos of each function of the project
• Each member’s experience, gains and insights during the sprint phase
• To distribute the contribution of each member, you can use the following markdown

Student ID

Task Description

Contribution

3.Scoring Rules for this Assignment

1.Defense Score

1. Defense Score (consistent with previous scoring rules) = Sum of scores from other groups/(total number of groups-1) * 0.25 + Sum of assistant scores/(number of assistants) * 0.35 + Sum of teacher scores/(number of teachers) * 0.40

2.Blog Score(100'):

• （20'）Summary of issues in the alpha phase (with the benefit of hindsight)
• （14'）Answered questions related to assumptions, goals, and plans; answered questions related to design/implementation, testing/release
• （28'）5 beta sprint essays
• （10'）user usage survey report
• （12'）Beta sprint summary essay
• （10'）Project expected plan, degree of completion, improvement plan completion status, project running link and screenshot display, etc.
• （6'）Process experience, team members’ division of labor and collaboration

​ Score for this assignment = Defense score * 60% + Blog score * 40%

Blog Guidelines

1. Submission Rules

• The blog is subject to the submission time of the class assignment page; the files that need to be submitted are subject to the submission time of github;
• Submitted before the deadline, the score will be the actual score;
• If the post is under review after it is published (the post displays 404), you can submit the link to the assignment page before the deadline and wait for the review to pass.
• Reasons for resubmission such as upload failure and network reasons will not be accepted.
  • Late Submission: Submitting within two days after the deadline is considered a late submission, and the score is the actual score * 50%; writing but forgetting to submit the assignment and late submissions are penalized equally.
  • Missed Deadline: Failing to submit the blog within two days after the deadline is considered a missed assignment, and the score is 0.
  • Assignment Plagiarism: When the teaching assistant finds that two blogs have text/images/code that are too similar, both blogs are considered plagiarized, and both receive a score of -100% (note that this is a negative score!).
  • Forgery of Submission: Although the assignment blog has not been completed, submitting it to occupy a place is considered a forged submission, and the score is 0.
  • Note: For assignments submitted in advance, if you can actively respond to teaching assistant and teacher feedback and make corresponding revisions before the deadline, these improvements will be taken into account in the subsequent grading. Early preparation has many advantages. Please note that editing blog content is not allowed after the deadline.

2.Points to Note

If the class group releases relevant notices, it is also part of the assignment requirements; please check the group notice in time. If you need to fill in related information in the group and fail to complete it before the deadline, deduct 50% of the actual score. If there are any questions about the assignment, please raise them in the class group three days before the deadline. If the assistant makes changes to the assignment requirements, it will be announced in the group; please be sure to check and improve the assignment according to the new requirements. Please respond promptly to the comments from the teacher or assistant and make the corresponding modifications. Even if the assignment is submitted, pay attention to the announcements from the assistant in the class group!

3.Clarifying Doubts

If there are unclear aspects of the assignment or if you don't understand something, you can ask in the QQ or WeChat group.