Conclusion of the fourth scrum project of the real-life Boxing Emperor -- Shi jinhao

Today, I listened to Cherry Che's lecture on using TFs for agile development. let's review what we called scrum in the past week. We found that it was purely a lie: There is no user story and the user needs are unclear, the working item is very casual, the update is not timely, and the division of labor among the team members is unclear ...... In short, it is very informal. I should bear the primary responsibility for where to fight and as a PM.

In fact, let's calm down and think about it. We did a lot of work in the last two weeks: list the features we want to implement, classify them, and design them.ProgramThe framework is modified multiple times. However, these are not reflected in TFs and blogs. Instead, they tend to be familiar with DirectX and other things that are not painful, familiar with DirectX and other things cannot be written, but what does it deliver give to users? Do you need to be familiar with this? I also discussed this issue with cherry in class and suddenly realized that the division of labor among the team members was not clear enough: PM paid too much attention to the technical aspects and was not sure enough about the entire project; due to the intervention of PM, Dev lacks subjective initiative. The program framework design is rough and test does not know where to start. There is also the process of using TFs for agile development that is not familiar with (I feel that Cherry's lecture is a bit late). Working item often forgets to update what it thinks, I have never heard of user story. Basically, the process is based on the previous major course assignments, such as requirement analysis, outline design, and detailed design. In the past, it was just a pass. This is no exception. It seems that we need to reflect on the development process.

It's not too late to make up for it. Besides, we are still at the beginning of scrum, and we still have the opportunity to make up the previous work. In fact, we just sorted out the results we discussed last week, it should be included in the TFS management process and then executed in strict accordance with the agile development process. For details, please refer to the scrum summary today (strictly speaking, it should be called sync-up, not yet called scrum ):

• Improve the user story-> working item Process
  The PM mainly designs the user story based on the previous feature list, and then review it to the entire group. (This should be the last week's work, but I still don't know what it is called user story)
  
• Clarify the roles and tasks of the team members
  PM -- Shi jinhao: scrum master, project driver, blog poster
  Dev -- Tian Fei, Chen wenlin, Fu Hao, and Chen Zihe: design the framework and implement functions of each module
  Test -- Peng Xiulian: Works with Dev to design a test plan
  
• Detailed progress report of members

  	today	Problem and Solution	tomorrow
  Tian Fei (Dev)	working item 37528: demo of using DirectX to create an animation	image Background: hand it over to Chen Zihe for transparent background	working item 37528: added the interaction function with users
  Chen wenlin (Dev)
  Fu Hao (Dev)	working item 37518: program Framework Design and interfaces of various modules	none	working item 37518: program Framework Design and interfaces of various modules
  Peng Xiulian (test)	working item 37418: Test Framework Design	the program framework is unclear: discuss with Dev more	working item 37418: Test Framework Design
  Chen Zihe (Dev)	working item 37704: photo processing of character movements	the company does not provide Photoshop: Try blend	working item 37704: photo processing of character movements
  Shi jinhao (pm)	Working item 37708: User story	None	Working item 37708: User story

   

• TFs remaining Work Report