项目管理

Agile Basics

2020-01-04  本文已影响0人  XBruce

Agile 宣言

Sprint basics:

Sprint Planning

Input: Product Backlog of stories prioritized by the PO
Process: Review and select stories for the sprint
Output: Sprint Backlog of stories the team commits to complete by the end of the Sprint

Sprint Development

Input: Sprint Backlog of stories the team commits to complete by the end of the Sprint
Process: Daily reporting and execution against a few stories at a time: designing, building, testing and closing<Kanban, Burndown chart>
Output: A shippable product increment that can be demonstrated
Sprint Development begins with the daily standup. Daily standups are self-reporting of the team on what work they will get done that day. This is usually done around a Kanban board, or other big visual information radiator (BVIR). The team opens only a few stories at a time and work story-by-story to analyze, build, and test the work.
The result by the end of the Sprint is a shippable increment that can be demonstrated to the product owner.
Meetings are facilitated by the Scrum Master, and the Product Owner determines if a Story is complete to meet the stakeholder needs.

Sprint Review

Input: 可交付和演示的功能增量
Process: PO向stackholders演示功能增量,得到对方的feedback,同时使得team能更清晰产品的方向。同时,PO可以根据feedback指导下一个Sprint要完成的backlog。
Output: Feedback on the product's direction and actions to improve the next sprint

Sprint Retro

仅限团队内部人员,主要回顾即将结束的Sprint过程是否顺利,有哪些需要改进的地方,一般以Game的形式进行,此次会议注意不要搞成批判大会。

总结

Remember that we vary scope to target just what the customer needs, so we don't waste time or money in the process. That's the power of the varying scope. It's fast and limits waste by reducing the work to a minimum viable product (MVP) that meets the project objectives (in the charter). To do this, every Agile project needs:

image.png

Comparation Agile/Lean/Traditional.


image.png

Agile:
提要Speed最有效的诀窍:
要事优先,删减没有必要完成的

image.png
上一篇下一篇

猜你喜欢

热点阅读