Software Process and Measurement Cast SPaMCAST 654 - Monotasking, A Conversation With Staffan Nöteberg
Jun 6, 2021
26:15
This week is a doubleheader (baseball term for two games played by the same teams on the same day against each other). We begin our re-read of Monotasking by Staffan Nöteberg and we have my interview with Staffan. Several years ago I read Staffan's book on Pomodoro which changed how I work. Monotasking might be even more useful and impactful. We discussed how to apply the ideas in the book to improve focus, productivity, and quality of life. Staffan Nöteberg is an enterprise agility coach with years of experience in improving personal productivity. He is also the author of Pomodoro Technique Illustrated (2009) and teaches seminars on monotasking to companies in North America, Europe, and East Asia. Twitter: https://twitter.com/staffannoteberg Website: https://monotasking.staffannoteberg.com/ Re-Read Saturday News We start our re-read of Monotasking by Staffan Nöteberg. The book is 237 pages published by Racehorse Publishing (an imprint of Simon & Schuster) and was released in English on June 1, 2021. For most of the readers of the blog and listeners to the podcast, this will be an initial read. The book's contents include a Preface, Introduction, 7 numbered chapters, an Afterword, and then other stuff like index and more (we will not cover the other stuff but I am glad for the index and endnotes). Now the fun part. Instead of a straight re-read and discussion. I am going to read a chapter, highlight the parts I am going to implement in the next week, tell you what I am going to do, and then the following week admit how well I performed. Week 1 - Logistics, Game Plan, and Preface - https://bit.ly/3x1oVap As a reminder, all of the entries from Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller are available! Week 1: Re-read Logistics and Front Matter - https://bit.ly/3mgz9P6 Week 2: A Brief Introduction To Scrum, and Why Scrum Goes Bad - https://bit.ly/37w4Dv9 Week 3: Breaking Bad Scrum with a Value-Driven Approach - http://bit.ly/3stGc9Q Week 4: The Product Owner - https://bit.ly/3qpKvSn Week 5: The Product Backlog - http://bit.ly/3cAEk9c Week 6: The Development Team - http://bit.ly/2OLVAAs Week 7: Embracing The Scrum Master Role - https://bit.ly/3m0HB5D Week 8: Management - https://bit.ly/31Kv39l Week 9: Thinking In Sprints - https://bit.ly/321wXTg Week 10: Sprint Planning - https://bit.ly/3stWOhx Week 11: Sprint Backlog - https://bit.ly/3njezit Week 12 - Reclaiming The Daily Scrum - https://bit.ly/3eNzMgz Week 13: Deconstructing the Done Product Increment - https://bit.ly/3bedTGc Week 14: The Sprint Review - https://bit.ly/3huZvgP Week 15: The Retrospective - https://bit.ly/3bOK2Vg Week 16 - Final Thoughts - https://bit.ly/3p3tbU0v Upcoming Events! ISMA 18 Virtual Conference, June 24th, 2021 8 AM EDT to 11:15 EDT I will host the event. The event will have a host of great speakers on great topics! ISMA 18 will be free for both IFPUG members and non-members. IFPUG members are eligible for 1 credit at the CFPS Extension Program (CEP) and also attract 3 Technical PDUs in the PMI Talent Triangle®, both by attending the full conference! Register: https://www.ifpug.org/isma18/ Real Value of TMMi (SPaMCAST is a Friend of TMMi America) Free webinar from TMMi America featuring Mark Summers June 25th, 2 to 3 PM EDT This webinar will explore the common usages of the TMMi Test Process Improvement framework. We will dive into how: You can leverage this framework to transform the way your organization delivers software. The model can transform your career. Next steps to take on your journey to becoming a Test Process Improvement superhero. The real value of the TMMi is to help you dramatically change the frequency and quality of your software delivery. Register at https://bit.ly/2RtoGpy Next SPaMCAST In the next Software Process and Measurement Cast, we talk with Ajit Ghuman, Head of Product Marketing at Narvar. Ajit and I talk pricing, marketing, product engagement/ownership, and development. Is there an ideal pattern for product and development to work together? If not, what are the consequences?