User Tools

Site Tools


start

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start [2024/01/18 09:52] – [Phase 2: Scrum pilot - 3 months (5 sprints x 2 weeks each)] 219.74.112.242start [2024/01/29 02:07] (current) – [Phase 2: Scrum pilot - 3 months (5 sprints x 2 weeks each)] 202.186.106.100
Line 4: Line 4:
 ===== Problem Statement ===== ===== Problem Statement =====
  
-Most companies are hierarchical. Managers make decisions which are cascaded down the ranks to be carried out. While feedback is often encouraged, responsibility often remains with the manager. The subordinate accepts that his boss can overrule any suggestion. Afterall, that's why bosses are paid more for.+Most companies are hierarchical. Managers make decisions which are cascaded down the ranks to be carried out. While feedback is often encouraged, responsibility almost always remains with the manager. The subordinate accepts that his boss can overrule any suggestion. Afterall, that's why bosses are paid more for.
  
-A sense of ownership is a powerful motivator for inspiring extraordinary work performance. If the norm is a traditionally top-down approach in the company, it is difficult to convince staff that any change is good, will be recognised and beneficial for all in the long run.+A sense of ownership is a powerful motivator for inspiring extraordinary work performance. If the norm is a traditionally top-down approach in the company, it is difficult to convince staff that any change is good, efforts will be recognised and it will be beneficial for all in the long run. This is explained well by Whirlwind of Work (WoW) in Covey's 4 Disciplines of Execution.
  
 As such, culture change requires a concerted effort to pilot a demonstration of what can be done. Theories in management books and seminars and trainings remain intangible, until the staff can see and feel for themselves that they actually work, and will yield positive results. As such, culture change requires a concerted effort to pilot a demonstration of what can be done. Theories in management books and seminars and trainings remain intangible, until the staff can see and feel for themselves that they actually work, and will yield positive results.
  
-One of the core principles of the Agile Manifesto is:+One of the many core principles of the Agile Manifesto is:
  
 <code> <code>
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. 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   * 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]]   * 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 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 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   * Recruit another upto 6 staff/developers to form pilot Scrum team
  
-==== Phase 2: Scrum pilot - 3 months (sprints x 2 weeks each)  ====+==== Phase 2: Scrum pilot - 3 months (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 and 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 conduct Sprint Planning+  * **Day 0 or minus 1:** (4 hours) Pilot Scrum Team conducts Sprint Planning
     * Product Owner presents Product and Sprint Backlog for discussion     * Product Owner presents Product and Sprint Backlog for discussion
     * Team estimates "story points" and agrees to Sprint Backlog (i.e. scope of work)     * Team estimates "story points" and agrees to Sprint Backlog (i.e. scope of work)
   * **Days 1 to 9:**   * **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 did you do yesterday?
       * What are you planning to do today?       * What are you planning to do today?
Line 56: Line 56:
     * Sprint 2 Planning: See Day-1, iterate     * 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 ==== ==== Phase 3: Embrace and Extend - 6 months ====
  
-  * Recruit upto 9 staff for Scrum Team 2+  * Recruit upto another 9 staff for Scrum Team 2
   * Product Owner and Scrum Master to attend trainings   * Product Owner and Scrum Master to attend trainings
   * Scrum Masters to conduct Scrum training for developers   * Scrum Masters to conduct Scrum training for developers
start.1705571563.txt.gz · Last modified: 2024/01/18 09:52 by 219.74.112.242

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki