Architect musing: Where do you separate yourself from development team?

I have recently changed the official role in my company where i moved into an Architect role. After spending few days with my new project team, I started to ask where does the role of an Architect start and end and if a team needs an architect in the first place.

Here is what my opinion is:

Architect takes care of:

1. Look at business requirements and convert to technical requirements. Assist the BA team to ensure technical User Stories are created to support n+2 business related User Stories.
2. Know the big picture and be able to think how it can be built over the course of sprints.
3. Identify critical scenarios for team to take care as non-negotiable.
4. Work on tools/methods that can reduce development/testing/troubleshooting time
5. Work on non functional requirements and ensure that they are addressed by team
6. Manage techical debt/architecture debt
7. Implement/suggest patterns for implementation 
8. Be able to troubleshoot bugs
9. Ensure right technology is picked


Dev Lead takes care of:

1. Right skilled folks are part of team and work assignment is appropriate
2. Know if a certain work can fit within sprint
3. Ensure development is as per the provided specification
4. Be able to troubleshoot bugs/issues
5. Ensure team has enough tests to identify any regression issues
6. Ensure that technology is used in best possible way
7. Code is optimized and following agreed standards/practices
8. Team is not overloaded and is motivated
9. Team knows what is to come in current and next 2 sprints