The document discusses adopting Scrum in the workplace ("Gemba"). It emphasizes that bringing Scrum to Gemba will require repeated cycles of study and practice. Key steps include determining goals, setting a time-box of around two weeks to generate and prioritize tasks, planning tasks for each sprint, taking action, reflecting on results and processes, and iterating. Training such as Scrum certification courses and working with a coach can help build abilities. While challenging, small incremental changes can help achieve goals if motivation is maintained and people remain the focus.
The document is a presentation for QCon Tokyo 2010 about succeeding in software development. It discusses concepts like CSP, the lack of silver bullets in software engineering, and necessary vs unnecessary work. It also covers training methods like Sukusuku-Scrum and the importance of trial and error. The conclusion emphasizes continuing to learn from experience through practice.
The document discusses adopting Scrum in the workplace ("Gemba"). It emphasizes that bringing Scrum to Gemba will require repeated cycles of study and practice. Key steps include determining goals, setting a time-box of around two weeks to generate and prioritize tasks, planning tasks for each sprint, taking action, reflecting on results and processes, and iterating. Training such as Scrum certification courses and working with a coach can help build abilities. While challenging, small incremental changes can help achieve goals if motivation is maintained and people remain the focus.
The document is a presentation for QCon Tokyo 2010 about succeeding in software development. It discusses concepts like CSP, the lack of silver bullets in software engineering, and necessary vs unnecessary work. It also covers training methods like Sukusuku-Scrum and the importance of trial and error. The conclusion emphasizes continuing to learn from experience through practice.
