Scrum Professional Scrum with Kanban level I - PSK-I 模擬練習

A. Visualizing your Workflow.

B. Limiting Work in Progress (WIP).

C. Inspecting & adapting your Workflow.

D. Actively managing WIP.

E. Ensuring the Product Backlog is refined frequently.

A. Kaizen, remove delays, visualize policies, pull system.

B. T-shirt size estimation, service level expectations, limit WIP.

C. Small batches, limit WIP, eliminate waste, Kaizen.

D. Visualizing flow, limiting WIP, actively managing the Work in Progress (WIP), inspecting & adapting the Workflow.

E. Class of service, cost of delay, visualize the Workflow, limit WIP, manage flow.

A. Definition of Ready.

B. Definition of Done.

C. All of the above.

D. Product Backlog refinement.

A. The Sprint Goal no longer helps the Developers. They do not know what they will be working on.

B. The Developers should never reserve more than 5% capacity for unplanned work. It is inefficient if the Developer's forecast does not take into account all of their capacity.

C. The Sprint Goal becomes more important. It can help the Developers maintain their focus as new Product Backlog items are brought into the Sprint Backlog.

A. Class of service.

B. Swim lanes per Product Backlog item type.

C. Visualization of your Workflow.

D. Work in Progress (WIP) Limits.

A. Professionalism.

B. Openness.

C. Transparency.

D. Courage.

E. Focus.

A. Throughput.

B. Work Item Aging.

C. Work in Progress.

D. Cycle Time.

E. Velocity.

A. Leading indicators.

B. Lagging indicators.