Waterfall
Waterfall V-Model
Agile comparison
Agile Manifesto
12 principles behind the Agile Manifesto can be split into 3 groups:
- Regular delivery of software
- Team communication
- Excellence in design
Our highest priority is to satisfy the customer through early and continues delivery of valuable software.
Delivery working software frequently (couple weeks - couple months), a preference is shorter timescale.
Working software is the primary measure of progress. (In Scrum the feature is DONE means it is potentially shippable).
=====
Business people and developers must work together daily. They should be available for each other.
Face-to-Face communication is a better way to convey the information.
Self-organised team gives the most valuable product.
Build projects around motivated individuals.
RETROSPECTIVE: At regular intervals, the team reflects on how to become more effective
======
Continuous attention to technical excellence and good design enhances agility.
Simplicity is essential. Do just what you need now, not in sometime in the future.
Welcome changing requirements, event in late development.
===== METHODOLOGIES OF AGILE =======
Scrum is a lightweight management framework.
Extreme programming is a disciplined approach at delivering high quality software quickly and continuously (delivery of 1-3 weeks).
Crystal methodology.
Dynamic Systems Development Method.
Feature Driven Design. (FDD) (time-lapse 2 weeks)
Kanban.
Extreme Programming
Rules: planning, managing, design, coding, testing
====
4 Activities: coding, testing, listening (customers & users), designing
5 Values: communication (f-2-f), simplicity (solving today's problem today), feedback, courage (realise issues and fix it), respect
3 Principles: feedback, assuming simplicity, embracing change
12 Practices /4 groups: fine-scale feedback (pair programming), continuous process, shared understanding, programmer welfare
29 Rules /5 groups: planning, managing, designing, coding
SCRUM
Split in 3 areas:
Roles: product owner (ussualy analist that communicate w/customer), scrum master (servant leader that fullfill the needs of the team), scrum team (5-9 people)
Ceremonies: sprint planning meeting, sprint review, sprint retrospective, daily scrum
Artifacts: product backlog, sprint backlog, burndown chart
======= DIFFERENCE between SCRUM and EXTREME PROGRAMMING ====
Scrum - has sprints from 2 weeks up to 1 month
XP - has iterations from 2 weeks
Scrum - teams do not allow changes into their sprints
XP - amenable to change within their iterations
Scrum - the team determine the sequence in which they will develop backlog items
XP - teams work in a strict priority order
Scrum - doesn't prescribe any engineering pactices
XP - prescribes many engineering practices like TDD, Pair Programming, Continuous Integration
In practice: team take Scrum, but adds some engineering practices from XP like TDD, Continuous integration, Code Review (instead of Pair Programming)
No comments:
Post a Comment