I have a special interest in designing object-oriented architectures, distributed computing, projects that involve integration technologies, Continuous Integration as well as agile methodologies
About my experience pairing in features and bug end-to-end:
There is no sense about who is the coding since both are working together in the same code, switching idea all the time and the keyboard;
The idea about collective code increase a lot; There is no "my code" and yes "the code that we did";
We broke the pair times and times in one card when we notice that the next steps will be operational like repetitive tasks; (So, not 100% all the time)
Two eyes with different backgrounds help a lot to create a better solution, and believe, faster;
Islands of knowledge it really uncommon;
Yeah, I really recommend and I could say that the benefits could be noticed fast; Obviously that all the team should accept the idea to try it.
Thank yoi for sharing! I like the "our code" feeling.
I also wonder if you really measured velocity and saw it's higher? I imagined, based on other people opinions mostly, that velocity should drop. If you managed to speed up, it deserves a publication!
I have a special interest in designing object-oriented architectures, distributed computing, projects that involve integration technologies, Continuous Integration as well as agile methodologies
Yeah, I'll try write. :)
The count base where we could notice the velocity increase was points delivered of features vs bugs card in some short cycles.
It was not so evident in the first ~2 months about after that we could compare the numbers. It's a mindset change of the team but I truly believe worth it.
I have a recent really good example where I had pair with a team from another squad in a feature and the solution came up with an idea that I put on the desk and his as well. When we shared the solution with the team in a stand-up meeting that team was really surprised with the "out of box" solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sorry by the late message.
About my experience pairing in features and bug end-to-end:
Yeah, I really recommend and I could say that the benefits could be noticed fast; Obviously that all the team should accept the idea to try it.
If I could point to big themes should be:
=)
Thank yoi for sharing! I like the "our code" feeling.
I also wonder if you really measured velocity and saw it's higher? I imagined, based on other people opinions mostly, that velocity should drop. If you managed to speed up, it deserves a publication!
Yeah, I'll try write. :)
The count base where we could notice the velocity increase was points delivered of features vs bugs card in some short cycles.
It was not so evident in the first ~2 months about after that we could compare the numbers. It's a mindset change of the team but I truly believe worth it.
I have a recent really good example where I had pair with a team from another squad in a feature and the solution came up with an idea that I put on the desk and his as well. When we shared the solution with the team in a stand-up meeting that team was really surprised with the "out of box" solution.