HealthCare.gov As A Project (NOT An Editorial)
- If you set in stone at the beginning of a project the required features, the resource allocation (people/dollars) and the date on which the project must deliver, you're gonna have a bad time.
- If you attempt to entirely rip out an existing system and replace it with a new one, you're gonna have a bad time.
- If you assume development of a system is just a technology project and your users will figure out how to use the tools you provide so you don't need to involve them along the way, you're gonna have a bad time.
- If you think that the timing of decision making and prioritization at higher levels has no effect on the people responsible for developing and implementing a business solution, you should think again.