Dec 17, 2019 6:05 PM
Replying to Deepesh Rammoorthy
...
I think "George Freeman" summarized his view in a different thread quite beautifully
The essence is that you must have a good understanding of the architectural pieces . A high level understanding of how your technical pieces of the solution hang together.
You should be able to understand the technical landscape, the product and solution road-map, the business case and how the solution caters to the vision and problem statement and be able to translate the "tech speak" from your delivery team to "non tech speak" to your stakeholders.
The best approach is to be a Servant leader and let your technical lead / Solution Architect do the run around with the best approach to implement the solution , while you manage the other important aspects of the project like Risk, budget, communication , stakeholder engagement , scope and schedule.
Be the enabler and remove road-blocks from your team's way and let them decide the optimum approach as long as they align to Scope and Schedule as agreed with you.
Encourage prompt escalation to yourself and be approachable at all times.
