The document describes how PeerTransfer changed their development process from Scrum to Kanban. Some key issues with Scrum included developers having to switch contexts weekly and too many bugs to test within a sprint. With Kanban, work is pulled in a continuous flow through stages like development, code review, testing, and deployment. Kanban also uses work-in-progress limits to prevent bottlenecks and encourage pairing, and estimates to add planning structure while focusing in sprints. The team aims for quality with practices like test automation, feature reviews, and pair programming.

1. How we changed our development process at
PeerTransfer
FROM SCRUM TO KANBAN

2. ABOUT ME…
• @jokinaspiazu
• Fellow tester at peerTransfer since 2011
• Professional tester since 2008
• Blog: Tales of a fellow tester.
• Context Driven Tester* in Agile dev team**
• * As CDT as I manage to be.
• ** As Agile as we know how to be.

3. SCRUM
Two week sprint:
First week developing.
Second week testing.

4. SCRUM
Devs write code in local.
Deploy to Staging.
Test.
Deploy to Production.

5. SCRUM
Problem 1:
Devs had to switch context.

6. SCRUM
Problem 2:
Too many issues to test.

7. SCRUM
Problem 3:
Big issues to test.

8. KANBAN

9. peerTransfer Kanban board (previous versions)

10. current peerTransfer Kanban

11. peerTransfer Kanban issues.

12. peerTransfer Kanban issues.

13. peerTransfer Kanban issues.

14. Backlog: Review issues and question if we are fixing the right problem
Dev: Support developers understanding the problem we want to solv
Code Reviewed: 2 Devs think the code is good enough.
Dev Done: This just a buffer waiting queue.
In acceptance: Here is where I deploy and test the features.
Acceptance Done: Our waiting for deploy queue.
Shippable: Merged to Master and deployed to Staging.
Live: In production.

15. Kanban: Problems & Solutions
When we found out that every developer was working on his own
features.
We decided to set up a WIP limit, in Dev queue,
to encourage Devs to pair.

16. Kanban: Problems & Solutions
When we found out that we were working
on features with different focus.
e decided to work in Sprints, and focus every sprint to one subjec

17. Kanban: Problems & Solutions
It happened that when one queue got blocked, features would
pile on the previous one.
Solution: Add WIP limit for all queues,.

18. Kanban: Problems & Solutions
At some point, product management needed predictability
for planning sprints.
So we started estimating features.
Estimate as weather estimate, not as contract negotiation.

19. peerTransfer Dev Team
Quality & Process are owned by the team.
Features are reviewed before we start coding.
Developers write code in pairs doing TDD.
Code is reviewed by 2 other developers.
Features are deployed in test environments and tested.
Architecture in support of quality:
We automate all what we can…
Test environment setup, Unit test execution, Integration suites
even deploy scripts that can be invoked from chat tool.

20. There is no NEED of having a tester in a Agile team.
But when you have one, it’s so nice,
That devs don’t want to work without you.
Having a single tester is possible…
when the testing team is all the company.
peerTransfer Dev Team

21. hank you!