Versions Compared

Old Version 4

changes.mady.by.user Manigandan Gopalakrishnan

Saved on

compared with

New Version 5

changes.mady.by.user Z-Kaviya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Retro Table:

S.NoReporter NameRetro PointMitigation planRetro Counter
1
Need to support other team member --
comsuming
consuming time
  • Lend support during your off time
  • Provide only Anydesk-VPN access
  • We can have time slot among us to address queries from other team
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 requests1
4
All should be knowing about all tasks
1
5
Sharing knowledge with meeting
at end of week
on the 1st day of sprint - internal, with screen sharing
1
6
De-
priotized
prioritized on-going ticket with high priority ticket disturbed the flow
  • Allocate 10% Story points for Adhoc requests
  • Comcast person can be PO
2
7
Positive points:
  • Could able to complete few Q3 blocker issues
  • Team support/ co-ordination was good
  • Task Analysis- we can able to grasp knowledge on code flow


8
Points to be overcome in upcoming sprint :
  • One person per ticket approach is followed in last sprint
  • Working on Q3 blocker - concentrated on last sprint so couldn't put much effort on planned tickets
  • Two-weeks sprint is challenging to complete planned tickets
  • Grooming knowledge on RDKB Architecture/components
  • Buffer time for priority tasks
  • Q3 validation support- create ticket and log effort

9