Mainteinance x Evolution x Innovation
In my company we work in Scrum teams (squads as we call here).. So its something from above that we all work in this framework alltough sometimes its no the best option, at least at my opinion... So we have a lot of problems, especially with teams that us the framework only to the mainteinance of the product.So we diveded our epics in Mainteinance (support), Evolution (Bug corrections and technical improvement), and Innovation. I was wondering what is your opinios about using the framework for things other than innovate.
The epics you describe seem more like areas of coherence around which Sprint Goals might be organized. Scrum is useful when meaningful Sprint Goals can be identified and served.
Exactly Ian !!!! Couldn't agree more with you.. We do have problems defining the sprint goals...
So you're saying that we shouldn't try to use the framework, right??
Do you think it’s appropriate to stop using Scrum because it is proving to be difficult? My advice would be to try looking for Sprint Goals in those epics you have identified, as they may provide a suitable coherence.