Constantly delivering value: Shorten the loop in Sleekr.co

Constantly delivering value: Shorten the loop in Sleekr.co

Implementation agile, code review, TDD, Software Quality Assistance in Mekari.com in Sleekr Polaris team

E5bc4a2129918ed558e384010f86b621?s=128

Fachrul Ch

August 19, 2019
Tweet

Transcript

  1. 3.
  2. 7.

    Problem - Unmet SLA - Different product vision Product -

    Team bottleneck - Slow bug fixing Delivery
  3. 8.
  4. 9.

    “If you are the only person on your Scrum team

    that can do a particular job, you should be fired.” -- Jeff Sutherland
  5. 11.
  6. 12.

    UX Back-end Developer Quality Engineer Front-end Developer System Engineer Wireframing

    Write unit testing Functional testing Write unit testing DevOps Storyline Write production code Automated Test Write production code System and OS Design Design DB, System architecture Write test plan styling Web server ... ... ... ... ...
  7. 13.

    Benefits - No single point of failure - Everyone is

    replaceable - Knowledge sharing - Collaboration
  8. 17.

    - Long-lived Pull Request - Just “approve” - Too focus

    on small detail - Review-is-not-my-job mindset - Longer development process Pitfall codeReview
  9. 18.

    What we do - Small PR (and commit) - Keep

    in sync - PR description (checklist) - Merge yours - STOP starting, START finishing
  10. 19.

    Problems - Too many bugs - Staging server bottleneck Product

    Infra - QA bottleneck - Tricky refactoring Delivery
  11. 20.
  12. 22.

    Backlog Grooming: - Understanding - Questioning Why - How to

    test Sprint Planning: - Affect regression - Acceptance criterias - Automatio, what level - Test data/environment During sprint: - Pair with dev - Definition of done - Finding value of quality - Design experiments to improve quality Daily Scrum: - Asking the right questions, solving the right problems - Seek confusion Review: - Usability test - Solve the business problem
  13. 23.

    • Competencies vs Roles • Testing is an activity •

    More effort testing the product conceptually at the start, the less effort manual testing at the end Quality Assistance
  14. 24.
  15. 26.
  16. 31.
  17. 33.
  18. 34.

    Key Takeaway - Start collaborating - Adopt slowly - Stick

    to standard - Automate the repetitive - Write test - Deploy != release
  19. 35.

    Further reading • https://anchor.fm/penguji • Atlassian’s Quality Assistance: ◦ https://www.atlassian.com/blog/inside-atlassian/jira-qa-process

    ◦ https://www.atlassian.com/inside-atlassian/quality-assurance-vs-quality-assistance ◦ https://www.atlassian.com/inside-atlassian/software-QA-skills ◦ Quality at Speed, How JIRA Does QA - Webinar https://www.youtube.com/watch?v=yRP29wFqu20 ◦ The Future of QA at Atlassian - Atlassian Summit https://www.youtube.com/watch?v=9giJYYag6wQ • Spotify’s Quality Assistance: ◦ https://www.cs.tut.fi/tapahtumat/testaus12/kalvot/Karl_ta.pdf ◦ https://www.slideshare.net/javimosca/bug-prevention-at-spotify
  20. 37.

    END