Network Update Lab Develop an Implementation Plan

Learning objective: By the end of this exercise, students will be able to develop a detailed implementation plan for a network update proposal, including tasks, timelines, resources, and risk management strategies.

How should your plan be implemented?

Congrats, you’ve got a solid network update plan and a compelling business case to back it up! Now, it’s time to figure out how you will make it happen.

Your implementation plan should cover all the key phases of the project, from procurement to deployment to post-launch support.

For each phase, outline:

• Tasks: What specific actions need to happen? This could range from “Order new Catalyst 9500 switches” to “Configure segmentation policies in Meraki dashboard”.

• Timeline: When will each task happen, and how long will it take? Factor in lead times for procuring equipment, scheduling maintenance windows for cutovers, and so on.

• Resources: Who will be responsible for each task, and what tools or materials will they need? Consider roles like network engineer, security analyst, project manager, and so on.

• Dependencies: Are there any tasks that can’t start until others are finished? For example, you can’t migrate apps to AWS until the Direct Connect link is up.

• Risks: What could go wrong, and how will you mitigate those risks? Have contingency plans ready for things like equipment DOA, misconfigurations causing outages, and so on.

The key to a successful implementation is thorough planning and clear communication. Everyone involved should know what’s happening, when, and why.

Consider using project management tools like Gantt charts or RACI matrices to keep things organized and on track.

Remember, the goal isn’t just to get the update done - it’s to get it done right, with minimal disruption to General’s business operations. A solid implementation plan will help ensure a smooth transition to General’s new and improved network.