Teamwork fifth - Project sprint

Teamwork fifth - Project sprint

Submission rules

deadline1: As of 2019-11-15 23:00

deadline2: As of 2019-11-17 23:00

Time delivery: Before deline1, the actual score obtained 100%

Pay: After deadline1, before deadline2 (wrote forget to submit a job in the blog garden, judged according to blog Published) for the pay, withholding the actual score * 10%;

Late: after deadline1, before deadline2 (deadline1 no homework, deadline2 write it up and submit it) is late, this assignment 0 points;

Lack of pay: pay or not to pay absence regarded blog post after deadline2, the fraction of negative work out;

Key will do the job is not completed: The job is zero, will do items are (will do) in the identification with operational requirements

Micro-channel release notification if the class group is part of the job requirements, please see the notice group;

If you need to fill out the information in a micro-channel group, failed to complete the prior deadline1, deduct 50% of the actual score;

Questions on the job, put forward in the class group in deadline1 three days before;

If the job requires a modification assistant, you will notice in the group, be sure to check and press new demands perfect job;

Sui Suinian

In the system design and database design job, everyone on the system level view of the system, class diagrams, database has been designed;

Most of the students in the class diagram design and database tables there which is not good place; so before the formal sprint should be good reason for a reason;

The purpose of this work is to everyone's actual coding of the project team to achieve it, at the same time agile development team practice;

We see that already in place, but how effective collaboration among team? How to make progress of the project are within expectations every day?

These are discussed in the theory of soft labor practices, this time the job is to compress the actual project development company within two weeks to allow everyone to experience the process;

Preparation may quicken the work, the work we still have to develop a good plan in advance, a clear grasp of agile process models to begin development;

Next is operational requirements;

Work requirements

Essay

First, a forewarned is forearmed essays [team name - Forewarned is forearmed], be released before 23:00 11-04

1. Sprint time schedule (seven-day sprint time, arrangements between 2019-11-3--2019-11-14)
2. For the last answer job students, teaching assistants raised the question, if it is to be perfected class diagram or table structures, which are rendered by the chart, please paste together to essays
3. Reflection and summary for the previous lack of local jobs
4. The team needs to be improved division of labor (for the previous lack of a need to strengthen and improve local teamwork and division of labor)
5. Team code standards, reference blog: operational requirements - code specifications
6. Read chapter 13-17 of the law building
7. Team building project github repository and link attached to the end of the essay

Second, a collection of essays sprint team name [-] collection of sprint, team sprint to place seven times link blog, in order to facilitate the teaching assistants to find, this blog will need to top

1. Use markdown link tables to render
2. Clearly marked the name of each log has a blog, as well as the corresponding dates, the day the amount of work remaining workload, work has been completed percentage of the total workload
3. Day sprint logs should be added to this essay
4. The end of the essay accompanying the team project github repository

Third, the seven sprint log essays [team name - Sprint logs (first few days)]

Daily scrum and sprint blog is divided into two parts PM Report

1. SCRUM part:
   each member Description:
   (1) my yesterday's progress (which completed the task, how much time, how much time remains), what problems encountered yesterday, yesterday solve what problems, (see previous program requirements ), plans for tomorrow. (Can be listed in tabular form)
   work (2) If the team members are working to develop the code must check-in, check-given record corresponding Issue content and links, the code must be performed every day (the day of screen shots, no points down )
   work (3) If the other team members work testing, that there must be concrete results (screenshots, test reports, etc.)
   photos (4) SCRUM meeting of a conference picture should be a day of non-real sprint conference shot put photos can protect his face to protect privacy. If this picture appears multiplexing pour points.
   (5) at least one project procedures / modules of the latest (run) shots.
2. PM reports:
   (1) the entire project expected amount of tasks (assignments = expected time all the work) and now spend time ( 'time is spent' all records), but also the rest of the time (all the work of the 'surplus time ')
   (2) PM drawn burndown chart (you can use third-party tools, or their use Excel to do it yourself). You must display two time changes during the entire sprint: Time already spent all the time, but also all the remaining work.
    Burndown need to show the real situation. Burndown have requested levels:
     ① to the number of tasks as a unit, this figure can show changes in the number of daily tasks. Reference Github generated using burndown .
     ② in hours, the time change of the display (see above article requirement).
   (3) Draw a "total task changes the line", reflects the number found previously did not think of things at work.
   (4) in tabular form than the contribution of each member

Fourth, an essay test team name [-] test summary, released before 23:00 11-14

1. Arrange testing describing the project
2. Selecting and applying testing tools
3. Pdf document test cases of git address
4. Testing Experience
5. Project Test Review

Fifth, a sprint summary essays [team name - Sprint summary], on this blog as the job is submitted essays, this one can only pay

1. Comes Forewarned is forearmed, test blog links
2. All the contents of the log contains a collection of essays in sprint
3. Describe the project is expected to plan
4. Real progress of the project
5. Process each member experience
6. The proportion of members of the division of labor and workload at all stages of
7. Accompanying code repository address, link address test documents, PPT link address

Reply process

1. Works display, please demonstrate students to carry, the computer takes a good pre-commissioning project, determined to run, if you need to use the phone to a computer screen cast, pre-commissioning well prepared in advance;
2. PPT presentations
3. PPT presentations and lectures work time control in 10 minutes

PPT defense requirements

1. The project members division of labor and the expected plan
2. The actual progress of the project curve, burndown
3. What are the problems encountered, and how to solve
4. Photo 1 best shot SCRUM meetings feel
5. The actual structure of the project: the front and rear end development framework, to use the technology, deployment processes, etc.
6. Arrange testing describing the project, the choice and application testing tools, test projects reviewed
7. Process members experience

Remark

Please in this job every essay that begins to add formatting description

This work belongs courses	<Class link>
Where the job requires	<Link job requirements>
Team Name	<Write the team name to>
The target job	<Write on specific aspects>
Text of the job	....
Other references	...

Sprint logs completed on time

The TA will check each specific requirements, if they meet the requirements, give points, not points on the back (not for 0), we do not require burn-down charts show a smooth curve downward, but requires burndown display real Happening. Obviously false data would have been processed down the point system.
Late-day report, the same day the report was 0 points. (24:00 GMT latest time of day)
day N reports submitted delayed one day, to give the N-th day 0.
Report of N days, did not submit more than one day, upside down day N score.
Report of N days, it should be real and effective, obviously submitted false data intentionally fool, upside down day N score.
The report does not pay day, the day the report was upside down all the scores. For example, out of ten, the same day the team will get (-10) points.

Site assessment requirements:

a) scoring items, including: PPT mass (20 '), speech (10'), the function completion (30 '), UI design and interactive experience (20'), teamwork (10 '), testing (10' there are also partially fill the existing problems and suggestions;;)
b) Rate requirements: respect for his group, scoring serious, pragmatic, adopt a standard for all groups, consensus scores can truly reflect the quality of reporting and other groups of this group prohibiting pot side flat case;

Grading

1) reply peer assessment team (30%), TA will prepare evaluation table
2) TA rates (50% reply, blog 40%, 10% review code specification), the results were 70%
3) The reply operations team score = peer assessment score + TA ratings

appendix

1) SpringBoot Quick Start Video
2) SprintBoot Web Advanced Video
3) SpringBoot integrated JWT achieve token verification
4) Lay ui classic modular front frame
5) Bootstrap rookie tutorial
6) iBootStrap drag generated layout
7) About Web front-end password encryption if there meaning summary!
8) IDEA plug-in installation code specifications Ali
9) jQuery newbie tutorial