Multiple sprint goals
Hello. Our team has a lot of responsibilities. One big product, a few functionalities with high priority, SD a few other "little" products which are very, very simmilar to the big one. One of the reason we do not have one product is old technology that does not allow us to combine them(and costs of transition naturally). It is our situation and it is not a problem for us. The problem is to define one Sprint Goal that give us focus and cosistency. It is impossible to have ONE sprint goal because we do not have enough knowledge to create enough tasks focused on one problem. Generally we are higly productive and work together as a team with every problem we face. The problem here is just to set one sprint goal. Reasonably is to create one goal for every product/functionality but I would like to ask you for opinion.
Best Regards
Generally we are higly productive and work together as a team with every problem we face
Amazing! It sounds like you have a well-formed team.
I wonder about the Product situation though.
A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.
It seems that you may not have a product with a clear boundary. Without this, I imagine it is also challenging to establish a single Product Goal. This is going to have a ripple effect which you are feeling with your Sprint Goal challenge.
An Increment is a concrete stepping stone toward the Product Goal. Sprint Goals and associated Increments developed during each Sprint align to the Product Goal to support commitment and focus for the Product.
Right now it seems like attempting to bend Scrum around an existing team structure instead of having a team or teams aligned to a Product or Products.
Is there an opportunity to align around Product instead? Could focus be given to specific Products with specific Product Owners (1 Product Owner to 1 Product)?
Have other frameworks or management methods been explored for this work?
It is our situation and it is not a problem for us. The problem is to define one Sprint Goal that give us focus and cosistency.
What are the consequences of the lack of focus and consistency you are presumably experiencing? Are they transparent and visible to all?
It is impossible to have ONE sprint goal because we do not have enough knowledge to create enough tasks focused on one problem.
Then that's the problem you need to solve. The idea of having a single Sprint Goal -- which would provide focus and consistency -- isn't the problem. It's just causing the real problem -- a lack of focus and consistency -- to be exposed. The question is: do you deal with this issue or try to find some way of covering it up?