Slow Down
Why should you slow down?
Myth: A Fast Developer is a Good Developer
Project Velocity
Perceived Velocity
Actual Velocity
Ideal Velocity
Project Momentum
What don’t you do when you work too fast?
Don’t Live with Broken Windows
Comment First
Refactor Continuously
Test Driven Development
Never Stop Learning
How can you slow down?
Insist on Formal Specifications
Estimating
The End
Upcoming SlideShare
Loading in …5
×

Danny Patterson: Slow Down

659 views
623 views

Published on

It's been beaten into the heads of developers for years; faster is better. Why should developers be judged by how quickly they solve problems and not how well they solve problems? This presentation will analyze the problems with working to fast and why you and your team should slow down.

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

No Downloads
Views
Total views
659
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
6
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Danny Patterson: Slow Down

  1. 1. Slow Down
  2. 2. Why should you slow down?
  3. 3. Myth: A Fast Developer is a Good Developer
  4. 4. Project Velocity
  5. 5. Perceived Velocity
  6. 6. Actual Velocity
  7. 7. Ideal Velocity
  8. 8. Project Momentum
  9. 9. What don’t you do when you work too fast?
  10. 10. Don’t Live with Broken Windows
  11. 11. Comment First
  12. 12. Refactor Continuously
  13. 13. Test Driven Development
  14. 14. Never Stop Learning
  15. 15. How can you slow down?
  16. 16. Insist on Formal Specifications
  17. 17. Estimating
  18. 18. The End

×