So youthinkyoucanchange?<br />Anders Sveen<br />JavaZone 2010<br />
agile<br />
change<br />
responding to change over following a plan- agile manifesto<br />
Plans are worthless. Planning is essential.- Dwight D. Eisenhower, general and president (1890-1961)<br />
continiouslearning<br />
experience<br />
changesyourview<br />
howsupportchange?<br />
stand up<br />
backlog<br />
discoverchange<br />
theuser story is alreadyapproved<br />
the database can’t be altered<br />
theinterface is locked<br />
thechange is toobig<br />
preventing, stopping or minimizingchange<br />
smallest change<br />
shortcuts<br />
change is an opportinity<br />
change must be as easy as possible<br />
Automated testing<br />Yoursafetynet<br />
safety<br />
quality in tests<br />
quality in your test data<br />
tests thatarewilling to change<br />
yoursafetynetbecomes an obstacle<br />
Codethat’swilling to change<br />Quality matters<br />
quality<br />
evolvable design<br />
knowledge, experience and discipline<br />
shortcuts and bad design<br />
encapsulation<br />
real objectoriented design<br />
good tests<br />
test data<br />
Change is hard<br />
experience, knowledge and focus<br />
try, try and tryagain<br />
it pays off<br />
water fall or agile?yourchoice<br />
http://smidig2010.no<br />anders.sveen@capgemini.com / http://blog.f12.no / @anderssv<br />
Upcoming SlideShare
Loading in …5
×

So you think you can change? - JavaZone 2010

1,191 views

Published on

Change is not about process, but about culture and mind set.

JavaZone 2010 lightning talk

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
1,191
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

So you think you can change? - JavaZone 2010

  1. 1. So youthinkyoucanchange?<br />Anders Sveen<br />JavaZone 2010<br />
  2. 2. agile<br />
  3. 3. change<br />
  4. 4. responding to change over following a plan- agile manifesto<br />
  5. 5. Plans are worthless. Planning is essential.- Dwight D. Eisenhower, general and president (1890-1961)<br />
  6. 6. continiouslearning<br />
  7. 7. experience<br />
  8. 8. changesyourview<br />
  9. 9. howsupportchange?<br />
  10. 10. stand up<br />
  11. 11. backlog<br />
  12. 12. discoverchange<br />
  13. 13. theuser story is alreadyapproved<br />
  14. 14. the database can’t be altered<br />
  15. 15. theinterface is locked<br />
  16. 16. thechange is toobig<br />
  17. 17. preventing, stopping or minimizingchange<br />
  18. 18. smallest change<br />
  19. 19. shortcuts<br />
  20. 20. change is an opportinity<br />
  21. 21. change must be as easy as possible<br />
  22. 22. Automated testing<br />Yoursafetynet<br />
  23. 23. safety<br />
  24. 24. quality in tests<br />
  25. 25. quality in your test data<br />
  26. 26. tests thatarewilling to change<br />
  27. 27. yoursafetynetbecomes an obstacle<br />
  28. 28. Codethat’swilling to change<br />Quality matters<br />
  29. 29. quality<br />
  30. 30. evolvable design<br />
  31. 31. knowledge, experience and discipline<br />
  32. 32. shortcuts and bad design<br />
  33. 33. encapsulation<br />
  34. 34. real objectoriented design<br />
  35. 35. good tests<br />
  36. 36. test data<br />
  37. 37. Change is hard<br />
  38. 38. experience, knowledge and focus<br />
  39. 39. try, try and tryagain<br />
  40. 40. it pays off<br />
  41. 41. water fall or agile?yourchoice<br />
  42. 42. http://smidig2010.no<br />anders.sveen@capgemini.com / http://blog.f12.no / @anderssv<br />

×