3. 敏 捷 式 專 案 管 理 的角色
(Scrum Roles)
產品負責人(Product Owner)
Owns „what” is desired and it’s desired
敏捷教練(Scrum Master)
Keeper of Scrum Proces, facilitator
敏捷團隊(Scrum Team)
Owns „how” and „how quickly” work is delivered
利害關係人/贊助人
(Stakeholders/Sponsor)
They have money :)
使用者(Users)
They will use our product
4. 衝刺計畫會議 Sprint Planning Meeting
“What” is to be developed? “How” it will deliver the Sprint Goal?
每日衝刺會議 Daily Srcum Meeting
The Daily Scrum is the key inspect and adapt meeting during a Sprint .
衝刺檢視/展現會議 衝刺 Review/Demo Meeting
A 衝刺 Review/Demo meeting is held at the end of the Sprint to inspect the Increment.
衝刺回顧會議 衝刺 Retrospection Meeting
In the Sprint Retrospective the Scrum Team revises their way of work in the past in order to make it
more efficient and effective in the future.
敏 捷 式 專 案 管 理 的慶典
(Scrum ceremonies)
5. 產品待辦清單(Product B a ck l o g )
Ordered list of everything that might be needed in the product. The Product Backlog defines
the “What” that will be built.
衝刺待辦清單(衝刺 B a ck l o g )
The 衝刺 Backlog is the set of Product Backlog items selected for the 衝刺 plus a plan for delivering the
product Increment and realizing the 衝刺 Goal
產品的增量(Product Increment)
A 衝刺 Review/Demo meeting is held at the end of the 衝刺 to inspect the Increment.
敏 捷 式 專 案 管 理 的工作產出
(Scrum artifacts)
6. 敏 捷 式 專 案 管 理 的程序
(Scrum process)
來自客戶,團隊,主管的投入
Inputs from customers, team, m a n a g e r s …
產品
負責人
產品
待辦清單
敏捷
團隊
衝刺
計畫
會議
衝刺的
待辦清單
敏捷教練
Daily Stand Up Meeting
衝刺 Review
衝刺 Retrospective
衝刺、日期和團隊交付不變
衝刺 and date and team
deliverable do not change
Finished Work
團隊的選擇將從頭開始,盡可能
的承諾交付在衝刺結束後
Team selects starting
at top as much as it can commit
to deliver by end of 衝刺
需求優先級列表:
功能,錯誤...
Prioritized list of
what is required:
features, bugs…
迭代
Iteration
1- 4周的
衝刺