RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
S.No | Reporter Name | Retro Point | Mitigation plan | Retro Counter | |
---|---|---|---|---|---|
1 | Need to support other team member -- consuming time |
| 2 | ||
2 | | Taking different approach for US by each resource | 1 | ||
3 | Time allocation for Adhoc requests (from community, rdk support team) | Allocate 10% Story points for Adhoc requests | 1 | ||
4 | All should be knowing about all tasks | 1 | |||
5 | Sharing knowledge with meeting on the 1st day of sprint - internal, with screen sharing | 12 | |||
6 | De-prioritized on-going ticket with high priority ticket disturbed the flow |
| 2 | ||
7Positive points:
| 8 | Points to be overcome in upcoming sprint : Q3 blockers - concentrated on RDK-REFPLT-2022-W35 sprint so couldn't put much effort on planned tickets |
| ||
8 | Two-weeks sprint is challenging to complete planned tickets | 3 | |||
9 | Grooming knowledge on RDKB Architecture/components | 4 | |||
10 | One person per ticket approach is followed in RDK-REFPLT-2022-W35 sprint | 1 | |||
Positive points - RDK-REFPLT-2022-W35 sprint : | |||||
1 |
| 3 |