I see in Agile world there are 3 defined roles exist:
1) Product Owner (PO)
2) Scrum Master (SM)
3) Development Team (DT)
But, are they enough to develop great software?
I see, moving from water fall model, Agile misses out below roles in a team:
1) Team Lead
2) Software Architect
3) Manager
In Agile world, we don't have any such role called Team Lead. Ok what was the typical duties of TL?
1) Planning a project
2) Recruiting resources ie Interviews
3) Reviewing team's work
4) Interacting with external teams
5) Project Status update to stake holders / customer
6) Giving feedback about team member performance
7) Having great amount of domain knowledge about product
8) Engaging team members in project
What architects used to do?
1) Having vision on program (multiple projects)
2) Defining architecture of projects
3) Choosing technology / tools to develop projects
4) Defining coding standards / Best practices
5) Collaborating with various team and customers
Though Manager role is not defined in Agile, there is no much difference for Manager role as they conduct Performance Review for team members.
In Agile, I'm sure many of us get confused who takes care of TL role and Architect role?
Though TL role is been done by DT, PO and Architect, Architect role still holds good and needed in Agile as well. It is because, the DT couldn't focus much on system and make decisions on technology and tools.
The below URL discusses on importance of architect in Agile:
https://dzone.com/articles/role-of-architect-in-scrum-team
1) Product Owner (PO)
2) Scrum Master (SM)
3) Development Team (DT)
But, are they enough to develop great software?
I see, moving from water fall model, Agile misses out below roles in a team:
1) Team Lead
2) Software Architect
3) Manager
In Agile world, we don't have any such role called Team Lead. Ok what was the typical duties of TL?
1) Planning a project
2) Recruiting resources ie Interviews
3) Reviewing team's work
4) Interacting with external teams
5) Project Status update to stake holders / customer
6) Giving feedback about team member performance
7) Having great amount of domain knowledge about product
8) Engaging team members in project
What architects used to do?
1) Having vision on program (multiple projects)
2) Defining architecture of projects
3) Choosing technology / tools to develop projects
4) Defining coding standards / Best practices
5) Collaborating with various team and customers
Though Manager role is not defined in Agile, there is no much difference for Manager role as they conduct Performance Review for team members.
In Agile, I'm sure many of us get confused who takes care of TL role and Architect role?
Though TL role is been done by DT, PO and Architect, Architect role still holds good and needed in Agile as well. It is because, the DT couldn't focus much on system and make decisions on technology and tools.
The below URL discusses on importance of architect in Agile:
https://dzone.com/articles/role-of-architect-in-scrum-team