Scaling Roles

I recently took a program level course on the Scaled Agile Framework (SAFe) and was introduced to 3 roles useful for scaling agile software development – the Release Train Engineer (RTE), the Product Manager (PM), and the Enterprise Architect (EA). Who are these people? And more importantly … what do they care about?

There are 9 SDLC areas represented in People First’s optimization challenge. A Strong(ER) score indicates that a person is a leader/mentor in that area. A Strong score indicates that a person is confident and competent in that area. A Neutral score simply indicates that a person is not strong in the area. This could be because they have not had an opportunity to develop skills in the area, or the area just does not interest them – which is perfectly acceptable. But it can also mean that they delegated the responsibility of caring to others (who care) because of the need to focus and specialize in 1 or 2 areas of the SDLC.

If an RTE were to take People First’s optimization challenge their score would most likely look like this – Strong(ER) in Development Process and Process Performance.

RTE

In comparison, an excellent team level agile/scrum master cares about Development Process and perhaps Process Performance too. Depending on their strengths in other areas of the SDLC their optimization challenge could look like this Scrum Master (actual score).

The RTE, in the context of their focused program level participation, will probably not score Strong in these other areas. They focus on keeping the train on the track and delegate cross-functional responsibilities to self-organized teams. See http://scaledagileframework.com/rte/ for more information about the RTE role.

If a PM were to take People First’s optimization challenge their score would most likely look like this – Strong(ER) in Business Value and Strong in System Value.

Program Manager

In comparison, an excellent team level PO master cares about Business Value and System Value too. Depending on their strengths in other areas of the SDLC their optimization challenge could look like this Product Owner (actual score).

Product Owner 'T'

The PM, in the context of their focused program level participation, will most likely not score Strong in these other areas. Their focus is on the features (content) and the Program Backlog and delegate cross-functional responsibilities to self-organized teams. See http://scaledagileframework.com/product-management/ for more information.

If an EA were to take People First’s optimization challenge their score would most likely look like this – Strong(ER) in Technical Architecture and Strong in Application Architecture.

Enterprise Architect

Epic Owner (EO) of the Architecture Epic, the EA makes sure the enterprise applications make consistent use/reuse of the most capable computer technologies possible. See http://scaledagileframework.com/enterprise-architect/ and http://scaledagileframework.com/architectural-epic/ for more information.

Who owns the Business Epic? A Business Architect is not a role introduced by SAFe but is a common role/title within large enterprises. If a Business Architect were to take People First’s optimization challenge their score would most likely look like this – Strong(ER) in Business Value and System Value.

See http://scaledagileframework.com/business-epic/ for more information.

 

 

 

 

 

 

 

Advertisements