Managing Experts
This page will store the guidelines for managing experts (e.g. designers, developers, QAs).
Designer on Extended Leave: If your designer will be out for a long period of time, instead
•
of off-boarding the previous designer and onboarding a new designer, then ask your
designer to recommend someone else from their company and the new designer can log in
through the previous designer's credentials to sub in while the previous designer is out
Information exchange between client and designers: Translate what the customers are
•
saying in the best way possible and reiterate them over the period. Communicate high level
messages on Mattermost with actions. Capture the information with relevant spec
documents within user stories, acceptance criteria etc.
Meeting cadence: Plan to meet with your experts in at least twice weekly meetings.
•
Suggestion: meeting once before your client meeting to get an update on status and once
after the client meeting to provide your experts feedback from the client.
During meetings: Begin with status updates and discussions, then prioritise the next
•
efforts, ensure experts' time is being fully utilised. Be explicit about what work needs to done
before the next meeting, (tip: use an action items list with priorities).
Collaborative efforts: Conduct regular checkins and status updates on where we are
•
and how to proceed forward. Host brainstorming sessions and question ideas to
produce the best products.
Rework: If your experts are not providing what you were expecting, it might be useful to get
•
to the root of the problem to understand why there is a discrepancy between expectations
and delivered products.
Escalations: If you are having issues with your experts that cannot be resolved through
•
conversations, adjusting approaches, and speaking with your manager, use the Capacity Esc
alation Form to submit the issue to the capacity network team and they will help you handle
the issue.
Hours:
•
don't assign more than 8-16 hours on a subtask (can be 24 for more complex features)
•
rule of thumb: divide expert estimates by 3 and give them that
•
Reasons experts will be docked hours:
•
IDE Bypass Offset Cost
•
Bugs Offset Cost
•
Frontend Bypass Cost
•
No MR Cost
•
Stories Not Delivered Cost
•
DLS Bypass Cost
•
Removed IDE Monitoring Cost
•
Commits w/o Story ID Cost
•
