Know the basic principles of project management

[shaownhasan]

Be transparent : You need to make the reasons behind every decision transparent. Especially, if there are people who are not involved in the decision-making process, it will be difficult to understand, comply with the decision and the reasons behind it.

Estimate and Evaluate
Don't forget that it's not just about implementation, there are more activities to consider, such as requirements engineering , testing and fixing bugs .

If you are placed in an agile project , learn how to estimate and plan properly: The benin email list book "Agile Estimating and Planning" by Mike Cohn provides a clear overview in this area.

Evaluating the “unknown” architecture : As an architect, you should also be able to evaluate the suitability of the architecture for the current or future context. And it is not only about the architecture, but also about how the system is managed because it is closely related to quality.

Balance
There is a price for quality : You need to balance architectural requirements and functional requirements . Over engineering should be avoided.

Conflict management : Software architects often act as bridges between groups with different backgrounds. Different backgrounds can trigger conflict.