Category: SAFe

WHAT IS PI PLANNING?

INTRODUCTION PI (Program Increment) Planning is the key event in encouraging true agile behavior in SAFe®. It is a whole team event where the whole program – the set of smaller agile teams working closely together as a single team-of-teams – come together in a big room (hence it is often referred to as Big Room Planning) to agree a...

Become a Scaled Agile SAFe Program Consultant/Trainer !

The SAFe Program Consultant Trainer program was introduced by Scaled Agile, it provides a platform for talented individuals who demonstrate capabilities of superior knowledge in providing the agile principles in an enterprise. (SPC’s) are people who combine their technical knowledge of SAfe with true motivation to improve the organization’s development process. Till now 60% of Fortune 100 USA organizations were...

An HR playbook for successful SAFe implementation

Introduction As an organization builds speed for a SAFe implementation, it rapidly winds up clear that significant change is included. Without due consideration, this awareness of looming change breeds fear and uncertainty with respect to those affected by the change. That can be practically every employee. In any change program, particularly one this broad, the projects Human Resources organization has...

Right-sizing features for SAFe Program increments

Introduction One of the key activities that will help make your SAFe® program a success is the cautious arrangement of your Features prior to Program Increment (PI) planning. Also, one essential part of this readiness is to slice up any of the focused-on Features that are too large to even think about being effectively delivered inside the PI. In this...

Design for Testability: A vital aspect of the system Architect role in SAFe

Introduction The system architect role is vital to the successful definition, design, delivery, and support of any IT project. A system architect examination and suggests the correct blend of IT components to accomplish a particular business, department, team, or functional goal. They impartially investigate wanted processes and results and advice on the correct mix of IT systems and segments to...

SAFe being a Scaled Agile Framework, not a Scaled Agile methodology

Introduction To start with, what’s the difference between a framework and a methodology? A methodology is a lot of principles, tools, and practices which can be used to guide processes to achieve a particular goal. A framework is a loose but incomplete structure which leaves space for different practices and tools to be included but provides much of the process...

How to get started with SAFe

Introduction As the world’s leading structure for scaling Agile over the project, the Scaled Agile Framework® (SAFe®) engages complex organizations to accomplish the advantages of Lean-Agile software and frameworks development at scale. Since 2011, hundreds of the world’s biggest organizations have found its advantages: quicker time-to- market, dramatic increments in productivity and quality, and increasingly motivated and connected with employees....

An HR playbook for successful SAFe implementation

Introduction As an organization builds speed for a SAFe implementation, it rapidly becomes clear that significant change is involved. Without due consideration, this awareness of looming change develops fear and uncertainty with respect to those affected by the change. That can be every employee. In any change program, particularly one this extensive, the enterprises Human Resources organization has a significant...

Right-sizing features for SAFe Program increments

Introduction One of the key activities that will help you make your Scaled Agile Framework program a success is the careful preparation of your Features prior to Program Increment (PI) planning. Also, one essential part of this preparation is to slice any of the focused-on Features that are too large to even think about being effectively delivered within the PI....

Design for Testability: A vital aspect of the system Architect role in SAFe

Introduction The system architect role is important to the successful definition, design, delivery, and support of any IT project. A system architect analyses and recommends the correct combination of IT components to achieve a particular business, department, team, or functional goal. They objectively analyze wanted processes and outcomes and advice on the correct combination of IT systems and components to...