We're using a hodgepodge mix of Sharepoint and Word docs for management to track and approve network changes and it's plain awful. Often when an engineer writes a MOP that gets rejected by our weekly review team, by then they've moved onto another project so someone else needs to pick up where they left off. There's little to no info as to why the original config change was rejected, and no way for us to easily suss out how the project evolved over time (MOPs are written in Word docs that are rarely commented). Is there a centralized solution out there that actually works well for engineers and management alike, or is there an actual legitimate need for this?
No comments:
Post a Comment