Sprint1 Planning Meeting

Just opened a Sprint1 plan meeting, originally planned is two hours, 1.5 hours to end, although not in the time tangle, but the heart is still somewhat uneasy. The only consolation is that, after all, it is the first time, and Sprint is allowed to fail (no excuses). ）

Meeting on time is a rule that everyone should follow, but unfortunately two of the main team members are late. In order to remind, we temporarily write "I ' m Late" with sticky notes, let them put themselves in a conspicuous position.

At the beginning of the meeting, product owner introduced the story to complete the sprint and made a more detailed statement of the basic requirements. Product owner finished the statement, unexpectedly silence. Team member has not asked any questions, although I have repeatedly suggested that there are questions to ask early, so as not to misunderstand the demand. A few minutes, finally someone asked questions, but the question is not about the story itself, but to the specific implementation details. I haven't opened my mouth yet, Product owner said, "I think it's a matter of implementation." Product owner proposed 4 story, because at the beginning did not determine the priority, in the discussion process, we set the priority for each story, the largest of which is 100, the other is 80,50,30.

The first part of the one-hour meeting ended in less than 30 minutes. "Hidden Trouble" has been buried.
Next, of course, is to decompose the task. At this time one of the member (a bit with s instead) said, "I have no concept of this, I do not know how to do." How should we estimate the time? So I asked him, "Do you fully understand the need?" After a few minutes of silence, he asked Roduct Owner about some details of story. I added: "If you don't understand how to do it, you need research, you can do it as a task." Although the time is not good to estimate, but you always have to have a time. "At this point, another member (W Generation later) asked another story," I do not need to interact with the server. "Product owner asks," If there is no interaction, then how does the data in this story be synchronized? s exclaimed: "Wow, wow, this is a lot of work." It's impossible to finish these two weeks. "I said:" Then why did not ask clearly at the beginning of the demand. "s argues:" I thought ... "I interrupted:" Do not say that you must confirm with product owner whether it is the demand he wants. No person will deviate from, will do not work hard. OK, now that this is not done in this sprint, do you consider breaking down, or negotiating with product owner to do it in the next sprint. S argued: "I feel I can implement the server side first, can do a few tasks," he one by one detailed. So product owner asked: "How do You Give me demo." "S:" I am from the database, export the data to you to see. "Product Owner:" You give me the data, how do I know if you have finished the logic. You can only be a unit test of your code. "s thought for a moment and agreed with everyone's point of view. Finally, Product owner agrees to put it into the next sprint to complete the story.

After the twists and turns of the above, the task is very smooth decomposition. The amount of work is estimated in "per-unit". There is nothing wrong with this link.

After a 90-minute discussion, Sprint 1 's plan is over, and the whiteboard next to me is already plastered over the sprint's task pad.