Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Retrospective
|
What should we have done better?- Start
- How to effectively share standup status?
- Know what are our expectations of our Technical Manager?
- Monthly 1-hour meeting with both Sustaining teams
- Not tracking Blocked/Waiting on Reporter times
- Expectations from New Product Manager (Abstract)
- Backlog Grooming → Backlog → Prioritized
- Use "Internal Only" with Jira
- Use Engineering Calendar for Annual Leaves.
- Daily standup
- Stop
- Others
- Know what are our expectations of our Technical Manager?
- Not only technical help but we need other help on the blocked ticket.
- Blocked or Waiting on Reporter
- Follow up in person / Ping individuals on slack
- New Feature help and help setup knowledge share with the team
- Updates from Cambridge +1
- Code Review when needed
- Or redirecting to someone with better context
- Monthly 1-Hour meeting with both Sustaining teams
- Every 1st Monday of the month
- It would be basic knowledge sharing
- One hour session from 6 – 7 pm.
- We can document that meeting for reference
- Not tracking Blocked/Waiting on Reporter times
- Context switching is very difficult for anyone in a team that a ticket.
- We can assume, if some ticket is blocked for ~5 days, it means, its not high enough priority for them.
- Need to think more about this to make it less painful for the dev team.
- Expectations from New Product Manager (Abstract)
- Help us showcase and present our team in Cambridge.
- Know our painful areas with a higher number of bugs (Maybe from the reports) and get in touch with the dev team
- Plan and address hot areas.
- Help develop a healthy environment around Sustaining Team.
- Actual vs Expected Behavior
- Prioritize CAT-3s in the backlog to Prioritize state.
- Find areas our team can work, i.e. find and suggest area which our team take on and improve
- Help develop a good healthy relationship with course teams and Ed services so that have visibility on our processes.
- They feel empowered to respond to tickets
- Backlog Grooming
- Prioritized tickets should be groomed.
- Who would be moving cat-3s to prioritized?
- Use Jira ticket security level to "Internal Only".
- All Jira tickets cloned into EDUCATOR are internal only.
- Verify ticket security during triage.
- If a ticket has sensitive information that should be Internal Only.
- Use Engineering Calendar for Annual Leaves.
- Daily Standup
- English Language
- Standup for the Mavericks.
- On Time
- Social / Ethical Work
- Priority to people who are on foot above all other transportation means.
|
Action items