Difference between revisions of "Scrum jumpstart"

Latest revision as of 19:24, 18 May 2013

To jumpstart scrum, use:

stable team to sustain maximum results of human assets.
yesterday’s weather to successfully pull product backlog items into a sprint and get them done.
daily clean code to get defect free at the end of the sprint.
first things first to get the right stuff done.
start what you finish and finish what you start to get things done.
andon cord to deal with emergencies.
boom buffer to deal with interruptions during the sprint.
scrumming the scrum to obtain a sustainable unfair competitive advantage.
happiness index to cultivate hyperperforming teams and organizations that excel and exceed goals while having fun.
teams that finish early accelerate faster to get hyperproductive.

Joined at the hip with scrum shock therapy.

Fuse with a healthy product jumpstart.

@@ Line 1: / Line 1: @@
 To jumpstart {{p|scrum}}, use:
-#{{p|stable teams}} to get started.
+#{{usage|stable team}}.
-#{{p|yesterday’s weather}} to successfully pull {{p|product backlog items}} into a {{p|sprint}}.
+#{{usage|yesterday’s weather}}.
-#{{p|daily clean code}} to get defect free at the end of the {{p|sprint}}.
+#{{usage|daily clean code}}.
-#{{p|first things first}} to get stuff done.
+#{{usage|first things first}}.
-#{{p|start what you finish and finish what you start}} to really get things done.
+#{{usage|start what you finish and finish what you start}}.
-#{{p|andon cord}} to deal with emergencies.
+#{{usage|andon cord}}.
-#{{p|boom buffer}} to deal with interruptions during the {{p|sprint}}.
+#{{usage|boom buffer}}.
-#{{p|scrumming the scrum}} to ensure you continuously improve.
+#{{usage|scrumming the scrum}}.
-#{{p|happiness index}} to get teams to have fun while accelerating.
+#{{usage|happiness index}}.
-#{{p|teams that finish early accelerate faster}} to get hyperproductive.
+#{{usage|teams that finish early accelerate faster}}.
 Joined at the hip with {{p|scrum shock therapy}}.