Alpha Stage Issues Summary Essay

 I. Assignment Information

This is a essay that summarizing issues in the alpha stage

Which course does this assignment belong to	2301-MUSE社区-CSDN社区云
What are the requirements for this assignment	Teamwork——Alpha Sprint-CSDN社区
The goal of this assignment	collect all essays and materials concerning Beta Phase
Other references	NULL

---

目录

 I. Assignment Information

II. Issues in Alpha

α.Vision and objectives

 β. Plan

 δ. change management

 ε. The role of the team, management, cooperation

 ζ . Design/implementation

 η . Test/Release

III. The Most Important Problem to Solve in the Beta Phase

---

II. Issues in Alpha

α.Vision and objectives

1. What problem does our software solve? Is it clearly defined? Is there a clear description of typical users and typical scenarios?

   THEMIS rental platform is mainly dedicated to improving the utilization rate of idle items among members of the school, saving social resources, and our software realizes the rental and rental of goods

   Typical user: FuZhou University students

   Typical scenario: the rental of idle items in daily life and the rental of short-term needs

2. Did we achieve our goals (how many of the planned features did we achieve? Was it delivered according to the planned delivery time? Has the planned number of users been reached?

   Planned functions: Several key basic functions have been implemented, including user registration and login, user personal information modification, Posting and comments, and software bug feedback.

   Delivery time: Most feature implementations are successfully delivered within the planned time frame, but some features have unknown bugs.

3. What are the lessons? If history were to be repeated, what improvements would we make?

   Strengthen team communication and division of labor, and timely communication between teams can effectively solve problems such as functional interface and code specification docking in a timely manner. Developers have a set of standardized material integration format so that clerical staff can write blogs efficiently.

 β. Plan

1. Is there enough time to plan?

   Yes, we planned the time of the sprint before the Alpha sprint started.

2. How did the team resolve disagreements with colleagues during the planning phase?

   Speak directly in the work communication group or report problems to the team leader.

3. Did you finish all the work you had planned? If there's something unfinished, why?

   It's almost done.

4. Are there clearly defined and measured deliverables for each task?

   For front-end pages, we use the matching degree of interface and function to deliver; For the back-end interface, we use the interface test to return the correct result to deliver; For features, we deliver them by completing the definition in the prototype specification.

5. Did the whole process of the project go according to plan? What happened to the project? What risks were not estimated at the time, and why were they not estimated?

   Progress is generally smooth, with the risk that some members sometimes do not complete their assigned tasks in time, delaying project progress.

6. Is there a buffer in the plan? Does the buffer work?

   No buffer is left. Resulting in some unfinished work delayed subsequent work.

7. What changes will be made to future plans? (e.g. Definition of buffer zone, overtime)

   Add buffers to the plan, use your own knowledge to improve features, and communicate with other software similar groups to improve each other.

8. What have we learned? If history were to be repeated, what improvements would we make?

   Assign tasks to members more rationally. Also hold each other accountable for the completion of tasks.

 δ. change management

1. Was everyone involved informed of the change in a timely manner?

   Yeah, the group leader keeps the group informed

2. What method did we use to determine "deferred" and "must implement" features?

   The priority of function implementation and the degree of function completion are discussed comprehensively

3. Are the project's Exit Criteria (what is meant by "done") clearly defined?

   For front-end pages, we deliver them with a match between the interface and the prototype design; For the back-end interface, we use the interface test to return the correct result to deliver; For features, we deliver them by completing the definition in the prototype specification.

4. Is there a contingency plan for possible changes?

   Yes, after daily group discussions, we are generally able to handle changes, solve problems, and make contingency plans better.

5. What have we learned? If history were to be repeated, what improvements would we make?

   Strengthen team communication and division of labor.

 ε. The role of the team, management, cooperation

1. How is each role of the team determined, and is it the best use of talent?

   Yes, after the project is approved, meetings are held and functional modules are divided according to the basis of each person.

2. Do team members help each other?

   Yes, ask questions in the group, and other members answer them in a timely manner.

3. When project management and collaboration issues arise, how do team members solve the problems?

   Solve problems through meetings if necessary.

 ζ . Design/implementation

1. When and by whom was the design work done? Is it the right time, the right person?

   It is appropriate for all team members to work together during the prototype design phase.

2. Did the design work encounter ambiguities, and how did the team resolve them?

   Yes, when working on software design ideas and functional implementation. Work it out in small groups.

3. Does the team use unit test, test-driven development (TDD), UML, and other testing methodologies?

   Yes, for the back end we used unit testing and then integration testing

4. How is the Code Review conducted, and is the code specification strictly enforced?

   Compare the corresponding Vue and Sprintboot official documentation for code review.

 η . Test/Release

1. Does the team have a test plan? Why not?

   Yes, after completing the basic function, some bugs in the Posting function were found in the test.

2. Have formal acceptance tests been conducted?

   No official app has been released yet.

3. Does the team have testing tools to help with testing?

   Yes,  we use Postman for API testing.

4. How does the team measure and track software performance? Are these tests useful in terms of how the software actually works? What improvements should be made?

   I haven't considered this part of the functionality yet; Effective and timely detection of potential bugs in software.

5. What have we learned? If history were to be repeated, what improvements would we make?

   Adequate time should be set aside for testing software features and release debugging.

III. The Most Important Problem to Solve in the Beta Phase

• There is no black box test for user revocation and there may be a problem;
• The user interface is not beautiful enough;
• User information: The profile picture cannot be transmitted.