Scrum drill (2)

C, of the three developers of ABC, will be on Monday, and will be temporarily absent.
First, define the sprint target, resource status, daily meeting time, and demo date. (These should have been set at the scheduled meeting last week)
When checking resource information, we found that ABC's investment was relatively low, from 0.5 to 0.3. The development cycle has changed from 8 days to 13 days. Try scrum first. It feels better.
Then, a simple system design is carried out, and a preliminary Architecture Scheme is defined.
The meeting was interrupted during Task breakdown. Leave AB to separate the task and select the task. A. Select the database design and B. Select the UI prototype.
 

On Tuesday, a is busy with other tasks. B is finished with the UI framework code and C is back.

Yesterday, I used the slide and pasted it on the glass. Many of them fell down. Finally, paste white paper on the glass, and paste it on the White Paper. See the results tomorrow.

The task board layout takes some time. Due to the actual situation, the task board should be pasted in the meeting room. If conditions are met, it should be pasted in the work area where everyone can see it in real time.

Currently, no detailed task breakdown is performed on the backlog. Break down a bit. A continues the preliminary database design, and BC enters the functional point development. B's functions are complex and require UML analysis.

The burnout chart goes down to a point.