CIS 1250 Lecture Notes - Lecture 9: Customer Satisfaction, Sustainable Development, Predictive Modelling
Document Summary
Reaction to previous methods, such as waterfall. Individuals and interactions over process and tools: working software is more important than comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan. Twelve principles of agile software development: customer satisfaction through rapid delivery of useful software. Shorter period between requirements gathering and customer feedback: welcome changing requirements, even late in development. No need to wait for redesign or a new system to be built. Shorter or no delays when a requirement changes. Features can be reordered or dropped: working software is delivered frequently. Shortens the time between planning and delivery. The team operates in iterations or sprints. Opportunities to improve the efficiency and effectiveness of producing the software: working software is the principle measure of progress. Producing quality software that the customer wants: sustainable development, able to maintain a constant pace. Teams (voting) establish a maintainable speed: close, daily cooperation between business and developers.