PI Planning
Kendis suggests reserving time to discuss Testing and Release strategies during the PI Planning event. Testing is a foundational and crucial aspect of software development that helps create high-quality and robust software to provide a trouble-free experience to the end user. Without it, the process of developing software is incomplete.
PI Planning
Planning Adjustments take place after the Draft Plan or Management Review and are usually the first event of Day 2 if you are following the two-day SAFe PI Planning. What are Planning Adjustments? Planning Adjustments are done to share any updates and communicate any high-level changes that may have been
PI Planning
As the dust settles after the exhilarating event of PI (Program Increment) planning, teams brace themselves for the journey ahead. PI planning marks the beginning of a new increment, filled with ambitious goals, collaborative efforts, and a shared vision. However, as the saying goes, The toughest challenges often reveal themselves
PI Planning
The event that concludes the first day of the PI Planning Agenda is called the Management Review. What is a Management Review? The Management Review aims to provide a platform for team leads, managers, and stakeholders to openly discuss any questions, challenges, or concerns regarding the PI Planning. The common
Scrum
In the ever-evolving landscape of Agile methodologies, the Scaled Agile Framework (SAFe) has recently made a significant terminology shift by rebranding Scrum Masters as "coaches." While this change signifies a broader scope of responsibilities and a more holistic approach to leadership, it also prompts a critical reflection on
PI Planning
The event that shows the results and summarizes the collective efforts of all the teams involved in the Team Break-Out sessions in the PI Planning Agenda, is called the Draft Plan Review. What is a Draft Plan Review? The Draft Plan Review is where teams give short presentations on their
PI Planning
As we approach halfway towards the first day of the PI Planning Agenda, after setting the Business Context,Product and Solution Vision, and Architectural Vision, the next recommended event that follows is the Planning Context. What is Planning Context? The Planning Context is when the planning processes and expected outcomes,
PI Planning
After establishing solid ground for PI Planning in the Scaled Agile Framework in the PI Planning Agenda with the Business Context and the Product and Solution Vision, the third recommended event that follows is the Architectural Vision. What is Architectural Vision? The Architectural Vision focuses on the technical aspects of
PI Planning
After the Business Context is presented and has provided the basis for PI Planning in the Scaled Agile Framework in the PI Planning Agenda, the Product and Solution Vision is the second event that follows. What is Product and Solution Vision? The Product and Solution Vision aims to highlight the
PI Planning
The PI Planning event in the Scaled Agile Framework (SAFe) goes for 2 or 3 days. The PI Planning agenda consists of various activities that aim to cover a vast scope of the Program Increment. The first event that takes place and sets the tone of the entire PI Planning
Scaled Agile
Epics, Features, and User Stories are trending words in the Agile community. Any organization that has adopted the agile way of working is seemingly obsessed with epics, features, and user stories and these organizations cannot seem to get enough of them. Indeed these work items are a critical part of
Scaled Agile
Product Management is a core and indispensable element of Agile Development in any Scaling Framework. It needs to ensure the creation of products or solutions to completely meet the needs of the end users. In order for this to be successful, a tremendous amount of work and individuals are required