1. I think it’s a good idea to look at the Team Learning Outcomes score (11.6 out of 15) as one that still needs improvement. I may even update the assessment to cover more ground in the learning area. I believe most teams don’t do as well as they seem to score.
2. Don’t focus too much on velocity – yes, it should be somewhat consistent, but it can also vary for many reasons beyond team maturity. You might want to (if you haven’t already), bring your concern to the team and see what they have to say about it.
3. Try setting a WIP limit at Sprint Planning to 1 or 2. Then, the team has to work together to get stuff done. Management priorities are important, but they are handled in the Product Backlog, not in the Sprint.
1. I think it’s a good idea to look at the Team Learning Outcomes score (11.6 out of 15) as one that still needs improvement. I may even update the assessment to cover more ground in the learning area. I believe most teams don’t do as well as they seem to score.
2. Don’t focus too much on velocity – yes, it should be somewhat consistent, but it can also vary for many reasons beyond team maturity. You might want to (if you haven’t already), bring your concern to the team and see what they have to say about it.
3. Try setting a WIP limit at Sprint Planning to 1 or 2. Then, the team has to work together to get stuff done. Management priorities are important, but they are handled in the Product Backlog, not in the Sprint.
Looks good. Thanks!!!