Вы находитесь на странице: 1из 3

Mehran (4.

5)
SunShine: Guido (for quick ramp-up), Inese (for analysis), Preethi, Vikas (quick
ramp-up)
Improvement: Need to pickup more stories and thereby velocity as we have some sl
ack time after delivering the story
Jan Willem (4)
Sunshine: Preethi (for testing with Reviva)
Improvement: We should challenge ourselves. Comeup with ideas.
What went well: We are working more closely now.
Dangers: We will be going live so need to focus on quality.
Lenneart (3.5)
Sunshine: Team for delivering the stories on time especially to Jan, Guido and S
yed
Improvement: Clear Description should be added to tasks
What went well:
Danger:
Sudheer (3)
Sunshine:
What went well: Sprint went fine including demo
Sunshine: Preethi and Lenneart for testing with Reviv and Demo. Inese for taking
the order type story. Yathin for analysing pipeline usage.
Improvement:
Danger:
Inese (3.5)
What went well:
Improvement: Planning should be improved. we need to balance it so that there ar
e just enough stories to keep developers on their toes. Release automation is no
t foolproof. More testing should be done for NL core stories.
Danger: We are refactoring SD2 when we are about to go live.
What went well: Test automation is improved.
Sunshine:
Kaspars(3)
SunShine:
Improvement: VDI issues need to be sorted out. Release process is not foolproof.
Release notes should be read carefully.
What went well:
Dangers Ahead: No testers for core stories.
Preethi(3.5)
SunShine: No sunshine
Improvement: Coordination with other teams was not so good. DB space issue on th
e day of demo was not acceptable. Refresh of MSISDN is still an issue. Testing f
or core NL is black box. Test case and test data creation is difficult.
What went well: Very descent and happy sprint. Reviva testing went well. Busines
s Demo was success. Stories are getting delivered to INT faster. Yathin's analys
is was very nice.
Dangers Ahead:

Guido (4)
SunShine:
Improvement: Release automation not working. Need improvement. MSISDN swap story
cacellation was not good. Skype call quality should be improved.
What went well: Stories were moved to INT quickly and testing was performed on t
ime. Green Hat presentation was nice.
Dangers Ahead:
Dmitrijs(4)
SunShine: Mehran for helping with stubs
Improvement: Task descriptions was left empty in the sub tasks. Proper previlage
s should be provided. VDI issues.
What went well: SAT access was given which helped.
Dangers Ahead:
Aleksandars ()
SunShine:
Improvement:
What went well:
Dangers Ahead:
Vikas (3.5)
SunShine: Team
Improvement:
What went well: Descent sprint
Dangers Ahead:
Pramod (4.2)
SunShine: Team - Syed and Yathin especially.
Improvement:
What went well: Technical analysis done ahead of sprint is good. Green hat demo
was nice.
Dangers Ahead:
Yathin (3)
SunShine: Inese for analysing the story.
Improvement: Analysis stories were done without considering the effort so it red
uced the velocity. Team should be aware of the initiatives going on so that ever
yone is on board. Team should be involved in Admin activities.
What went well:
Dangers Ahead:
Syed (4)
SunShine: Vikas for the GreenHat demo.
Improvement: Need to take up challenging tasks
What went well: Sprint went well. Stories were well analyzed and delivered on ti
me.
Dangers Ahead: We are trying to refactor SD2 at a time when we are going live.
Action items:
1) Have a grooming session to understand regression test for NL Core stories.

2) Check how knowledge can be shared with

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++
Retro Point 15S03
----------------Pramod : Bug Fixing is delayed as there are issues in DEV MWS(Button Disabled in
Permissions Management)

Вам также может понравиться