Lotus

Sprint Report – Sprint 2022Q1-4

SPRINT REPORT OUTLINES

1. CURRENT SPRINT RECAP

2. PRODUCTIVITY METRICS
3. QUALITY METRICS
4. PRODUCTION SUPPORT (ISSUES/OUTAGES)
5. CONTINOUS IMPROVEMENT / INNOVATION
 1. CURRENT SPRINT RECAP
LOGISTICS

Team Capacity: All member of the team has fulfilled at least 85% of their planned capacity.

Team Velocity: Team planned 33 user story points, and burned 34 user story points.
 1. CURRENT SPRINT RECAP
LOGISTICS

Iteration Goals:
Delivered:
• Deploy production for Client DB: US730923, US704578, US749033, US759028
• Complete the technical design of Integration of Carrier DB and Salesforce
• Supporting SFDC Integration Testing for Client DB
• Change UPN for 280 accounts: Element
• Continue on support production & handle Pager Duty incidents in production
 1. CURRENT SPRINT RECAP
LOGISTICS

Risks/issues/dependencies outside the team

• Risks: N/A
• Issues: Team was not able to reach out RMIS (contacted but no response yet). So some works are pending such as get list columns in Carrier DB that not mapped to
RMIS, verify ADO defect #4630 RMIS - Updated W9s are not sent to Carrier DB.
• Dependencies: Contacted RMIS but no response yet in the last sprint.
 2. PRODUCTIVITY METRICS
LOGISTICS

Committed vs Delivered:
• Iteration 2021Q4-IP, there is a gap between Committed & Delivered (10 vs 7) because 2 user stories were accepted after the last day of
the sprint, 1 user story was carried over the next sprint.
• The percentage of Unplanned is quite high because the backlog health at the beginning of the sprint is not good. Team keeps
brainstorming each sprint to have more idea about the app improvement, and also work with RTC to have more work.
• For the last sprint – 2022Q1-4, team delivered all committed user stories.
 2. PRODUCTIVITY METRICS
LOGISTICS

Predictability:
• Team is trying to make the Cycle Time under 3.0 days. The average of Cycle time is 2.8 days now, which is good.
• The Predictability metric of throughput for the last 6 iterations, it is 78%, the team will continue to improve this metric by increase the Throughput metric.
• Team is trying to increase the Throughput to above 12 user stories per iteration. The average is 11.3 user stories per iteration now.
 2. PRODUCTIVITY METRICS
LOGISTICS

Velocity:
• Lotus is the consolidated team from Americano & Macchiato. The Rally board was merged from Americano into Macchiato, then the name changed to Lotus. This
make the velocity from iteration 2021Q4-1 to 2021Q4-5 in the below chart is the summarized velocity of 2 teams. So the trending line is decreasing.
• Iteration 2022Q1-2, team has long days holiday, so the velocity was low in this iteration. This is impacted to the overall trending line.
• Team is planning the target velocity for 2022 Q1 is 33 user story points, and try to increase the velocity for the up coming time.
• Velocity for the last iteration – 2022Q1-4 is 34 user story points (planned 33 user story points).
 3. QUALITY METRICS
LOGISTICS

Unit Test Coverage:

• Code coverage of Carrier DB is 96% (above
80%) which is good.
• Code coverage of Client DB is 82%, (above
80%), improved from the previous sprint which
is 79%. This sprint is quite good but team will
continue improving in the next sprint by
updating the Unit Test.
Carrier DB

Client DB
 3. QUALITY METRICS
LOGISTICS

Automation Coverage Rate:

• Automation Coverage Rate is 76.6%, below 80%, which is not good. Converted 3 test cases from Manual to Automation in this sprint.
• Team is continuing improvement by converting more manual test cases to automation. However, many test cases cannot be automated because
they are dependent on other systems, and we need other parties to verify the result manually.
 3. QUALITY METRICS
LOGISTICS

Defects:
• There are 2 remaining defects on Production environment.
• Team deployed the fix on 24-Feb-2022 for DE199545. Waiting for
DHL team to verify on their side, but they didn’t response yet.
• With the DE199503, team fixed it and is waiting for RMIS to verify.
Reached out to RMIS twice but they didn’t response yet.
• All defect on Staging is killed

Defects on Production

Defects on Staging
 4. PRODUCTION SUPPORT (ISSUES/OUTAGES)
LOGISTICS
Roll back:
• 0 roll back in this sprint

Pager Duty SLA:

• 2 incidents in this sprint
• Maximum acknowledge time is 15 seconds
• Maximum resolution time is 57 minutes

SNOW Open Tickets

• 0 ticket in this sprint
 5. CONTINUOUS IMPROVEMENT / INNOVATION
LOGISTICS
Went well
• Team kept on track the release
plan of User Stories
• Production deployment
successfully for Client DB
• Good learning spirit, team gets 2
Azure certifications (AI-900, DP-
900) in this sprint
• Improved pager duty response
• Strong responsiveness and
engagement
To Improve
• Improve grooming activities
before the sprint started
• More new works to implement
Actions
• Keep weekly trending reviews of
Pager Duty incidents
• Keep focus on Pager Duty
response time
• Keep learning spirit, prepare for
AWS, Azure certification exam
• Standardize production
deployment process then
optimize
Lotus
Sprint Planning – Sprint 2022Q1-5
 1. CURRENT SPRINT RECAP
LOGISTICS

Team Capacity:

Team Velocity: Team is planning 33 user story points for this iteration. Loaded 34 user story points – 103%
 NEXT SPRINT PLAN
LOGISTICS

Iteration Goals:
• Fixed the Production Data for Client DB
• Client DB enhancement: Remove MESSAGE_STATUS_LOG to improve performance
• Carrier DB enhancement: Create Job to remove data in Job Status table when needed to improve performance & lighter process to remove those data
• Continue on support production & handle Pager Duty incidents in production
• Supporting SFDC Integration Testing

Risks/issues/dependencies outside the team

• Risks: N/A
• Issues: Team was not able to contact RMIS to verify ADO defect #4630 RMIS - Updated W9s are not sent to Carrier DB. Annette also reached out, waiting for reply.
• Dependencies: Contacted RMIS but no response yet
LOGISTICS

Thank you and looking for your feedback!