Some IT systems are maintained for decades. Others are replaced with ground-up rewrites after 5 years or less. There are always trade-offs to be made, but some approaches better fit IT systems with long-lived missions.
At a certain point, a whole-sale rewrite is the best option for replacing the stale, decaying software that leads to major headaches and eventual catastrophe. That said, big rewrites have big risks and big failures. For systems with stable and enduring mandates, long-term investments in IT systems pay off and give room for smart maintenance strategies.
Rather than engaging in an intense modernization effort followed by years of minimal maintenance, a better alternative often is modernizing a system continuously, balancing operations, maintenance, and renovation. Ideally you can improve, update, and upgrade the software system one piece at a time while it continues to operate, avoiding feature freezes and scary cut-overs. This presentation will explore ways to continually modernize.
6:30-7:00 Happy (half) Hour - Grab some food and drink, and meet people
About the Presenter:
Dane Weber is presently a Ruby software developer, but has served in many roles over the last ten years in the software development world including product owner, Agile coach, Scrum Master, business analyst, and account owner. He sees software systems as an extension of human systems, both of which he is passionate about improving. He brings a unique perspective to the software development world with his broad IT experience along with his externships and M.S. in Clinical Psychology. His new hobby is collecting certifications, including: CLP, CSD, CSM, ICP-ACC, ICP-ATF, PMI-ACP, and PMP.