| Panel |
|---|
| borderColor | #91c89c |
|---|
| bgColor | #f3f9f4 |
|---|
| What did we do well?- Continue
- Keeping tickets up to date
- Appreciate
|
- Revenue Project Work
- Keeping tickets up to date
- What if we can update the ticket every 2nd / 3rd day?
- Update:
- When we have an update +1
- Blocked:
- Update to the reporter that we are still waiting on XYZ.
- Benefit:
- Farhanah won't be tagged and pinned
- It's a good general practice to keep the ticket updated.
- Khubsurat +1
- No update is a bad update
|
Not only technical help but we need other help on the blocked ticket.Blocked or | Panel |
|---|
| borderColor | #d04437 |
|---|
| bgColor | #fff8f7 |
|---|
| 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 JiraUse Engineering Calendar for Annual Leaves.
- Daily standup
- Stop
- More
- Importance of Giving and receiving feedback
- Others
|
Know what are our expectations of our Technical Manager?Daily Standup - Follow Security Fix Process
- Others
- Schedule and plan for Triage Board.
- Waiting on Reporter
|
Follow up in person / Ping individuals on slackNew Feature help and help setup knowledge share with the teamUpdates from Cambridge +1Code 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. - How to effectively share standup status?
- When we are sharing the status in the channel, what measure we should take that everyone picks up quickly what are you doing?
- General Rule:
- Ticket Link / Number – Working on this
- Ticket Number + Ticket Title
- Jira Integration with Standup Room +3
- Importance of Giving and receiving feedback
- Listen Tool: Souce is Retro.
- Start Using it.
- Immediate Feedback.
- Direct Feedback
- Specific Feedback
- Once In a month. (2 Retros) +3
- Reminder inside Listen Tool:
- A reminder in Standup channel.
- Daily Standup +2
- English Language
- Standup for the Mavericks.
- On Time
- Social / Ethical Work
- Actions:
- Priority to people who are on foot above all other transportation means.
- Rabia: -1
- Asad: 1
- Dawoud: 1
- Awais: 1 + (-10):
|