Software Engn 1 Syst Analysis
Software Engn 1 Syst Analysis CSIS 360
Popular in Course
Popular in Computer Information Systems
This 2 page Class Notes was uploaded by Laurianne White MD on Monday October 12, 2015. The Class Notes belongs to CSIS 360 at Fort Lewis College taught by Brian Hanks in Fall. Since its upload, it has received 27 views. For similar materials see /class/221847/csis-360-fort-lewis-college in Computer Information Systems at Fort Lewis College.
Reviews for Software Engn 1 Syst Analysis
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 10/12/15
CSIS 360 Lecture 17 Classic Mistakes A typical software project can present more opportunities to learn from mistakes than some people get in a lifetime So did anyone try to identify the classic mistakes as you read the case study Scope creep approved project much larger than original proposal Wishful Thinking schedule shorted based on desire rather than reality More work in less time Expectation that new technology would result in signi cant productivity improvements Poor hiringpersonnel practices Lack of proj ect management monitoring Tool and requirements don t match Overwork stress tiny bonus management vacation 9 impact on morale Quality shortcutsno inspections General mismanagement Not tracking requirements to actual work CodingTesting departments as adversaries instead of cooperating organizations Waterfall lifecycle 7 can t release to testing until nearly done As you were reading the scenario did any particular scenes or actions jump out at you as particularly noteworthy surprising or unbelievable If these are classic mistakes in the sense that they have been made so often everyone knows about them and they have predictable bad results why do organizations still make them They have seductive appeal For example 0 Add more people to a late project 7 it just sounds good Problem more communication everyone else has to help bring new people up to speed Keep someone on the project even if the other developers nd him impossible to work with 7 he s contributing and we can t afford not to have that work done Problem he s slowing everyone else down 0 Avoiding these classic mistakes won t guarantee rapid development but making them will prevent it Number 1 reason projects succeed Standish Group 1994 User Involvement How does this relate to the process you choose Have you seen any of these common practices Which practices do you think are the worst Can you think of any other mistakes that you would add to this list Using wrong technology or trying to force the technology to do things it wasn t designed to do report writer in case study Using wrong process Did you notice that most of the mistakes were related to people and process I think all of these can be considered as management mistakes at some level
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'