Phpnw11 - Uncon

975 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
975
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Kwaliteitsmanagement / Quality Assurance / QA Ervoor zorgen dat kwaliteit op een bepaald niveau blijft Hoe definieren we het niveau? (perfectionistisch, aanpassen nav nieuwe inzichten) Context (in alle onderdelen van het ontwikkelproces) Eerst zorgen dat het niveau gehaald wordt Dan zorgen dat het niveau gehandhaafd blijft Waarom? Wat gaat er mis? Elk bedrijf anders, maar algemene problemen zijn: teveel bugs na oplevering aan klant, functionaliteiten worden niet gerealiseerd zoals klant bedoeld heeft, er is geen standaard manier van werken, ontbrekende documentatie, veel legacy code Efficienter werken is tijd besparen en dus ook een vorm van kwaliteitsverbetering
  • Uitkijken voor terugval momenten
  • Phpnw11 - Uncon

    1. 1. Introducing Quality Management - A practical approach Lineke Kerckhoffs-Willems @the_linie [email_address] http://joind.in/3813
    2. 2. Agenda <ul><li>About me
    3. 3. Quality Management
    4. 4. Approach
    5. 5. Possible improvements
    6. 6. Questions </li></ul>
    7. 7. About me <ul><li>Working as Quality Manager at Compo Software
    8. 8. Over 9 years experience with PHP
    9. 9. Member of PHPWomen
    10. 10. Conference attendee
    11. 11. Blogger: www.phpassionate.com
    12. 12. Twitter: @the_linie and @phpassionate </li></ul>
    13. 13. Quality Management <ul><li>What is quality management?
    14. 14. Two sides </li><ul><li>Improvement
    15. 15. Monitoring </li></ul><li>Why do you need Quality Management? </li></ul>
    16. 16. Approach – Preparation <ul><li>Role assignment </li><ul><li>Responsibilities
    17. 17. Task assignment </li></ul><li>Risks </li><ul><li>Platform
    18. 18. Planning
    19. 19. The customer </li></ul></ul>
    20. 20. Approach – creating a platform <ul><li>Management </li><ul><li>Emphasize which issues will be solved
    21. 21. Be honest </li></ul><li>Fellow developers </li><ul><li>Make sure they have enough time
    22. 22. Efficiency, structure, readability
    23. 23. Emotion
    24. 24. Self exploring </li></ul></ul>
    25. 25. <ul><li>Identify possible improvements
    26. 26. Prioritise and determine order of implementation </li></ul>Approach – The first step What Duration of implementation Priority Advantages Depen-dencies Order Functional design 1 month 2 Clarity 1 Technical design 1 month 1 Clarity Documentation 1 2
    27. 27. Approach – Deming circle
    28. 28. Approach – Plan <ul><li>SMART </li><ul><li>Specific
    29. 29. Measurable
    30. 30. Acceptable
    31. 31. Realistic
    32. 32. Time </li></ul></ul>
    33. 33. Possible improvements <ul><li>Development lifecycle
    34. 34. Documentation
    35. 35. Version Control System
    36. 36. Coding standards
    37. 37. Deployment strategy
    38. 38. Framework choice
    39. 39. Automated tests </li></ul>
    40. 40. ? Lineke Kerckhoffs-Willems @the_linie [email_address] http://joind.in/3813
    41. 41. Thank you! Lineke Kerckhoffs-Willems @the_linie [email_address] http://joind.in/3813
    42. 42. Image credits <ul><li>Deming circle: &quot;Diagram by Karn G. Bulsuk (http://blog.bulsuk.com)&quot; </li></ul>

    ×