Scrum 課程綱要 2015.11.02
Besides Dev.Job
Scrum Runtime <Important>
Sprint Planning <--> Daily Scrum --> Sprint Review Metting --> Sprint Retrospective Meetting --> Spring Planning Metting
Backlog Refinement Metting
使用 Task Board 來管制現場(類似白板的概念)
Product Owner (不管 Team 多大,都只有一個窗口)
依照商業價值排序需求
接受或拒絕工作結果
PO will develop functional test cases to validate that the requirement has done..(建立測試個案)
Owns this artifact
並非只有一種標準方法去取得 product backlog
Capturing Requirement
UseCase....等很多方法
User Story...描述故事跟流程
UseCase 還有 Business UseCase(GOOD) 純粹描述商業狀態
UseCase Desc.(description) 講重點,突顯明確表達
Use Case ID
Use Case Name
Actors
Description
Preconditions
Postconditions
Normal Flow
Alternative Flows
Exceptions
Activity Diagram + UseCase Diagram + State Diagram + Mockup Diagram => 可成案讓開發者了解
US & UC 不同處
UC show mere relations
UC show more detail in description
US show consequences(後續情境) Directly
Less is more
ICL interface control list
Granularity(粒度)
Sprint 越一開始越詳細,後面可以大略
=> Implementable User Story 1
=> Large User Story
=> Epic
UseCase
不需要一開始太詳細 (Dive & Surface) 合適的顆粒度,在合適的時間
Product Backlog (Invest Rule)g
Independent(可獨立
Negotiable(可協商
Valued(可計算
Estimable(可估算
Small
Testable
Do Remember
Prioritization!!!!
沒有留言 :
張貼留言