Successful development without QA

2,536 views

Published on

How to bring out potential of developers?

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,536
On SlideShare
0
From Embeds
0
Number of Embeds
95
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Successful development without QA

  1. 1. Pavel Gabriel coach, programmer, agile-evangelist alovak@gmail.com Monday, October 11, 2010
  2. 2. Successful development without QA team By CharlotteSpeaks♥{Charlotte.Morrall} Monday, October 11, 2010
  3. 3. Your dev team doesn't provide sufficient product By Gabriel Pollard Monday, October 11, 2010
  4. 4. Boss says: several testers will solve our problems Monday, October 11, 2010
  5. 5. You don't want extra departments and processes Monday, October 11, 2010
  6. 6. ? Hire testers or Perfect the team? Monday, October 11, 2010
  7. 7. More than 90% of tester jobs require technical skills Monday, October 11, 2010
  8. 8. C/C++/J2EE/Perl/Ruby/ Python/Network Monday, October 11, 2010
  9. 9. You'd like to increase quality to make your boss happy Monday, October 11, 2010
  10. 10. You decided to perfect the existing team Monday, October 11, 2010
  11. 11. Monday, October 11, 2010 ? How?
  12. 12. 1 2 3 Responsibility Awareness Communication Monday, October 11, 2010
  13. 13. 1 Responsibility Monday, October 11, 2010
  14. 14. ? Problems with responsibility Monday, October 11, 2010
  15. 15. Who is responsible for the quality? Monday, October 11, 2010
  16. 16. Whole team is responsible Monday, October 11, 2010
  17. 17. You are responsible Monday, October 11, 2010
  18. 18. How to make developers more responsible? Monday, October 11, 2010
  19. 19. Teach the developers to be responsible Ask  ques)ons Monday, October 11, 2010
  20. 20. One day... Monday, October 11, 2010
  21. 21. What are you going to do about it? -­‐  I’m  but  one  developer Monday, October 11, 2010
  22. 22. What change can you make? -­‐  I  can  help  colleagues Monday, October 11, 2010
  23. 23. So, what are you going to do? -­‐  I  will  prepare  presenta)on Monday, October 11, 2010
  24. 24. Practices to  boost  responsibility Monday, October 11, 2010
  25. 25. Code review Monday, October 11, 2010
  26. 26. Demonstrations Monday, October 11, 2010
  27. 27. 2 Awareness Monday, October 11, 2010
  28. 28. Monday, October 11, 2010 ? Problems with awareness Developers  are  tolerant
  29. 29. Underperformance Monday, October 11, 2010
  30. 30. Bugs Monday, October 11, 2010
  31. 31. Bad communication Monday, October 11, 2010
  32. 32. Aware developers can cope with any problems Monday, October 11, 2010
  33. 33. Teach the developers to be awareness Ask  ques)ons Monday, October 11, 2010
  34. 34. One day... Monday, October 11, 2010
  35. 35. Why did you fail to do that? -­‐  I  could  not  test Monday, October 11, 2010
  36. 36. Why did you write this kind of test? -­‐  We  have  been  always  tes)ng   such  way Monday, October 11, 2010
  37. 37. What else can you do? -­‐  I  don’t  know Monday, October 11, 2010
  38. 38. What could help you? -­‐  I  need  suitable  tes)ng  tool Monday, October 11, 2010
  39. 39. What are you going to do about it? -­‐  I’m  going  to  find  it  and  use  it. Monday, October 11, 2010
  40. 40. Practices can  complement  ques)ons Monday, October 11, 2010
  41. 41. TDD/BDD Test  Driven  Development Behavior  Driven  Development Monday, October 11, 2010
  42. 42. ATDD Acceptance  test-­‐driven  development Monday, October 11, 2010
  43. 43. Retrospectives to  improve  process  and  discover  tools Monday, October 11, 2010
  44. 44. 3 Communication Monday, October 11, 2010
  45. 45. ? Problems with communication Monday, October 11, 2010
  46. 46. What does a developer need? to  do  his  work  effec)vely Monday, October 11, 2010
  47. 47. Vision purposes,  target  audience,  use  cases Monday, October 11, 2010
  48. 48. Knowledge peculiari)es  of  business  domain   per)nent  stories Monday, October 11, 2010
  49. 49. Feedback Monday, October 11, 2010
  50. 50. Practices to  improve  communica)on Monday, October 11, 2010
  51. 51. Standup meetings Monday, October 11, 2010
  52. 52. Company meetings to  see  internal   processes  and  needs Monday, October 11, 2010
  53. 53. Demonstrations to  get  a  feedback Monday, October 11, 2010
  54. 54. Support done by developers to  understand  real  needs  and   problems  of  the  users Monday, October 11, 2010
  55. 55. 1 2 3 Responsibility Awareness Communication Monday, October 11, 2010
  56. 56. Monday, October 11, 2010 ?Questions? Pavel  Gabriel alovak@gmail.com
  57. 57. Thank you! Monday, October 11, 2010

×