Agile vs Fragile - Summary

agile-vs-fragile-summary.md

Agile vs Fragile - Summary

My personal notes on Brian Copeland's blog series: Agile vs Fragile

(If you are unable to access the blog post, try using a US proxy or web-based proxy service e.g. http://hideme.be)

1) Deliver value to customer

• Agile: focus on deliver valuable software to customer
• Fragile: focus on meeting delivery period

2) Welcome changing requirements

• Agile: change is managed
• Fragile: change happens

3) Deliver frequently

• Agile: deliver small but valuable items fast
• Fragile: deliver fast, even defective/not valuable items

4) Business people and developers work together, 5) Face-to-face interaction

• Agile: constant interaction
• Fragile: same place, but work alone

6) Motivated individuals given with env, support & trust.

• Agile: team members are self directed
• Fragile: management burnout team members to meet timeline

7) Working software = measures of progress

• Agile: define done-done, quality over schedule, doesn't ship if not working
• Fragile: schedule over quality, ship and repair later

8) Sustainable development

• Agile: focus on winning the marathon, not individual sprints, keep team fresh
• Fragile: burn out team members to deliver each sprint.

9) Technical discipline matters

• Agile: use process & design to drive quality
• Fragile: eliminate process & design to drive speed

10) Simplicity

• Agile: find simplest solution with quality; use simple processes
• Fragile: find fastest solution; eliminate processes e.g. tests

11) Self-organizing team

• Agile: permitted to make errors; towards same goal, jump in to help other project roles
• Fragile: blame game, confrontation by management; not crossing the project role boundary

12) Retrospective frequently and adjust accordingly

• Agile: Retrospective review on strengths, weaknesses; Adjust processes in next sprint
• Fragile: No review or become blame game, and no action taken.