The New Approach of TAB
The new approach is introduced to utilize the architect team more efficiently and empowers the technical team members to think about solutions without the architect team's direction. Please find few suggested points below
We aim to move away from handholding and spoon-feeding. Individuals should take ownership of their work by proposing solutions and thinking through challenges. The architect team will provide reviews and guidance as needed.
The architect team will only engage in technical matters following the TAB process and technical support requests. These requests should be self-explanatory and include details of the methods attempted, clearly explained in the request. The architect team expects to understand the exact requirements before getting involved.
It's recommended to minimize unnecessary calls.
The architect team will focus on technical queries and reviews, providing suggestions for process-related issues without taking responsibility for follow-ups or outcomes. The PMO and delivery teams should handle process-related tasks, including planning, unit testing, code reviews, and resource performance.
Technical support requests should be well-documented, clearly outlining the methods tried. Avoid raising requests without any prior findings.
Any requests marked as "Urgent" will be rejected if deemed unnecessary, pending confirmation from Anoop/Sanjay.
This approach is being implemented to enhance the efficiency of the architect team and has already been initiated in several cases. We welcome your feedback and will discuss it.