Sign up to save your podcasts
Or
Share Scaled Agile SAFe Inspect and Adapt Event Scaled Agile Framework
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Scaled Agile SAFe Inspect and Adapt Event Scaled Agile Framework
#SAFe #inspectandadapt #agile The #Inspectandadapt is a significant event, held at the end of each #ProgramIncrement, where the current state of the #Solution is demonstrated and evaluated by the train. after this evaluation, the teams reflect on the #backlog items and identify things to be improved, thus upholding the #agilemanifesto principle of continuous improvement and adjustment. This is additionally one of the four pillars of #SAFe. These opportunities should occur continuously throughout every #programincrement, but having additional structure and synchronization allows time to be allocated towards identifying and applying #improvements across many different teams. All #ARTstakeholders participate along with the #AgileTeams in the I&A event. The result is a set of improvement #backlog items that go into the #ProgramBacklog for the next #PIPlanning event. in this way, every #AgileReleaseTrain improves every #PI. For #LargeSolutions, a similar I&A event is held by the #SolutionTrain. The I&A event consists of three parts: #PISystemDemo #Quantitative and #qualitative measurement #Retrospective and problem-solving workshop The #PISystemDemo is there to show all the features that have been developed within the #AgileReleaseTrain over the course of the #ProgramIncrement. The audience of this demo typically includes the #customer, #portfoliorepresentatives, and more. This means the event follows a more formal pattern and requires time for preparation and staging, though still timeboxed, with an emphasis on keeping #stakeholders engaged to provide #feedback for #improvement. During the second part of the I&A event, teams review the metrics that had been previously agreed upon to collect and discuss the data to decide upon the actions that should be taken moving forward, like realignment or improvement. The #ReleaseTrainEngineer and #SolutionTrainEngineer must prepare for this in advance by gathering the relevant information and analyzing it to ensure the data is accurate, before working on a presentation for the #ART to look over. The teams then have a brief retrospective to identify significant issues that may have come up during the #PI, allowing time to address them, or at least come up with a plan to utilize moving forward. The #teams can provide members to develop new problem-solving teams, or existing teams can choose to tackle them. The combination of different members from existing #teams allows for a greater diversity of thought, however, and helps develop solutions faster. For addressing systemic problems, a structured, root-cause problem-solving workshop is held by the #ART. This kind of from-the-ground-up analysis of the problem allows the #ART to see what's causing the issue and gives them greater flexibility to actually solve the problem, not just the symptoms.
View all episodes
By ALEPH GLOBAL SCRUM TEAM™#SAFe #inspectandadapt #agile The #Inspectandadapt is a significant event, held at the end of each #ProgramIncrement, where the current state of the #Solution is demonstrated and evaluated by the train. after this evaluation, the teams reflect on the #backlog items and identify things to be improved, thus upholding the #agilemanifesto principle of continuous improvement and adjustment. This is additionally one of the four pillars of #SAFe. These opportunities should occur continuously throughout every #programincrement, but having additional structure and synchronization allows time to be allocated towards identifying and applying #improvements across many different teams. All #ARTstakeholders participate along with the #AgileTeams in the I&A event. The result is a set of improvement #backlog items that go into the #ProgramBacklog for the next #PIPlanning event. in this way, every #AgileReleaseTrain improves every #PI. For #LargeSolutions, a similar I&A event is held by the #SolutionTrain. The I&A event consists of three parts: #PISystemDemo #Quantitative and #qualitative measurement #Retrospective and problem-solving workshop The #PISystemDemo is there to show all the features that have been developed within the #AgileReleaseTrain over the course of the #ProgramIncrement. The audience of this demo typically includes the #customer, #portfoliorepresentatives, and more. This means the event follows a more formal pattern and requires time for preparation and staging, though still timeboxed, with an emphasis on keeping #stakeholders engaged to provide #feedback for #improvement. During the second part of the I&A event, teams review the metrics that had been previously agreed upon to collect and discuss the data to decide upon the actions that should be taken moving forward, like realignment or improvement. The #ReleaseTrainEngineer and #SolutionTrainEngineer must prepare for this in advance by gathering the relevant information and analyzing it to ensure the data is accurate, before working on a presentation for the #ART to look over. The teams then have a brief retrospective to identify significant issues that may have come up during the #PI, allowing time to address them, or at least come up with a plan to utilize moving forward. The #teams can provide members to develop new problem-solving teams, or existing teams can choose to tackle them. The combination of different members from existing #teams allows for a greater diversity of thought, however, and helps develop solutions faster. For addressing systemic problems, a structured, root-cause problem-solving workshop is held by the #ART. This kind of from-the-ground-up analysis of the problem allows the #ART to see what's causing the issue and gives them greater flexibility to actually solve the problem, not just the symptoms.