Some ideas about agile development

First, positive. Do not wait for others to assign tasks, after dividing the task card, according to the actual ability and ideas to collect the task, the personal initiative to play the strongest. Although some people are inevitably raped tricky, fishing nets, but at least to the greatest extent to avoid the task beyond the scope of the project delays caused by the problem.

Second, communication. We all work together to develop, naming specifications, some basic class calls, data encapsulation, and even project update submissions need to be communicated. Including the completion of the project within the group, each function module corresponding to the completion of each member has the right to know.

Iv. Change of requirements. The PO will come up with new requirements at any time, possibly supplementing the original requirements, perhaps altering the original requirement, or even overthrowing the idea. The results of the negotiations with Group A are very different from those identified by Group B. Even pre-confirmed parts, late anti-water, require re-design.

V. Mobility of Members. Because of the project needs, a bunch of strangers gathered together, the level of ability is not aligned, the direction is different, all are re-run to adapt, halfway, someone will leave at any time, someone will come in.

Six, emergency situation. Temporary request to check the progress of the project, presentation equipment failure, test error handling, facing the party a difficult, confused response measures.

Some ideas about agile development