Group Report 3 29 Comments

#Group Report 3 29 Comments #Summarization:
This group report summarized the temporarily situation and did some preview about the future plan. According to the Agile software development method, we are between the middle between the strategy step and release step. Our first presentation should be good enough, everyone did a good job. What we decided to improve is a more detailed record about the problems we meet in each class. This kind of documents will help us to do a better summarization after each step and give others, specially developers a good advice to avoid the same situation happens.

#Strategy: Vision, Goals, Charter and Funding
We set up several goals on levels with different difficulties. Now we are proud to say that we have finished the first important step in our project. The core calls are almost implemented (only 3 left if I count with no mistakes). Besides that, since we have set up multi goals already, we can move towards next one without hesitation.

#Release: Backlog, Release Plan, Estimation
Because the next presentation (also the code review) is coming, we will need to move to the release step. However this release is aiming nobody else but our advisor. Our release plan is to implement the assignment we have from the php homework as mentioned by times. Now what we have is the output of get account, which can list the industries by select condition. And we still have a lot of works needed to be done on the unit test part. We decided and made changes with the structure of the folder, by advising that test function should be moved into an isolated folder. It will affect the unit test we have right now, since import path is moved. About the backlog part, git hub did a job that good enough so maybe we could skip that. And the estimation… we are not quite sure about the meaning of it. Is that a part of estimating the requirements of customers?

Kan Chai