Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  Business Analyst Lesson from Healthcare.gov system glitch
Previous Previous
 
Next Next
New Post 10/22/2013 12:41 PM
User is offline Mike
1 posts
No Ranking


Business Analyst Lesson from Healthcare.gov system glitch 
Modified By Chris Adams  on 10/22/2013 3:04:31 PM)

What can we (Business Analyst) learn from Healthcare.gov (Obamacare) System glitch?

One contributing factor to its system failure seems to be with SPECIFICATION:

http://www.newyorker.com/online/blogs/elements/2013/10/why-the-healthcaregov-train-wreck-happened-in-slow-motion.html?mobify=0

Any thoughts on this ?

 
New Post 11/9/2013 8:00 PM
User is offline Chris Adams
323 posts
5th Level Poster






Re: Business Analyst Lesson from Healthcare.gov system glitch 

I'd be cautious about assuming anything about the project from an article.  I'm sure you've been on enough project to know that the only people who understand what really went wrong are those working on the project.  And they usually don't give the full truth to reporters because they are trying to cover their a a**

With that said, this is a government project.  It probably had rediculously complex and verbose specifications.  And yes the requirements were probably changing.  We all know they difficulties of trying to conform to a strict waterfall methodology.  Requirements change, that's life.

With this type of system, the most important part of the project should have been the data model.  You have 100s of systems that all need to interface and exchange data.  It all starts with the data.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  Business Analyst Lesson from Healthcare.gov system glitch

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC