Transitioning from Waterfall to SAFe in Cisco-centric network environments?

All answers to this question.

The biggest hurdle in a SAFe transition is shifting the mindset from fixed milestones to iterative value streams. In network environments, you have to align hardware procurement cycles with software sprint cadences. When I led a similar transition in 2023, we focused on establishing "Agile Release Trains" that included both network engineers and developers. This reduced our deployment lead time by 35%. You must ensure that your Product Owners understand the technical debt associated with legacy Cisco configurations to avoid late-stage bottlenecks.

   Answered 2024-05-16 by Deborah Higgins

How are you handling the "Definition of Done" for physical hardware tasks compared to software updates? In an Agile framework, it's easy to track code, but how do you quantify a successful router configuration in a two-week sprint? Are you using any automated testing tools like Cisco Modeling Labs to validate your "Done" state before physical implementation?

   Answered 2024-05-18 by Ryan Mitchell

• Ryan, that is a critical point. Currently, we use CML for virtual validation, which allows us to treat "Done" as a verified simulation. This way, the hardware team stays in sync with the software sprints. We found that without virtual staging, our sprints were constantly slipping due to hardware lead times and physical lab availability. Addressing this early saved our Agile pilot from failing.

     Commented 2024-05-20 by Mark Stevens

I recommend starting with a small pilot team to test the SAFe ceremonies before scaling. This prevents the initial confusion from disrupting your entire global refresh timeline.

   Answered 2024-05-21 by Karen Douglas

• I agree with Karen. Small-scale testing of PI Planning prevented a lot of chaos during our rollout last year. It’s the safest way to iron out communication gaps.

     Commented 2024-05-22 by Deborah Higgins