để đảm bảo rằng nó phù hợp với tiêu chuẩn các dịch vụ web khác nhau. Để làm được điều đó, kích chuột phải vào file trong Eclipse và chọn "Xác nhận". Nếu có bất cứ điều gì sai, họ sẽ được báo cáo trong cửa sổ vấn đề. | user stories ind tasks It s time to get you and your team ot developers working. Take each of the iSwoon user stories for Iteration I and assign each to a developer by drawing a line from the user story to the developer of your choice. you are here 111 break up user stories Into tasks Now it s your turn. Take the user story of creating a date and break it into tasks you think you and your team need to execute. Write one task down on each of the sticky notes and don t forget to add an estimate to each task. user stories ind tasks Po your tasks add up Did you notice a possible problem with your estimates We ve got a Usei story w ill an estimate bill now We re adding nt it estimates In our tasks. What happens when the two sets of estimates don t agree esbmaie Order Floors development task5 THU. Order flowers tlti Priority . Task 5 Task b 1 A p Both oi these estimate ean t be ri ht r ht Create Send Flowers event that ởontains the address and 0 days Task estimates add confidence to user story estimates Your user story estimates kept you in the right ballpark when you Were planning your iterations lint tasks really add another level of detail specific to the a tual roiling you ll do I. I I - In lad. it s often best to break out tasks iiom your user stories light at the beginning of the estimation process. if you have time. I llis way you ll add even more confidence to the plan that yon give your customer. It s always best to rely on the task estimates. Tasks describe the actual software development work that needs to lw done ami are far less of a guesstimate than a coarse-grained user story estimate. Break user stories into i t Ĩ tasks to add CONFIDENCE to your estimates anJ your plan. Ạnd the earlier p Ito S do this. the better you are here .
