A guide for how to build a Network Automation practice

[Nicklas Wagerth]

Overcoming Hurdles in Network Automation: A Practical Guide to Navigating Change with NADM

There's a lot of talk in the business world about the non-technical obstacles that prevent companies from adopting Network Automation. Indeed, implementing major changes can be daunting, but numerous companies have successfully navigated this transition. We've collated their advice and strategies along with our best practices into one easy-to-read document.

Don't worry, it's not rocket science! But it does need some elbow grease, teamwork, and a positive attitude towards change.

The Cisco Network Automation Delivery Model (NADM) is a useful guide for building a successful automation practice. This step-by-step model is based on the structured change management approach proposed by the expert John Kotter.

So why do we need NADM? Whether you're making minor adjustments or major overhauls, the enormity of the task can be overwhelming. It's difficult to know where to begin, who should be involved, and how to ensure the changes are sustainable.

That's where NADM comes into play. You can view it chronologically or by topic. While you might find many familiar elements, reviewing the model in its entirety can help identify any gaps or weak areas in your current approach.

We are eager to hear your thoughts and experiences. Please feel free to leave a comment on this post

A practical guide to build a Network Automation practice

[Torbjørn]

There seems to be some not-properly-rendered markdown under "Phases and steps". Other than that I think the NADM is great! This will absolutely be of use.

[Stampeder]

Two immediate comments come to mind.

First as laid out ADM is the definition of an Agile project. Given the steps outlined if falls almost perfectly into the Agile Methodology.

Next is Single Source of Truth. Automation is a network application. Meaning is involves many network elements and by definition requires documentation or in short a Single Source of Truth. This is not only essential it is critical to the success of any automation project. In over 30 years of networking I have seen many disasters in automation attempts from the single lack of an accurate Single Source of Truth. If you can't put it on paper you can't automate it.

Finally, given the above comments I think this is an excellent approach and one with a great deal of merit.

[Nicklas Wagerth]

Thank you for your insightful comments! I have made a note of the "not-properly-rendered markdown" issue and plan to address it soon.