Why it should be Sprint Review instead of Sprint Demo?

Tại sao nó nên là Sprint Review thay vì Sprint Demo?

A Sprint Review is more than just a demo; it is a review of the completed Sprint, the Product Backlog, and the Marketplace. Admittedly, demos are an important part of the Sprint Review. The purpose of the Sprint Review meeting is for the team to show the customers and stakeholders the work they have accomplished over the sprint and compare it to the commitment given at the beginning of the sprint.

Continue reading
Tại sao các đội phát triển yêu thích Scrum?

Tại sao các đội phát triển yêu thích Scrum?

A Scrum development team has the autonomy to choose how best to accomplish their work, rather than being directed by others outside the team. Unlike traditional management principles, the self-organizing empowered teams are not directed and controlled from the top; rather they evolve from team members participating actively & collectively in all the Scrum practices and events.

Continue reading
Scrum: How to Refine Product Backlog?

Scrum: Làm thế nào để tinh chỉnh danh sách công việc sản phẩm?

Not all items in the product backlog will be of the same size and level of detail (i.e. features/ eprics/ user stories and tasks) at the same time. PBIs that we plan to work on soon should be at the top of the backlog, smaller in size, and very detailed so that they can be worked on in the near-term sprint. PBIs that we won’t be working on for some time should be at the bottom of the backlog, larger, and less detailed.

Continue reading
Agile Backlog Prioritization Technique: MoSCoW

Kỹ thuật ưu tiên backlog linh hoạt: MoSCoW

MoSCoW Method provides a way to categorize users’ requirements based on their priority. It helps develop a clear understanding of the customers’ requirements and their priority. MoSCoW stands for must, should, could and would. Visual Paradigm comes with a rich set of diagram templates. You may start with a blank diagram or a pre-made MoSCoW Method template.

Continue reading