Scaled Agile
Agile is all about responding to change. That does not necessarily mean that we should leave everything to be done at an ad hoc basis which will eventually lead to a disaster at all developmental and management levels. Thus it is wise to have some level of planning done. A
Scaled Agile
Visibility and transparency are important when it comes to planning or tracking your work items in the Program Increment. All of the work items have stories, dependencies, risks and objectives and failing to correctly recognize or acknowledge them can lead to disrupting a transparent flow of information. To ensure that
Dependency Management
Agile teams are meant to be self managing and independent. But as the size of an organization grows or the scope of the product being developed becomes complex, many teams have to work together. Thus dependencies can start existing between these different agile teams. These dependencies can become a serious
PI Planning
In the Scaled Agile Framework, staying strongly committed to a plan is never advised. The reason is very simple; the requirements of the customer can change. For any professional that is a part of the Scaled Agile Framework, possessing a Lean-Agile Mindset is fundamental. It is in fact one of
PI Planning
For the Scaled Agile Framework, PI Planning holds utmost importance and value. It heavily relies on the presence of people to be located in one place, under one roof to discuss and plan what needs to be done in the Program Increment. Unfortunately, the Coronavirus pandemic disturbed life all over
PI Planning
Program Increment (PI) Planning session is a time boxed event where Teams of an Agile Release Train that are united by a shared vision, meet and plan new features, discuss dependencies and risks. It is truly a cornerstone event for SAFe; without it SAFe cannot be implemented. In this article
PI Planning
There is nothing better than having everyone in the same room for PI, tribe or big room planning. But it’s not easy, it’s expensive and not everyone can travel. Kendis offers solution, which enables teams to plan together from different locations. It will help you manage digital program
PI Planning
“If everyone is moving forward, then success takes care of itself”- Henry Ford In the Scaled Agile Framework (SAFE), the Agile Release Train (ART) is designed to deliver solutions by working around a Value Stream with the collaboration of multiple Agile Teams and stakeholders. While remaining steadfast to a
Scaled Agile
In today’s highly competitive world, organizations are driven by technology and are becoming very innovative in achieving their goals and to eventually stay ahead. Starting off with this New Year January 2020, SAFe released its upgrade, “SAFe 5.0” which entirely focuses on “Business Agility” and addresses how to
PI Planning
The most vital component of achieving anything of value and essentially the backbone of SAFe, is the Program Increment (PI). A Program Increment is timeboxed to 8-12 weeks, where an Agile Release Train, which is constituted of multiple agile teams work towards accomplishing the objectives of the PI. An Agile
Risks
When creating a project, encountering risks is inevitable. With growing technologies and newly evolving working methodologies, risk management has become extremely important. Risks need to be identified and mitigated properly or they can gravely harm your progress. These risks need to be addressed with utmost clarity and transparency. Today, many
Solution Board
What is a Solution Train? The Solution Level is where large solutions are built with the collaboration from multiple Agile Release Trains which may have thousands of practitioners. Solution train builds complex solutions with a Lean-Agile approach. It organizes and coordinates multiple Agile Release Trains into one, guiding the focus