Shulou(Shulou.com)06/03 Report--

Sprint is the heart of Scrum and lasts a month or less to build a completed, usable, and potentially releasable product increment. The length should be consistent throughout the development process, with the previous Sprint completed and the new next Sprint immediately followed, a bit like a baton game.

Sprint Planning Meetings: Don't over-meet, don't meet just for the sake of meeting. Usually within a month, with an upper limit of eight hours or less; and so on. Its main purpose is to make sure that each participant understands the purpose of the meeting. The Agile Coach ensures that meetings run smoothly and teaches Agile teams to follow the Time Box Rule. A few things: What do you do this time? How to complete the selected work? What problems will you encounter during this period? Expected deliverable increment? Daily Station Meeting: 2W1H, What did I do yesterday? What are you doing today? Do you need help from others? One thing to note is that the standing meeting should not be too long, and everyone should participate in the core, not be lectured, and ensure that everyone can speak and have the opportunity to lead the meeting; Development work: ensure that the Sprint runs properly through Kanban, code testing, code review, and communication;Sprint review meeting: held at the end of the Sprint, used to review the delivered increments and adjust the ProBackLog list as needed. Attendees: team members, customers, stakeholders; meeting time should also not be too long, depending on the size of the Sprint. Focus on a few key points in the meeting: what is "done" and what is "not done" with the probacklog, what problems are encountered and how to solve them, demonstrate "done" work and solve incremental delivery problems, discuss the current probacklog situation, predict possible target delivery dates based on current rates (mainly to clarify that the estimated delivery time is not accurate), discuss the next step, and update the probacklog. Attention: face up to the problem, solve the problem, not the accountability meeting, pay attention to the direction of the meeting! Sprint Review Meetings: Review and review. It is a good thing to review the current completed Sprint properly, so that we can summarize good methods and avoid stepping into pits. Its meetings take place after the sprint review meeting. The main point is the same as point 4. There are two kinds of meetings in the country: eulogizing or criticizing. Know the real purpose of the meeting: to ensure that team members have the same goals, meetings can make work more productive and maximize benefits.

The Sprint consists of the 5 points above, and throughout the sprint, there are several rules to ensure that the sprint is completed smoothly.

No change to goals, no degradation in quality, and partial adjustments to what the product owner and development team do in scope as the project progresses.

The length of each sprint should be limited to one month, too long, not in line with the essence of Sprint, through small versions of iteration, delivery to spy on user feedback, and make changes. If the time is too long, the risk is stretched accordingly and predictability is compromised.

In the previous brain map, we saw "cancellation". There are many reasons for cancellation: obsolescence, market change, customer not needed, technical level, etc. If Sprint is cancelled, then any "done" and "to do" list items need to be reviewed. If the result part is potentially available for release, a version release will usually be made.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.