Differences

This shows you the differences between two versions of the page.

--- start [2024/01/29 01:42] – [Problem Statement] 202.186.106.100
+++ start [2024/01/29 02:07] (current) – [Phase 2: Scrum pilot - 3 months (5 sprints x 2 weeks each)] 202.186.106.100
@@ Line 22: / Line 22: @@
 Scrum promotes self-organising teams, fosters ownership, accountability, and collaboration. Scrum empowers teams to make decisions and have ownership over their work. This leads to increased engagement, enthusiasm, and a sense of accomplishment.
-Benefits of cross-functional teams and how they eliminate silos, leading to smoother workflows.
+The cross-functional nature of Scrum teams help eliminate silos, leading to smoother workflows.
-Scrum's regular meetings and artifacts (like Product Backlog and Sprint Backlog) ensure everyone has a clear view of progress and priorities.
+To foster cadence, Scrum's regular meetings and artifacts (like Product Backlog and Sprint Backlog) ensure everyone has a clear view of progress and priorities.
@@ Line 33: / Line 33: @@
   * Identify 3 staff to draw up plans
   * Attend [[https://www.sutd.edu.sg/Admissions/Academy/Our-Offerings/Short-Courses/scrum-alliance/Certified-Scrum-Product-Owner|CSPO (Certified Scrum Project Owner) course]]
-  * Appoint Product Owner to seek feedback and [[https://youtu.be/502ILHjX9EE?si=YX7r7nG2JxQdVvny|draws up Product and Sprint Backlogs]] comprising User stories
+  * Appoint a Product Owner to seek feedback and [[https://youtu.be/502ILHjX9EE?si=YX7r7nG2JxQdVvny|draws up Product and Sprint Backlogs]] comprising User stories
-  * Appoint Scrum Master to attend [[https://www.sutd.edu.sg/Admissions/Academy/Our-Offerings/Short-Courses/scrum-alliance/Certified-Scrum-Master|CSM (Certified Scrum Master) course]]
+  * Appoint a Scrum Master to attend [[https://www.sutd.edu.sg/Admissions/Academy/Our-Offerings/Short-Courses/scrum-alliance/Certified-Scrum-Master|CSM (Certified Scrum Master) course]]
   * Recruit another upto 6 staff/developers to form pilot Scrum team
-==== Phase 2: Scrum pilot - 3 months (5 sprints x 2 weeks each)  ====
+==== Phase 2: Scrum pilot - 3 months (6 sprints x 2 weeks each)  ====
-In each 2-week sprint (i.e. 10 working days), there is a "cadence" of activities that happen. It is very important to have the whole team physically seated together to foster team cooperation, reduce "silo" behaviour, and allow any simmering issue to surface quickly to be resolved.
+In each 2-week sprint (i.e. 10 working days), there is a "cadence" of activities that happen. It is important to have the whole team physically seated together, away from their respective "WoW", to foster team cooperation, reduce "silo" behaviour, and allow any simmering issue to surface quickly to be resolved.
-  * **Day-1:** (4 hours) Pilot Scrum Team conducts Sprint Planning
+  * **Day 0 or minus 1:** (4 hours) Pilot Scrum Team conducts Sprint Planning
     * Product Owner presents Product and Sprint Backlog for discussion
     * Team estimates "story points" and agrees to Sprint Backlog (i.e. scope of work)
   * **Days 1 to 9:**
-    * Scrum Master conducts Daily Stand-ups every morning (15 mins): Every team member answer 3 questions:
+    * Scrum Master conducts Daily Stand-ups every morning (15 mins): Every team member answers 3 questions:
       * What did you do yesterday?
       * What are you planning to do today?
@@ Line 56: / Line 56: @@
     * Sprint 2 Planning: See Day-1, iterate
-At the end of each Quarter (i.e. every 3 months), it is a good practice to tally up what has been done, achieved, improved and learnt. To consider whether, and how, to take this initiative forward, as well as if any additional resources/support is needed.
+At the end of each Quarter (i.e. every 3 months, approximately 6 sprints), it is a good practice to tally up what has been done, achieved, improved and learnt. To consider whether, and how, to take this initiative forward, as well as if any additional resources/support is needed.
 ==== Phase 3: Embrace and Extend - 6 months ====