Fantastic transformation story JP!

Very informative, thanks JP ☺

Thank you JP for sharing this inspiring transformation story! You brilliantly demonstrated how starting small with just 2 committed leaders out of 28 led to massive organizational change. I particularly appreciate how you handled the two different leadership styles - one wanting rapid change and the other preferring a systematic approach. Your patient-doctor analogy perfectly captures why peer success stories drive better adoption than top-down mandates. Reducing release cycles from 3.5 years to under 2 years is incredible! Your approach of letting success create a pull effect clearly worked, as evidenced by the expansion to 50+ ARTs. Keep sharing these valuable real-world implementation stories!

What is SAFe SPC Certification All About?

From Engineering Leader to Transformation Consultant

Driving Innovation to Market Faster with SAFe

JP, I love the energy you bring to this video! Your passion truly shines through, and it’s clear that your firsthand experience with Agile transformation fuels your enthusiasm.

Very Nice Initiative. All the best

very informative.

Precise and to the point info

Thank you. Can you please share the link to download the Leading SAFE 6.0 workbook?

Inspiring!

Very well explained - thank you.

Register with this link: us06web.zoom.us/webinar/register/WN_puoyqnrfS4qmvOHpxaL8cA

*promosm*

Great 👍

how can we join this session ?

Product management is very diluted in Indian market. At best a technical product manager can come close to a product owner

@4:54 is the key

Great Video - Great Point ! In one of my past project the architect equated utilization to productivity and since he had the over riding "position" the mgmt went with it. The end result was that the project was delayed by 6 months. I hope he sees this message and understands the difference !

This video is very helpful for all teams who are transitioning from waterfall to Agile. This is a classic issue for teams who are not cross function or who still have "developers" and "testers" separately inside an agile team.

Very nice overview JP sir

I agree with this, except for the statements at the end regarding allowing waterfall inside a story. There are ways in which we can be Agile even inside a story, and we should absolutely go there. We can use acceptance criteria or automated acceptance tests as internal vertical slices, and have working functionality at the end of each slice. Best teams are doing this, and they deliver working, tested code (”Done”) every 15 to 120 minutes.

Good Information very Useful Sir

Great piece of information

In both, the case 10 stories delivered. The team which not even picked stories to work on whether they utilized the free time for learning or Identifying areas for improvements? This answer will tell in the long term who is giving more value to the customer.