summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: e6e04a0)
raw | patch | inline | side by side (parent: e6e04a0)
author | Chase Maupin <chase.maupin@ti.com> | |
Fri, 12 Apr 2013 15:02:02 +0000 (10:02 -0500) | ||
committer | Felipe Balbi <balbi@ti.com> | |
Fri, 12 Apr 2013 15:13:31 +0000 (18:13 +0300) |
* Added an additional benefit of two week sprints to address a
common concern of how can we react in a timely fashion to
customer support escalations without modifying sprints.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
common concern of how can we react in a timely fashion to
customer support escalations without modifying sprints.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
the-sprint.tex | patch | blob | history |
diff --git a/the-sprint.tex b/the-sprint.tex
index 4654cb1d3717570f6a19e302124f6e5062d9ea31..5387ee19cd858d3300f669beb83135185d49c972 100644 (file)
--- a/the-sprint.tex
+++ b/the-sprint.tex
Due to item \ref{item:short-amount-of-time}, risk management becomes easy. If
it turns out a particular sprint isn't successful, we're not loosing a
considerable amount of work -- only 2 weeks -- and we can easily fix that on
-the next sprint.
+the next sprint. A 2 week duration also allows a reasonable response time
+to changing priorities in the backlog such as customer issues.
\paragraph{}
Item \ref{item:not-too-short}, on the other hand, makes it easier to see