Có một số bạn chia sẻ với Scrumviet, thỉnh thoảng bạn lại nghe một ai đó nhắc đến “Sprint 0”, “Design Sprint”, “Hardening Sprint”.
Và bạn phân vân tự hỏi, liệu những dạng Sprint này là gì? Chúng có tồn tại không và có mang lại lợi ít khi thực hành Scrum không?
Scrum đề ra ba vai trò trong Scrum Team: Product Owner, Scrum Master và Development team. Nhưng cũng có nhiều câu hỏi được đặt ra, liệu một người có thể vừa làm Product Owner vừa làm Scrum Master?
Some people asked me about Sprint Length and how to define sprint length. Most of the concern is can we do Scrum with 1 day Sprint? Can we do Scrum with Sprint longer than 1 month? So this post will go through this topic.
I always say Definition of Done is simple: It is just a common language/ understanding about "What done means" of Scrum Team and stakeholders.
But why is it very important?
Well! Let's go through events inside a Sprint and see how DoD support Scrum team.
1. At Sprint Planning: Definition of Done helps and guides Development team forecast about how many Product Backlog Items they can do within this sprint to achieve a sprint goal.
I got interesting questions about Daily Scrum and would like to share it today. Some people asked me a question about "hold Daily Scrum at the beginning of the day", let’s go into the details of this case:
- Scrum Master asked the team to have daily Scrum at the beginning of the day.
- The reason he wants to have Daily Scrum at beginning of the day is: He thought Daily Scrum must be held at early of day and it also brings one benefit that people go to office right time, and people can start to work right after the meeting.
Why we are here?
Last week I had a short discussion with some fellows, one of the interesting topic is about "Human Resources", and most of them had an issue with how to align Scrum with HR department: