APPortunity 2022 Global Conference
June 1-3, 2022 | Virtual
Project Management Central
|
Please login or join to subscribe to this thread
|
||||
|
||||
We had over eight Scrum teams, which we divided along product lines. That created a set of silos that stretched our Scrum of Scrums. It's hard to say if we would avoided the silos if we would have split the teams along epics.
...
1 reply by Kiron Bondale
May 13, 2022 3:38 PM
Kiron Bondale
...
Were the products interrelated such that one epic spanned multiple products?
Kiron May 13, 2022 12:29 PM
Replying to Stéphane Parent
...
We had over eight Scrum teams, which we divided along product lines. That created a set of silos that stretched our Scrum of Scrums. It's hard to say if we would avoided the silos if we would have split the teams along epics.
Kiron ...
1 reply by Stéphane Parent
May 13, 2022 6:10 PM
Stéphane Parent
...
Most of the epics spanned multiple Scrum teams, Kiron.
We had a client-facing application feeding into an internal benefits request management system which, in turn, fed the separate payment system. On top of that we had other products that queried and manipulated the same data. Because each product had its own technology stack, it meant little cross-training outside of a given Scrum team but a lot of back and forth to ensure features were appropriately carried through all the stacks. May 13, 2022 3:38 PM
Replying to Kiron Bondale
...
Were the products interrelated such that one epic spanned multiple products?
Kiron We had a client-facing application feeding into an internal benefits request management system which, in turn, fed the separate payment system. On top of that we had other products that queried and manipulated the same data. Because each product had its own technology stack, it meant little cross-training outside of a given Scrum team but a lot of back and forth to ensure features were appropriately carried through all the stacks. ...
1 reply by Kiron Bondale
May 14, 2022 9:17 AM
Kiron Bondale
...
Very interesting - thanks for the clarification, Stephane! Given this, were the epics more than just "really big user stories" as they sound like they might have been used to represent whole subsystems?
Kiron
Our team likes to live in their own comfort zones and do well completing tasks using skills they enjoy and are good at. This seems to work well for most projects we are involved in.
May 13, 2022 6:10 PM
Replying to Stéphane Parent
...
Most of the epics spanned multiple Scrum teams, Kiron.
We had a client-facing application feeding into an internal benefits request management system which, in turn, fed the separate payment system. On top of that we had other products that queried and manipulated the same data. Because each product had its own technology stack, it meant little cross-training outside of a given Scrum team but a lot of back and forth to ensure features were appropriately carried through all the stacks. Kiron ...
1 reply by Stéphane Parent
May 14, 2022 10:02 AM
Stéphane Parent
...
One epic for a specific client benefit would cover the capture of the client request, the processing of the request and the delivery of the benefit.
Such epics crossed many products and services. May 14, 2022 9:17 AM
Replying to Kiron Bondale
...
Very interesting - thanks for the clarification, Stephane! Given this, were the epics more than just "really big user stories" as they sound like they might have been used to represent whole subsystems?
Kiron Such epics crossed many products and services. |
||||
Please login or join to reply
ADVERTISEMENTS
|
"One of the symptoms of approaching nervous breakdown is the belief that one's work is terribly important." - Bertrand Russell |