2. Go through program and pitch to internal teams - ideas to improve
3. Attend client meetings and list out client wish list - present to team (set clients expectations you will present to the team in weekly call - not right now)
- if any bugs (not usability issues) but then log in the asana right away with details
Technical side ready
1. Understand requirements (and deadlines)
(when we give the review task - ask people to fill in a form)
2. Write down how you are going to implement/do (more than 4 hrs)*
Especially why something is not 90% if not 99% similar to what we have and you have done
Mihir does not approve automatically whatever the developer says they are going to do
Developer might need training (even basic HTML)
Developer might need to prove they can do by implementing prototype
Developer just not qualified to do it
3. Engage testing team
4. Implement/do (get continuous testing and progress)
5. Review code/document - what you did (in case review task)
6. Upload/test
7. Update asana
8. Notify client
Have all tasks go through triage
New functionality
Usability request
Queries
Urgent tasks
Let answer be by developer (if necessary in coordination with Mishal/Martin)
Make developer realize Mihir is going to review their answers and tasks (even if closed)
Mihir update SOP
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
