I've been recently offered a new job as Java Architect, a role that I think I can fit at least under a pure technical point of view.
Nevertheless, I'm worried about that I should take the responsibility of junior developer's technical growth and, most important, I'll have to help project managers to estimate developing time for new projects or changes to be applied to existing projects. And that's something I've never done before. Or, well, I've done dozens of time but always with respect to projects I deeply knew, and taking in account the actual skills of my co-workers, that I know pretty well - I mean I know who's better in writing tests, who can review code, and more or less how much each member of the team will take to perform a task.
Moreover, despite the fact that I'm currently an architect in a small company, I'm afraid to not measure up with the same role in a much more larger reality, where things like tracking project changes, defining all the architecture's pieces, tracking of bugs and issues and so on will presumablyl go through a deep , formal processes I'm not comfortable with.
Could you give me any advice, guys ?
Thanks Jeanne, but at the moment I haven't already accepted. Indeed I've some concerns like the forementioned ones.
Based upon your experience, what are the most important skills any architect should have?