This week's introduction

You've spent a lot of time so far making careful decisions about how you will be using your software. I'm sorry to have to be the one to tell you this, but here it is: you didn't design HIFIS perfectly.

There.

I've said it.

No matter how much time you've spent, and how great you think it is, there's something you overlooked. Maybe there's something that sounded great in theory but once you get to the real world, it's no longer great. Or maybe everything is in fact perfect, until the next software update comes out which causes you to rethink some of your earlier decisions. Or everything's working well until a change in funding requirements, or until a new program begins...

That's normal. After implementation, you are going to be continually testing and tweaking your software to make it just right. The good news is it's going to be way easier to do so now that you're familiar with your whole system and what HIFIS can and can't do.

This week's topic is managing changes, issues and bugs, and software updates.