minor update - code review or pull request workflow

initialcapacity · May 3, 2022 · 3675fbd · 3675fbd
1 parent 873cab3
commit 3675fbd
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 # Why pairing is faster
 
-A paper proving that pairing is faster than pull requests.
+A paper proving that pairing is faster than a code review or pull request workflow.
 
 Download the [latest draft](https://github.com/initialcapacity/why-pairing-is-faster/releases/latest/download/why-pairing-is-faster.pdf)
 of the paper.
@@ -18,8 +18,8 @@ We complete more features faster by pairing because the code reviews happen in p
 ## Summary 
 
 When paring, dependencies between stories in a backlog have less of an impact on team velocity.
-The impact of dependencies is much higher in a pull request workflow, meaning stories must be highly parallelizable
-to achieve the same productivity.
+The impact of dependencies is much higher in a code review or pull request workflow, meaning stories must be
+highly parallelizable to achieve the same productivity.
 
 ## Simulator
 

diff --git a/pairing.tex b/pairing.tex
@@ -182,7 +182,7 @@
     \section{Summary}\label{sec:summary}
 
     When paring, dependencies between stories in a backlog have less of an impact on team velocity.
-    The impact of dependencies is much higher in a pull request workflow, meaning stories must be highly parallelizable
-    to achieve the same productivity.
+    The impact of dependencies is much higher in a code review or pull request workflow, meaning stories must be
+    highly parallelizable to achieve the same productivity.
 
 \end{document}