Deployment of a project office using the SAFe methodology using the “Project Management Hexagon” metric, part 1

Description of the SAFe methodology

SAFe (Scaled Agile Framework) is a scalable agile methodology that allows organizations to manage large programs and project portfolios through the integration of individual Agile teams into a single system. SAFe aims to organize synchronization between teams, providing clear structures for management both at the level of individual projects and at the level of the organization as a whole. The framework supports work at several levels:

1. Command level: used Scrum, Kanban, XP to complete tasks.

2. Software level: control a group of commands via Agile Release Train (ART)which implements program goals.

3. Portfolio level: strategic project management and resource allocation between programs.

Project Management Hexagon Metric

The Project Management Hexagon is a model that includes six key metrics to measure the success and productivity of projects. In context SAFe these metrics can be used to evaluate performance both at the individual team level and at the project portfolio level.

1. Time: time management and meeting deadlines at all levels of the project. Estimate the time spent on completing tasks and iterations within sprints, programs and portfolio.

2. Resources: assessing the effectiveness of the use of human and material resources, both within individual teams and at the portfolio level. The resource metric also evaluates the allocation of employees to tasks based on their skills.

3. Quality: quality built into product development and process management through SAFe-approaches to testing, verification and validity of the product at all levels.

4. Risks: risk management and changing plans to account for unforeseen circumstances. IN SAFe risk management is synchronized at all levels.

5. Costs: control over the budget and costs, assessment of financial efficiency.

6. Value: Measuring the value created for customers across an entire program or portfolio.

Roles in SAFe and their relationship to the Management Hexagon metrics

1. Release Train Engineer (RTE)

• Metrics: Time, Risks.

• Function: Coordinating the work of all teams, ensuring synchronization and meeting deadlines, managing risks at the program level.

• Documents: Program Increment Plan (PI Plan), risk report.

• Tools: JIRA, Confluence, PI Planning tools.

2.Product Owner

• Metrics: Value, Resources.

• Function: Prioritizing tasks in the backlog, working with the team to maximize the value created.

• Documents: Product Backlog, Roadmap.

• Tools: JIRA, Kanban boards.

3. Scrum Master

• Metrics: Time, Quality.

• Function: Help the team adhere to Scrum processes, remove roadblocks and support completion of tasks on time with a focus on quality.

• Documents: Scrum Backlog, sprint report.

• Tools: JIRA, Confluence.

4.Business Owner

• Metrics: Cost, Value.

• Function: Management of strategy at the portfolio level, monitoring the budget and financial performance of the program.

• Documents: Financial reports, strategic plans.

• Tools: Financial Planning Software, Confluence.

5. System Architect/Engineer

• Metrics: Quality, Risks.

• Function: Development and coordination of architectural solutions, product quality support.

• Documents: Architectural solutions, testing reports.

• Tools: Confluence, tools for CI/CD.

SAFe Project Management Tools

Deployment of a project office under SAFe requires the use of a number of tools to synchronize the work of all levels of management, from teams to portfolio.

1. JIRA/Azure DevOps — task management at all levels (team, program, portfolio).

2. Confluence — a centralized system for documenting processes, plans and architectural solutions.

3. PI Planning Tools – tools for carrying out PI Planningwhere software increments are planned for several iterations ahead.

4. Kanban boards — help track the progress of tasks and synchronization between teams.

5. AgilePM — a system for managing Agile projects that supports work at all levels SAFe.

Documents in a project office working on SAFe

Project office within SAFe requires formalization of processes and maintenance of key documents to manage programs and portfolios. Basic documents that must be maintained in the project office:

1. Backlog at portfolio level — includes strategic initiatives and major projects to be implemented.

2. Program Backlog — a list of tasks and goals for a software increment.

3. Team Backlog — tasks to be performed at the command level.

4. PI Plan — a software increment plan that specifies goals, priorities and tasks for several iterations ahead.

5. Roadmap — a roadmap showing the main stages and deadlines for completing tasks.

6. Risk and change reports — Risk and change management documents are maintained for all levels.

7. Financial reports — cost estimation for programs and strategic projects.

Description of relationships: Hexagon matrix of management/roles/documents/tools

Text description:

Each Project Management Hexagon metric is associated with specific roles, documents, and tools. Timeas a key metric, is controlled Release Train Engineer (RTE) And Scrum Master. To do this, use task management tools such as JIRA And Kanban boardsand documents progress in sprint reports and increment plans.

Resources managed Product Ownerwho is responsible for prioritizing tasks and allocating resources within teams. He uses Product Backlog And Roadmapas well as task management tools such as JIRA.

Quality controlled through roles Scrum Master And System Architect/Engineerwho monitor the implementation of testing, CI/CD and correct product development. Important documents include architectural designs and testing reports.

Risks managed at all levels, especially through Release Train Engineer And System Architectusing risk reports and problem analysis tools.

Conclusion

Project office working according to the methodology SAFerequires adaptation of management processes and the use of key metrics of the “Project Management Hexagon”. Deployment of a project office at the base SAFe allows you to effectively manage large programs and portfolios, ensuring synchronization, control over resources, risks and quality. An important element of successful implementation is the correct integration of roles, documents and tools that support tasks at all levels of management.