CIS 2250 Lecture 23: Design by Failure
8 Feb 2017
School
Department
Course
Professor
Document Summary
The problem is not the failure, the problem is what you do about it . Missing functionality - can"t make somethings work. Fragile - testing is incomplete and know bugs exist in the code. When you have fragile code, it"s usually because of a focus on functionality, and lack of focus on testing. Most likely it was because of a lack of planning. Usually a result of lack of planning. Often you don"t know it"s an assumption. You have to make an assumption -- and make sure everyone knows it. Don"t have enough information to make good decisions. Is the company you"ve been hired by thinking about changing platforms? (because they"re not going to tell you, you have to ask them explicitly) You need to work the teams background and experience. Ex: the team decides to use scrum, and you find out no one has used scrum.
