Tony Timbol - How Constraining Boundaries can set you Free from Overcommitting in Agile Development
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
How Constraining Boundaries can set you Free from Overcommitting in Agile Development Agile’s incremental development principle is key to high performance.
Agile teams struggle with incremental development because of the anti-pattern of too large user stories.
Stories range from dense pseudo programming specifications to epic size scope items. How can teams handle both?
While story-splitting techniques abound, teams still struggle with high story escape rates because stories never complete in an iteration.
Are there any other methods to help teams fit scope into short incremental timeboxes?
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.