Lecture 2 - SCRUM Flashcards
Rapid Application Development (RAD)
Objective: prodice useful software quiclkly (based on prototyping)
Software developed in increments providing new functionality
Alternative to waterfall in 80s/90s
RAD Characteristics
Specification, design, implementation are inteleaved
Software has a series of versions, with stakeholders involved in version evaluation
UI developed using an IDE and graphical toolset
Agile Methods
Reduce overheads in the software process
Respond quickly to changing requirements without excessive rework
- focus on code
- iterative approach
- working software, quickly
- evolve software to meet changing requirements
Agile manifesto
individuals and interactions > processes and tools
Working software > comprehensive documentation
Customer collaoration > contract negotiation
Responding to change > following a plan
Agile Principles
Customer Involvment
Incremental Delivery
People over Processes (team members should work with their strenghts, and not be stuck to processes)
Embrace change
Maintain Simplicity (eliminate complexity)
Where to apply Agile?
Small/Medium software. Small, integrated teams. Clear customer commitment and involvement. Not a lot of external rules and regulations that affect the software
Agile Dificulties
Keeping customer interest and team members collaboration high is hard.
Prioritizing changes in presence of multiple stakeholders.
Maintaining simplicity requires a lot of work
Contracts are not suitable, as they don’t account well for changes in requirements.
Documentation is less important, so if the original team cannot be maintained there may be problems in maintenance
Extreme Programming
Agile methods with extreme aproach to iterative development:
- New versions several times a day.
- Increments delivered to customers every 2 weeks.
- All tests must be run for evey build.
Very small and frequent system releases. Customer involvement is full time! Requirest constant refactoring to keep simplicity
