Difference between revisions of "Bhamilton18 Week 11"

From LMU BioDB 2017
Jump to: navigation, search
(Finished Defintions)
(Added Outline points--problems, main message and the needs)
Line 20: Line 20:
 
#'''Tech Surge:''' "The Obama administration says this surge is made up of engineers from inside and outside government" that are employed to "clean up the code of the error-plagued HealthCare.gov site."
 
#'''Tech Surge:''' "The Obama administration says this surge is made up of engineers from inside and outside government" that are employed to "clean up the code of the error-plagued HealthCare.gov site."
 
#*https://www.npr.org/sections/alltechconsidered/2013/10/22/239220962/the-healthcare-gov-tech-surge-is-racing-against-the-clock
 
#*https://www.npr.org/sections/alltechconsidered/2013/10/22/239220962/the-healthcare-gov-tech-surge-is-racing-against-the-clock
−
==The Secret Startup That Saved the Worst Website in America '''''Outline'''''==
+
==''The Secret Startup That Saved the Worst Website in America'' '''''Outline'''''==
−
#What is the main message of this work?
+
===Main Message===
 +
'''It is important to be adaptable when creating a project, as plans and goals change throughout the process. Keeping an open mind, with many difference perspectives allows the project to run more smoothly and effectively.'''
 +
===The Problem===
 +
#The US government attempted to create a HealthCare.gov website in order for citizens to find and sign up for health care.
 +
#HealthCare.gov became one of the worst websites for users.
 +
#*'''91% uptime rate'''
 +
#*'''Six successful sign ups on the first day'''
 +
#**'''Despite thousands attempting'''
 +
#*'''$250 million to build'''
 +
#*'''$70 million maintain'''
 +
===The Need===
 +
#Technical Workers who could quickly to fix, maintain and reduce costs of the Healthcare.gov website
 +
#*This created a '''Tech Surge''' which was a group of Silicon Valley developers who needed to "save" the website.
 +
#Althoguh the '''Tech Surge''' received the most spotlight, it was a group called Marketplace Lite that dealt with the nitty-gritty of HealthCare.gov.
 +
#*'''Marketplace Lite''' was a a group of designers and developers that worked round the clock to create a working, successful health care tool.
 +
===The Process===
 +
#Marketplace Lite was a small group of start up coders whose work started at the Doubletree Hotel in Baltimore.
 +
#The MPL (Marketplace Lite) was set up for days in the dining rooms, floors and lobby of the hotel.
 +
#The days consisted of 10hours a day 7 days a week for months.
 +
#The MPL wanted to create a more efficient way to store and manage the data that came with the HealthCare.gov website.
 +
#*This prompted the MPL workers to reach out to cheaper storage options, such as '''Amazon Web Services (AWS)'''.
 +
#**AWS allows for users to rent storage or computational power  more cheaply than running/storing on the users own.
 +
#***By utilizing off site super computers, AWS can increase runtime, decrease cost and scale the computational power to the demand of the consumer.
 +
#**The AWS platform was not accepted by the government for many months, therefore as a place holder '''Akami''' was used.
 +
#***AWS was approved nearly six months later in the process.
 +
#By 2014, the members in the MPL team and Tech Surge projects contact's were running out. While the Tech Surge group was disbanding many members in the MPL team stayed on the project and even quit their "day-jobs."
 +
#*One person left Google, one left SkillShare
 +
#*New members were hired with start up experience to help the project continue smoothly.
 +
#One important piece of tech that dramatically increased the MPL work efficiency was the implementation of '''HipChat'''
 +
#*'''HipChat''' is a group chatroom, much like Slack, that allows quick messages and attachments to be sent and reviewed more efficiently than email.
 +
#Preceding the implementation of HipChat the government began forcing deadlines and work environment regulations.
 +
#*This included creating a detailed 3-month plan for the coders to follow, despite accepting the "agile" way for working.
 +
#**As defined above, the "agile" way of working is more effective, especially for programers, developers and designers as it allows flexibility with project deadlines and adjustment for errors.
 +
#*The government wanted to control every aspect of the website despite not understanding how it or the programmer plan worked.
 +
#With time, the government learned that the programmers "knew what they were doing" and followed the launch plan of '''App 2.0'''
 +
#*'''App 2.0''' is the MPL insurance application that allowed users to sign up and in more quickly than the original application.
 +
#**Users could finish in '''9 minutes''' versus the original '''20 minutes'''
 +
#**Users only had to go through '''16 pages''' in stead of '''76 pages'''
 +
#** A record '''85%''' of users were able to finish the registration versus the previous '''55%.'''
 
#What is the importance or significance of this work?
 
#What is the importance or significance of this work?
−
#What design/development practices, processes, techniques, methods, or approaches were described in this work?
 
 
#Briefly state how these activities benefit the endeavors of web design and/or software development.
 
#Briefly state how these activities benefit the endeavors of web design and/or software development.
−
#Summarize the main points of the work.
 
 
#What aspects of this work will inform how you carry out your final project?
 
#What aspects of this work will inform how you carry out your final project?
−
===Presentation===
+
==Presentation==
 
==Acknowledgments==
 
==Acknowledgments==
 
==References==
 
==References==

Revision as of 19:34, 13 November 2017

