scrum

Name: scrum
Author: krzysztofsurdy

41installs1forks

How to install scrum?

krzysztofsurdy/code-virtuoso/scrum

$npx -y skills add krzysztofsurdy/code-virtuoso --skill scrum

Installs into the current project.

Summary

Scrum framework fundamentals, sprint goal writing, and agile ceremony facilitation. Use when the user asks to plan a sprint, write sprint goals, facilitate daily scrums, run sprint reviews or retrospectives, define scrum roles, manage the product backlog, or apply agile estimatio

Files · 1

View on GitHub

SKILL.md

1	# Scrum
2
3	A lightweight framework for delivering complex products through iterative, incremental work. Scrum is founded on empiricism (knowledge from experience) and lean thinking (reduce waste, focus on essentials). Teams work in fixed-length iterations called Sprints, inspecting and adapting continuously.
4
5	## Three Pillars
6
7	\| Pillar \| Meaning \|
8	\|---\|---\|
9	\| Transparency \| The process and work must be visible to those performing and receiving the work \|
10	\| Inspection \| Scrum artifacts and progress must be inspected frequently to detect problems \|
11	\| Adaptation \| When inspection reveals deviation, adjust immediately \|
12
13	## Five Values
14
15	Commitment, Focus, Openness, Respect, Courage. The Scrum Team commits to achieving goals, focuses on Sprint work, is open about challenges, respects each other as capable people, and has courage to do the right thing.
16
17	---
18
19	## Sprint Goal
20
21	The Sprint Goal is the single objective for the Sprint. It is the commitment of the Sprint Backlog. The Sprint Goal provides focus and coherence, encouraging the Scrum Team to work together rather than on separate initiatives.
22
23	### Quick Template (Focus / Impact / Confirmation)
24
25	```
26	Our focus is on [outcome].
27	We believe it delivers [impact] to [stakeholder/customer].
28	This will be confirmed when [measurable event happens].
29	```
30
31	Example: "Our focus is on sending a basic notification email containing a report link. We believe it delivers confidence to our finance team. This will be confirmed when we have an email in an inbox with a working link."
32
33	### SMART Criteria
34
35	\| Criterion \| Applied to Sprint Goals \|
36	\|---\|---\|
37	\| Specific \| Define exactly what the team will achieve, not a vague direction \|
38	\| Measurable \| Include a way to confirm completion objectively \|
39	\| Achievable \| The team can realistically deliver within the Sprint timebox \|
40	\| Relevant \| Connects to the Product Goal and delivers stakeholder value \|
41	\| Time-bound \| Bounded by the Sprint duration \|
42
43	### Anti-Patterns
44
45	\| Anti-Pattern \| Problem \| Fix \|
46	\|---\|---\|---\|
47	\| Task list disguised as goal \| "Complete stories #101, #102, #103" provides no strategic focus \| State the outcome those stories achieve \|
48	\| Vague aspiration \| "Improve the system" gives no direction or measurable outcome \| Be specific: what improves, for whom, how will you know \|
49	\| Multiple unrelated objectives \| "Build auth AND redesign dashboard" splits focus \| Pick one objective; if truly independent, they belong in separate sprints \|
50	\| Dictated by PO alone \| Team has no ownership or buy-in \| Craft the goal collaboratively during Sprint Planning \|
51	\| Never referenced after planning \| Goal becomes forgotten wallpaper \| Reference the goal daily in the Daily Scrum \|
52	\| Too ambitious \| Team cannot deliver, loses motivation \| Base on actual velocity and capacity \|
53
54	See [Sprint Goals Reference](references/sprint-goals.md) for 5 complete templates with examples and the FOCUS evaluation checklist.
55
56	---
57
58	## Scrum Events
59
60	All events are timeboxed. Shorter Sprints use proportionally shorter event timeboxes. Every event is an opportunity to inspect and adapt.
61
62	\| Event \| Timebox (1-month Sprint) \| Purpose \| Key Output \|
63	\|---\|---\|---\|---\|
64	\| Sprint \| Max 1 month \| Container for all work and events \| Usable Increment \|
65	\| Sprint Planning \| Max 8 hours \| Define the Sprint Goal and Sprint Backlog \| Sprint Goal + selected backlog items + delivery plan \|
66	\| Daily Scrum \| 15 minutes \| Inspect progress toward Sprint Goal \| Actionable plan for next 24 hours \|
67	\| Sprint Review \| Max 4 hours \| Inspect the Increment and adapt the Product Backlog \| Feedback, updated Product Backlog \|
68	\| Sprint Retrospective \| Max 3 hours \| Inspect the team's process and plan improvements \| Improvement actions for next Sprint \|
69
70	### Sprint Planning: Three Topics
71
72	1. Why is this Sprint valuable? - Product Owner proposes how to increase value; team defines Sprint Goal
73	2. What can be done this Sprint? - Developers select Product Backlog items based on capacity and velocity
74	3. How will the chosen work get done? - Developers decompose items into tasks (typically one day or less)
75
76	See [Scrum Events Reference](references/scrum-events.md) for detailed facilitation guidance, formats, and tips.
77
78	---
79
80	## Scrum Roles
81
82	\| Role \| Accountability \| Key Responsibilities \|
83	\|---\|---\|---\|
84	\| Scrum Master \| Scrum framework effectiveness \| Facilitates events, removes impediments, coaches team and orga

