You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello, Tech enthusiasts! Are you ready for October to begin 🙀?
I wanted to share with you an Article I came across from Work/Life (The Atlassian blog) from a senior developer on the Jira team about the tools and techniques that make remote pair programming successful.
In the article, they talk about why you should try remote pair programming, how to get started, tools of the trade, etc. If you have any thoughts on the piece, leave them in the comments below - I'm interested to hear about your experience with remote pair programming!
Read the full article on the Atlassian blog
Cheers,
Bridget
Oh, sweet! Let me know if anyone has any feedback :). Also, feel free to invite your team to this group!
I haven't been involved in any way with RPP. However, I have found it mentioned more and more w/in the Community of late. Mostly around the sensitive topic of not being able to assign issues to a team.
Hi @Jack Brickey -- I wonder if what you note is one of the aspects of doing the work: selection versus implementation.
For selection, we could have push (leader assigned work) or pull (self-assigned work).
And implementation could be how the team delivers it: solo people in a cave/cubicle, pairing, mobbing, etc., co-located or remote or a mix.
Both (selection and implementation) need to deal with accountability, and I have definitely noted chatter about accountability sliding with remote work...especially when leader expectations were not aligned with teams before "everyone-work-from-home" times started.
Best regards,
Bill
Thanks for sharing, @Bridget