week 2 summary
Gergő Pintér, PhD
gergo.pinter@uni-corvinus.hu
evolution of software life cycle models (incomplete)
- software life cycle models
- waterfall
- V model
- iterative
- agile
- regarding to change management
waterfall model
- sequential, rigid model
- (originally) not possible to step back to a previous phase
- testing is after the implementation, errors are found late in the
process
- not possible to make changes during the development
- could take years
V model
- still rigid
- each phase has output and a review process
- errors are found at early stage
- decreases the risk of failure
- large to small: testing is done in a hierarchical perspective
iterative model
- software is built incrementally,
- with each iteration adding new features or refining existing
ones
- possible to get feedback after each iteration
- can be rigid within an iteration
agile model
- continuous collaboration and fast response to change, while the
iterative model takes a more gradual approach, building up the final
product over multiple iterations
- scrum is an agile methodology
scrum team
- optimally 3 to 9 people
- cross-functional
- self-organizing
roles
- scrum master
- responsible establishing scrum as defined in the Scrum Guide
- by helping everyone understand the theory and practice, both within
the scrum team and the organization
- responsible for the scrum team’s effectiveness
- product owner
- responsible for maximizing the value of the product resulting from
the work of the scrum team
- also responsible for effective product backlog management
- developers
sprint planning
- initiates the sprint
- maximum of eight hours for a one-month sprint
- define a sprint goal
- it is up to the developers how to turn product backlog items into
increments
![]()
sprint
- 1-4 week long
- considered a short project
- turns backlog items into increments
- includes daily scrum
![]()
sprint review
- scrum team presents the their work to the stakeholders
- the attendees collaborate on what to do next
- maximum of four hours for a one-month sprint
![]()
sprint retrospective
- concludes the sprint
- maximum of three hours for a one-month sprint
- the scrum team discusses what went well/bad, what problems
encountered
![]()
kanban
- uses a visual workflow
- pull-based system
- no task in the workflow without request
- uses columns for states of the product
- defines conditions when to move a task between columns
- conditions flow
- no iterations (sprints)
- no roles
- encourages to improve the workflow