People who liked this also viewed

6 picks

Type

scrum

41installs1forks

View on GitHub

How to install scrum?

krzysztofsurdy/code-virtuoso/scrum

$npx -y skills add krzysztofsurdy/code-virtuoso --skill scrum

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Scrum
2
3	A lightweight framework for delivering complex products through iterative, incremental work. Scrum is founded on empiricism (knowledge from experience) and lean thinking (reduce waste, focus on essentials). Teams work in fixed-length iterations called Sprints, inspecting and adapting continuously.
4
5	## Three Pillars
6
7	\| Pillar \| Meaning \|
8	\|---\|---\|
9	\| Transparency \| The process and work must be visible to those performing and receiving the work \|
10	\| Inspection \| Scrum artifacts and progress must be inspected frequently to detect problems \|
11	\| Adaptation \| When inspection reveals deviation, adjust immediately \|
12
13	## Five Values
14
15	Commitment, Focus, Openness, Respect, Courage. The Scrum Team commits to achieving goals, focuses on Sprint work, is open about challenges, respects each other as capable people, and has courage to do the right thing.
16
17	---
18
19	## Sprint Goal
20
21	The Sprint Goal is the single objective for the Sprint. It is the commitment of the Sprint Backlog. The Sprint Goal provides focus and coherence, encouraging the Scrum Team to work together rather than on separate initiatives.
22
23	### Quick Template (Focus / Impact / Confirmation)
24
25	```
26	Our focus is on [outcome].
27	We believe it delivers [impact] to [stakeholder/customer].
28	This will be confirmed when [measurable event happens].
29	```
30
31	Example: "Our focus is on sending a basic notification email containing a report link. We believe it delivers confidence to our finance team. This will be confirmed when we have an email in an inbox with a working link."
32
33	### SMART Criteria
34
35	\| Criterion \| Applied to Sprint Goals \|
36	\|---\|---\|
37	\| Specific \| Define exactly what the team will achieve, not a vague direction \|
38	\| Measurable \| Include a way to confirm completion objectively \|
39	\| Achievable \| The team can realistically deliver within the Sprint timebox \|
40	\| Relevant \| Connects to the Product Goal and delivers stakeholder value \|
41	\| Time-bound \| Bounded by the Sprint duration \|
42
43	### Anti-Patterns
44
45	\| Anti-Pattern \| Problem \| Fix \|
46	\|---\|---\|---\|
47	\| Task list disguised as goal \| "Complete stories #101, #102, #103" provides no strategic focus \| State the outcome those stories achieve \|
48	\| Vague aspiration \| "Improve the system" gives no direction or measurable outcome \| Be specific: what improves, for whom, how will you know \|
49	\| Multiple unrelated objectives \| "Build auth AND redesign dashboard" splits focus \| Pick one objective; if truly independent, they belong in separate sprints \|
50	\| Dictated by PO alone \| Team has no ownership or buy-in \| Craft the goal collaboratively during Sprint Planning \|
51	\| Never referenced after planning \| Goal becomes forgotten wallpaper \| Reference the goal daily in the Daily Scrum \|
52	\| Too ambitious \| Team cannot deliver, loses motivation \| Base on actual velocity and capacity \|
53
54	See [Sprint Goals Reference](references/sprint-goals.md) for 5 complete templates with examples and the FOCUS evaluation checklist.
55
56	---
57
58	## Scrum Events
59
60	All events are timeboxed. Shorter Sprints use proportionally shorter event timeboxes. Every event is an opportunity to inspect and adapt.
61
62	\| Event \| Timebox (1-month Sprint) \| Purpose \| Key Output \|
63	\|---\|---\|---\|---\|
64	\| Sprint \| Max 1 month \| Container for all work and events \| Usable Increment \|
65	\| Sprint Planning \| Max 8 hours \| Define the Sprint Goal and Sprint Backlog \| Sprint Goal + selected backlog items + delivery plan \|
66	\| Daily Scrum \| 15 minutes \| Inspect progress toward Sprint Goal \| Actionable plan for next 24 hours \|
67	\| Sprint Review \| Max 4 hours \| Inspect the Increment and adapt the Product Backlog \| Feedback, updated Product Backlog \|
68	\| Sprint Retrospective \| Max 3 hours \| Inspect the team's process and plan improvements \| Improvement actions for next Sprint \|
69
70	### Sprint Planning: Three Topics
71
72	1. Why is this Sprint valuable? - Product Owner proposes how to increase value; team defines Sprint Goal
73	2. What can be done this Sprint? - Developers select Product Backlog items based on capacity and velocity
74	3. How will the chosen work get done? - Developers decompose items into tasks (typically one day or less)
75
76	See [Scrum Events Reference](references/scrum-events.md) for detailed facilitation guidance, formats, and tips.
77
78	---
79
80	## Scrum Roles
81
82	\| Role \| Accountability \| Key Responsibilities \|
83	\|---\|---\|---\|
84	\| Scrum Master \| Scrum framework effectiveness \| Facilitates events, removes impediments, coaches team and orga

People who liked this also viewed

6 picks

Type