Skip to main content

Week 6 Lecture - Reflection of Fishman "They Write the Right Stuff" (1996) Reading


During the lecture, we reflected on the assigned reading: Fishman, "They Write the Right Stuff" (1996)

Summary of Paper


  • The NASA process stifles creativity but that is the point
  • People working at the company have to channel their creativity into changing the process not changing the software
  • 12 of 22 members are women
  • They work strictly 8-5 unlike coders unlike in companies such as Microsoft where late nights are common
  • Its all about the process that allows them to work normal hours, stay on budget and deliver on time

  1. The product is only as good as the plan for the product - plan the most minute detail before commencing writing the code - their requirements are almost " blueprint like detail
  2. The best teamwork is rivalry team work
  3. Have a database on why, how, when etc. code was changed and also a database describing every error dating back 20 years. They’ve accumulated so much data that they’ve been able to create software to predict future errors
  4. Don’t just fix the mistakes - fix whatever permitted the mistake in the first place





Discussion

  • The process at NASA stifles creativity but is there not still a degree of creativity? Is creativity not involved in anything that requires change?
  • Creativity just happens differently - locked in early on
  • Not a normal industry
  • This makes sense in high risk industries e.g. pacemakers, nuclear plants
  • Some forced by regulation
  • May not work in other industries which need to adapt quickly, need to experiment, fail fast etc
  • Engineer who left the org did not enjoy working in the jockey, pizza environment as he had become indoctrinated in this culture
  • Quality, Cost, Time, Scope
  • Where are we with the variables
  • This org is optimizing?
  • Quality is fixed
  • Cost is a variable
  • Scope - Fixed primarily, overall goal stays constant
  • Time: Variable if necessary- not a free variable, they don’t want to use it as a variable but if they identify a flaw they will pull release date


Comments

Popular posts from this blog

Exercise: Prototyping and Creating Mock-Ups

We were tasked with designing a test-free search page mock-up for individuals who were unable to read. We were first required to create a paper prototype and then use an online tool, Balsamiq. I found the exercise very interesting as it forced me to refine all my ideas into one, single representation. It also involved selecting the most important requirements as we were under a time constraint. I found the paper prototype process slightly easier a using Balsamic introduced constraints, in that I had to create my design choosing from the icons within the Balsamiq tool as opposed to creating my own. I found this exercise very useful and I will aim to introduce quick prototyping in my future roles when applicable.

Week 2 Design thinking - Build the right thing

This week focused around building the thing right as opposed to building the right thing. Great design has always been concerned with the whole experience of interaction. One of the most interesting topics emerging from the class was prompted by a quote from Alan Cooper. It prompted discussion around what do you get when you cross a computer with a camera? A phone? A plane? With a car? A ship? You get a bigger computer.   The products we use on a daily basis are becoming ever more like software. Allen stressed that we need to develop an annoyance and radar for bad design and an appreciation for superior design. He showed us a variety of good and bad design examples and showed examples of how users will highlight the problems in your products or else they will leave marks e.g. a sign telling the user how to interact correctly with a product / service During the lecture, we also watched a video "Inside IDEO" which followed the IDEO design team revolutionizing the ...

Research Essay

A major assessment component for the Design, Development and Creativity module was conducting a research essay which involved working individually or in pairs. Myself and my partner, Beth conducted our research essay on updating a digital product, the UCD student portal through the introduction of a digital collaboration tool as a core offering for all students studying at the University. This essay involved conducting both primary and secondary research. In terms of primary research, we conducted a questionnaire, interviews and observational research to understand how students currently interact with the UCD student portal and how it can be improved. Once we understood the problems associated with blackboard and how it could be updated by making it a more engaging site, we conducted secondary research, studying existing literature and case studies on the topics of collaboration and utilising collaborative tools. Upon decision on the update required, a usability, requi...