Product Backlog: Continue down refinement;
1. Interface beautification, unified interface style, with concise aesthetics as the main;
2. Enrich the content of the layout, to attract users;
3. Try to add a new layout;
Sprint Planning meeting: Determine the goals to be completed for this sprint
1. To achieve user management of user information.
2. To achieve the content of the additions and deletions to change.
3. Optimize the code, try to make the code easy to manage and read.
4. Try to use the architecture, reconstruct the project, and do not know whether it can be completed, but will try it out of the plan.
Goal: Make your Web page better
Sprint Backlog: What to do with a new sprint
There is also a need for further discussion, and it is not possible to real deal the extent to which our team can be completed before the start of the project, but to understand the actual workload of our expected goals in practice after the start of the project, as well as the difficulty in judging the optimal plan in our ability range. Because the plan is not keeping up with the change, we can only give a plan to rush to now. The specific content depends on the actual ability of the players and the next course arrangement is not overflowing.
But there are goals that can be determined by completing the content:
1. Finish the design of the interface, unify the design style of the team before sprint, design a beautiful and concise page style.
2. Add some new layouts that are still too monotonous for now.
3. Unify the team member's naming norm and the design norm.
0601 Spring2.0 Press conference