How do you guys formulate sprint goals when you are working on 3-4 different products? My team is a Client driven team and we support about 3-4 different clients at any given time…INCLUDING production support. Can we have more than one sprint goal?
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do you guys formulate sprint goals when you are working on 3-4 different products? My team is a Client driven team and we support about 3-4 different clients at any given time…INCLUDING production support. Can we have more than one sprint goal?
The short answer is “you don’t”
The basic principle of out-of-the-box Scrum is that the team works on a single product. That’s largely about focus and context switching.
Check out Gloria Mark’s work (for example) on the impact of working on 2+ projects at the same time, but a rough summary is that (a) it will add 20-40% overhead to both projects and (b) it will increase employee stress.
Increased stress isn’t just a fluffy bunny thing; stressed people communicate less well and make more errors, before they burn out and quit.
Still – if that’s your reality, my suggestion would be not to use Scrum, and focus on the Kanban Method instead. You won’t need to worry about Sprint Goals (or indeed when you have enough data estimation) and you will be able to actively track the cycle time (and hence customer facing performance) for each customer.
If you limit Work-in-progress effectively you might also be able to do something about that context switching….