EBTM 337 Lecture Notes - Lecture 9: Systems Development Life Cycle, Continuous Delivery, Breakcore

• School: Towson University
• Department: e-Business and Technology Management
• Course: EBTM 337
• Professor: Projilia

Document Summary

Chapter 9: systems development and project management: corporate responsibility. As an organizations" reliance on software grows, so do the business-related consequences of software successes and failures including: *advocates frequent (cid:498)releases(cid:499) in short development cycles which is intended to improve in a gate waiting for the stakeholder"s analysis, and then it either moves to the next gate or development of software into four (cid:498)gates(cid:499) *each gate consists of executable iterations of the software in development. *under this methodology, each day ends or begins with a stand-up meeting to monitor and control the development effort. Iterative development- consists of a series of tiny projects. Prototype- a smaller-scale representation or working model of the users" requirements or a proposed design for an information system *essential part of the analysis phase when using a rad methodology. Failure to manage project scope: scope creep, feature creep.