Definitions

  1. Uptime rate: "time during which a piece of equipment (such as a computer) is functioning or able to function."
  2. Infrastructure: "the underlying foundation or basic framework (as of a system or organization)."
  3. AWS: "Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, content delivery and other functionality to help businesses scale and grow."
  4. Cloud Computing: "Cloud computing is the on-demand delivery of compute power, database storage, applications, and other IT resources through a cloud services platform via the internet with pay-as-you-go pricing."
  5. Domain-name routing: It begins with a Domain Name System which "is a directory used by SMTP to convert a name to a list of servers that can receive connections for that name and to find the IP address of a specific server."
  6. Akamai: "is the global leader in Content Delivery Network (CDN) services, making the Internet fast, reliable and secure for its customers."
  7. Sequential design strategy: "are iterative algorithms that use data acquired from previous iterations to guide future sample selection."
  8. Gantt chart: "A general production planning tool for scienti- fically managed factories."
  9. Agile-strategy: "is proposed in response to the circumstances as a solution and is perceived as a vital characteristic that manufacturing companies need to have in order to maintain their competitive advantages in the new order of world business"
  10. Tech Surge: "The Obama administration says this surge is made up of engineers from inside and outside government" that are employed to "clean up the code of the error-plagued HealthCare.gov site."

The Secret Startup That Saved the Worst Website in America Outline

Main Message

It is important to be adaptable when creating a project, as plans and goals change throughout the process. Keeping an open mind, with many difference perspectives allows the project to run more smoothly and effectively.

The Problem

  1. The US government attempted to create a HealthCare.gov website in order for citizens to find and sign up for health care.
  2. HealthCare.gov became one of the worst websites for users.
    • 91% uptime rate
    • Six successful sign ups on the first day
      • Despite thousands attempting
    • $250 million to build
    • $70 million maintain

The Need

  1. Technical Workers who could quickly to fix, maintain and reduce costs of the Healthcare.gov website
    • This created a Tech Surge which was a group of Silicon Valley developers who needed to "save" the website.
  2. Althoguh the Tech Surge received the most spotlight, it was a group called Marketplace Lite that dealt with the nitty-gritty of HealthCare.gov.
    • Marketplace Lite was a a group of designers and developers that worked round the clock to create a working, successful health care tool.

The Process

  1. Marketplace Lite was a small group of start up coders whose work started at the Doubletree Hotel in Baltimore.
  2. The MPL (Marketplace Lite) was set up for days in the dining rooms, floors and lobby of the hotel.
  3. The days consisted of 10hours a day 7 days a week for months.
  4. The MPL wanted to create a more efficient way to store and manage the data that came with the HealthCare.gov website.
    • This prompted the MPL workers to reach out to cheaper storage options, such as Amazon Web Services (AWS).
      • AWS allows for users to rent storage or computational power more cheaply than running/storing on the users own.
        • By utilizing off site super computers, AWS can increase runtime, decrease cost and scale the computational power to the demand of the consumer.
      • The AWS platform was not accepted by the government for many months, therefore as a place holder Akami was used.
        • AWS was approved nearly six months later in the process.
  5. By 2014, the members in the MPL team and Tech Surge projects contact's were running out. While the Tech Surge group was disbanding many members in the MPL team stayed on the project and even quit their "day-jobs."
    • One person left Google, one left SkillShare
    • New members were hired with start up experience to help the project continue smoothly.
  6. One important piece of tech that dramatically increased the MPL work efficiency was the implementation of HipChat
    • HipChat is a group chatroom, much like Slack, that allows quick messages and attachments to be sent and reviewed more efficiently than email.
  7. Preceding the implementation of HipChat the government began forcing deadlines and work environment regulations.
    • This included creating a detailed 3-month plan for the coders to follow, despite accepting the "agile" way for working.
      • As defined above, the "agile" way of working is more effective, especially for programers, developers and designers as it allows flexibility with project deadlines and adjustment for errors.
    • The government wanted to control every aspect of the website despite not understanding how it or the programmer plan worked.
  8. With time, the government learned that the programmers "knew what they were doing" and followed the launch plan of App 2.0
    • App 2.0 is the MPL insurance application that allowed users to sign up and in more quickly than the original application.
      • Users could finish in 9 minutes versus the original 20 minutes
      • Users only had to go through 16 pages in stead of 76 pages
      • A record 85% of users were able to finish the registration versus the previous 55%.
  9. What is the importance or significance of this work?
  10. Briefly state how these activities benefit the endeavors of web design and/or software development.
  11. What aspects of this work will inform how you carry out your final project?

Presentation

Acknowledgments

References

  1. Crombecq, K., Tommasi, L. D., Gorissen, D., & Dhaene, T. (2009). A novel sequential design strategy for global surrogate modeling. Proceedings of the 2009 Winter Simulation Conference (WSC). doi:10.1109/wsc.2009.5429687
  2. H. Sharifi, Z. Zhang, (2001) "Agile manufacturing in practice ‐ Application of a methodology", International Journal of Operations & Production Management, Vol. 21 Issue: 5/6, pp.772-794, https://doi.org/10.1108/01443570110390462
  3. Wilson, James M. (2003). "Gantt charts: A centenary appreciation" (PDF). European Journal of Operational Research. 149 (2): 430–437. doi:10.1016/S0377-2217(02)00769-5. Archived from the original (PDF) on 26 November 2013.
Retrieved from "https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Bhamilton18_Week_11&oldid=4326"