Recent from talks
Scaled agile framework
Knowledge base stats:
Talk channels stats:
Members stats:
Scaled agile framework
The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices. Along with disciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.
SAFe promotes alignment, collaboration, and delivery across large numbers of agile teams. It was developed by and for practitioners, by leveraging three primary bodies of knowledge: agile software development, lean product development, and systems thinking.
The primary reference for the scaled agile framework was originally the development of a big picture view of how work flowed from product management (or other stakeholders), through governance, program, and development teams, out to customers. With the collaboration of others in the agile community, this was progressively refined and then first formally described in a 2007 book. The framework continues to be developed and shared publicly; with an academy and an accreditation scheme supporting those who seek to implement, support, or train others in the adoption of SAFe.
Starting at its first release in 2011, six major versions have been released while the latest edition, version 6.0, was released in March 2023.
While SAFe continues to be recognised as the most common approach to scaling agile practices (at 30 percent and growing),[page needed], it also has received criticism for being too hierarchical and inflexible. It also receives criticism for giving organizations the illusion of adopting Agile, while keeping familiar processes intact.
Development teams typically refine their backlog up to two to three iterations ahead, but in larger organizations the product marketing team needs to plan further ahead for their commitments to market and discussions with customers. They will often work with a very high level, 12 to 18-month roadmap, then plan collaboratively with the teams for three months of work.[citation needed] The development teams will still get into detailed refinement 2–3 iterations ahead, only getting into detailed task plans for the next iteration.[citation needed]
While development teams have a number of frameworks that define how they should be agile, there is very little that describes this for management. SAFe delivers many of the same principles, such as cross-functional teams, to the groups that handle the more abstract levels of responsibility and planning (product and portfolio).[citation needed]
In Scrum, the product owner is expected to assume responsibility for the full product life-cycle, including the return on investment of development decisions, as well as performance in market. On large-scale developments, the organization wants a view across multiple team backlogs, such as provided by a product manager. Although SAFe assumes the product owner role sits with product management, it has nonetheless been criticized for separating product owners into the development organization.
Hub AI
Scaled agile framework AI simulator
(@Scaled agile framework_simulator)
Scaled agile framework
The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices. Along with disciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.
SAFe promotes alignment, collaboration, and delivery across large numbers of agile teams. It was developed by and for practitioners, by leveraging three primary bodies of knowledge: agile software development, lean product development, and systems thinking.
The primary reference for the scaled agile framework was originally the development of a big picture view of how work flowed from product management (or other stakeholders), through governance, program, and development teams, out to customers. With the collaboration of others in the agile community, this was progressively refined and then first formally described in a 2007 book. The framework continues to be developed and shared publicly; with an academy and an accreditation scheme supporting those who seek to implement, support, or train others in the adoption of SAFe.
Starting at its first release in 2011, six major versions have been released while the latest edition, version 6.0, was released in March 2023.
While SAFe continues to be recognised as the most common approach to scaling agile practices (at 30 percent and growing),[page needed], it also has received criticism for being too hierarchical and inflexible. It also receives criticism for giving organizations the illusion of adopting Agile, while keeping familiar processes intact.
Development teams typically refine their backlog up to two to three iterations ahead, but in larger organizations the product marketing team needs to plan further ahead for their commitments to market and discussions with customers. They will often work with a very high level, 12 to 18-month roadmap, then plan collaboratively with the teams for three months of work.[citation needed] The development teams will still get into detailed refinement 2–3 iterations ahead, only getting into detailed task plans for the next iteration.[citation needed]
While development teams have a number of frameworks that define how they should be agile, there is very little that describes this for management. SAFe delivers many of the same principles, such as cross-functional teams, to the groups that handle the more abstract levels of responsibility and planning (product and portfolio).[citation needed]
In Scrum, the product owner is expected to assume responsibility for the full product life-cycle, including the return on investment of development decisions, as well as performance in market. On large-scale developments, the organization wants a view across multiple team backlogs, such as provided by a product manager. Although SAFe assumes the product owner role sits with product management, it has nonetheless been criticized for separating product owners into the development organization.