From f11c17059b36060f6094ce5665b6164f1f6f8c2c Mon Sep 17 00:00:00 2001
From: Moquan Chen <mq.chen@gmail.com>
Date: Thu, 3 Oct 2019 11:41:51 +0200
Subject: [PATCH 1/2] Added The Product Manager way

---
 README.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/README.md b/README.md
index 77a49a5..160b903 100644
--- a/README.md
+++ b/README.md
@@ -310,3 +310,23 @@ $ disown
 Now it's not your problem anymore.
 Process will close automatically upon next reboot/shutdown.
 
+## The Product Manager way
+Credit: @mqchen
+
+1. Create new Jira issue.
+1. Set priority to A - Critical.
+1. Assign to random team member.
+
+## The Experienced Product Manager way
+Credit: @mqchen
+
+1. Create new Jira issue.
+1. Set priority to A - Critical, Epic link and Components.
+1. Write Given-When-Then acceptance criteras.
+1. Schedule estimation workshop meeting.
+1. Conduct estimation meeting with Planning Poker cards.
+1. Prioritize in next sprint.
+1. Assign to random team member.
+1. Conduct acceptance test.
+1. Review burn down chart together with the team.
+1. Schedule retrospective.

From 10248f9d254d24904b4236b2951ae2b6dda01912 Mon Sep 17 00:00:00 2001
From: "Luke Stephens (hakluke)" <13975395+hakluke@users.noreply.github.com>
Date: Thu, 3 Oct 2019 21:15:35 +1000
Subject: [PATCH 2/2] Update README.md

---
 README.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 160b903..bbea0b3 100644
--- a/README.md
+++ b/README.md
@@ -314,19 +314,19 @@ Process will close automatically upon next reboot/shutdown.
 Credit: @mqchen
 
 1. Create new Jira issue.
-1. Set priority to A - Critical.
-1. Assign to random team member.
+2. Set priority to A - Critical.
+3. Assign to random team member.
 
 ## The Experienced Product Manager way
 Credit: @mqchen
 
 1. Create new Jira issue.
-1. Set priority to A - Critical, Epic link and Components.
-1. Write Given-When-Then acceptance criteras.
-1. Schedule estimation workshop meeting.
-1. Conduct estimation meeting with Planning Poker cards.
-1. Prioritize in next sprint.
-1. Assign to random team member.
-1. Conduct acceptance test.
-1. Review burn down chart together with the team.
-1. Schedule retrospective.
+2. Set priority to A - Critical, Epic link and Components.
+3. Write Given-When-Then acceptance criteras.
+4. Schedule estimation workshop meeting.
+5. Conduct estimation meeting with Planning Poker cards.
+6. Prioritize in next sprint.
+7. Assign to random team member.
+8. Conduct acceptance test.
+9. Review burn down chart together with the team.
+10. Schedule retrospective.