Intention Driven Pairing: A Daily Workflow for Effective Pairing
•Download as PPTX, PDF•
0 likes•396 views
A recent article I wrote on this practice: https://www.connected.io/post/delivering-better-products-through-intention-driven-pairing
More Related Content
Viewers also liked
Viewers also liked (15)
Similar to Intention Driven Pairing: A Daily Workflow for Effective Pairing
Similar to Intention Driven Pairing: A Daily Workflow for Effective Pairing (20)
Recently uploaded
Recently uploaded (20)
Intention Driven Pairing: A Daily Workflow for Effective Pairing
- 1. Intention Driven Pairing A Daily Workflow for Effective Pairing sobes paulsobes@nulogy.com
- 2. Intention Driven Pairing A Daily Workflow for Effective Pairing sobes paulsobes@nulogy.com
- 4. 1: Set Expectations 2: Work in Pomodoros 3: Close with a Retrospective
- 5. 1: Set Expectations 2: Work in Pomodoros 3: Close with a Retrospective 1: Set Expectations
- 6. 1: Set Expectations 1. Sync on Tasks and Time 2. Set Learning Goals
- 7. 1.1: Sync on Tasks and Time
- 8. “I want to become more efficient at coding through the use of tools and shortcuts” “I want to get more comfortable with JavaScript TDD” 1.2: Set Learning Goals
- 9. 1: Set Expectations 2: Work in Pomodoros 3: Close with a Retrospective 1: Set Expectations 2: Work in Pomodoros
- 10. 2: Work in Pomodoros ● A defined period of time (e.g. 25 minutes) ● Aim for uninterrupted focus ● Interrupts are deliberate and intentional ● If interrupted, decide whether to switch context ● If context is switched, pomodoro is abandoned
- 12. Different Levels of Tracking
- 13. 1: Set Expectations 2: Work in Pomodoros 3: Close with a Retrospective 3: Close with a Retrospective 2: Work in Pomodoros
- 14. 3: Close with a Retrospective 1. Share Constructive Criticism 2. Set The Stage For Tomorrow
- 15. “I get disengaged when I navigate for more than 3 pomodoros in a row. Next time, can we try switching more often?” “Relying on console.log really slowed us down. Next time, can we try setting breakpoints using Chrome dev tools?” 3.1: Share Constructive Criticism
- 16. 3.2: Set The Stage For Tomorrow “Who will we need feedback from?” “How many more days until we integrate?” “Are we still on track for the iteration?” “Are we ready to rotate pairs?”
- 17. 1: Set Expectations 2: Work in Pomodoros 3: Close with a Retrospective
- 18. How Do I Start? ● Pick and tweak parts that work ● Try it on your own first ● Find advocates on your team ● “It’s just an experiment”
- 19. twitter: @sobes email: paulsobes@nulogy.com Thank You! Questions?
Editor's Notes
- Mini-survey. Show of hands: Who has tried pair programming? Who practices pair programming regularly? Who feels like they should pair more? Who feels like they can get more out of pairing? You guys are perfect for this presentation.
- I work at a company called Nulogy. At Nulogy, pair programming is the default. That means, coding alone is uncommon. Personally, it took me some time to adapt to this. Sometimes, I felt like my pairing experience could be better. Over time, I also realized that I wasn’t the only one who felt this way. Through iteration retrospectives, our team has developed a pairing workflow to help optimize our pairing experience. This is what I’d like to share with you about today. (click). (walk through as though we were following the workflow today) PRACTICE THIS SLIDE
- We do this at the start of the day. TWO PARTS. sync on tasks and time set learning goals
- After pairing up… Review TODO list together Flag work that we expect to get done today. Compare calendars, find gaps in your calendars that you can pair together. Even a half hour of pairing in a whole day can be valuable.
- better use of tools JS TDD
- What does this mean? Summarizing it in FIVE points: A defined period of time (e.g. 25 minutes) Aim for uninterrupted focus Interrupts are deliberate and intentional If interrupted, decide whether to switch contexts If context is switched, pomodoro is abandoned PRACTICE THIS SLIDE
- Most importantly: Use a timer! Here’s the traditional version. We have an app that we built in-house on one of our hack days (click) Take a 5 minute break after each pomodoro. After a few pomodoros ,take a longer break (10 minutes). It’s totally up to you how to structure the duration of the work and the breaks. The point is to be intentional about both. No checking email, slack, etc during the pomodoro! Save it for the break.
- Now that we’re working in pomorodos, it is much easier to track our work Simple: Count number of pomodoros completed / interrupted / abandoned in a day Detailed: Make notes after each pomodoro Again, it’s whatever works for your individually, or for your team. Even the minimal tracking can yield insights. Why didn’t I get more done today? Maybe because I was interrupted 25 times today. How long did that defect REALLY take to fix?
- A chance to reflect on the day. TWO PARTS. Share Constructive Criticism Set The Stage for Tomorrow Be intentional about how long the retro will take: 30 seconds or 10 minutes. Even a 30 second retro can be hugely beneficial.
- navigating too long console.log
- feedback? when integrate? on track? rotate?
- ideally, outcomes the retro feed into expectations for the next day. so the daily workflow is actually a cycle.
- FOUR THINGS to keep in mind Pick and tweak parts that work (we started w/ daily retro) Try it on your own first Find advocates on your team It’s just an experiment. Now I invite you to experiment with your own daily workflow. Enjoy!