Chitranshu has helped with work planning,tracking sheet that has helped to track the team and work usage. Can be shared with other team folks.
Rotation of people within team gives and opportunity to work on other technologies, reduce dependency during their unavailable times and team members are happy with that
Start of the sprint, stories are marked 'Selected for Development' by mobile team and has been helpful to track any scope change.
use of slack bot for standup has been helpful to track team's (content framework) updates
Stories that had complete clarity only was taken up by KP team and any stories that came in between and needed more clarity was moved out to next sprint. Was communicated to PMs earlier on through Jira ticket comments
Status updates on Jira must happen more regularly
The single scrum board has helped else creating individual filters was hard
Deployment script post code freeze must be available DevOps instead of creating just before PROD deployment as this led to some of the tasks missed (forgotten)
Retrospective if had earlier would be beneficial as you tend to remember points then
Process changes related to bugs from QA, Implementation team must be prioritised by PMs that needs to be resolved
Communication on process changes must be discussed by TMs
Jira simplification must be done especially status change workflows
Sprint 3 code ended up in pre-prod. Find the root cause and take action accordingly
Timeboxing developers with release timeline or calendar without buffers is hampering creativity and productivity of team folks and there should be time given to nurture them as these ideas will flow into features/implementation that they are building. Ex: Google has one day a week as creativity day
Teams must be trusted as team members are working hard on whatever has been assigned
Low level team members are not accountable and they rely upon managers for every thing
Developers must be able to analyse and understand his/her change how does it fits in the big picture and be responsible for end to end delivery
Feedback to developers must be given , that is not the culture (Top-Down) here and this is adding burden on the Tech Mgrs as they are held accountable.
Bottom up culture could be good
Showcase is preferable to be done between PMs and team members for a given epic and relevant stakeholders
Timeline/Release delays must be communicated to all the stakeholders which is currently not happening
Release delays must have scope reviewed and published if the release has to happen on the given date
Go/No-Go Calls for pre-prod with TMs, PMs must be made for a PROD release
When number of issues are high, there has to be a meeting with all stakeholders to arrive at a decision on what will be taken up and get an ETA for the same
During the planning week QA is busy with stage validation which leaves with no time for participation in the planning