Scaling Scrum: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Scaling the [[Scrum Framework]] for a large program of work or across an enterprise is really about working with multiple small teams rather than working with one single big team. | Scaling the [[Scrum Framework]] for a large program of work or across an enterprise is really about working with multiple small teams rather than working with one single big team. | ||
[[File: | [[File:Scaling_scrum2.jpg|500px|Scaling Scrum]] | ||
==Limitation of Team Size== | ==Limitation of Team Size== | ||
Team size can be represented as a node graph, in that, the number of communications paths x: | Team size can be represented as a node graph, in that, the number of communications paths x: | ||
<math>x=\frac{(n-1}{2}</math> | <math>x=\frac{(n-1}{2}</math> | ||
Revision as of 00:47, 26 November 2018
Scaling the Scrum Framework for a large program of work or across an enterprise is really about working with multiple small teams rather than working with one single big team.
Limitation of Team Size
Team size can be represented as a node graph, in that, the number of communications paths x: <math>x=\frac{(n-1}{2}</math>