There has been no shortage of articles on how to work remotely recently, including our series on remote Agile. While most of the ideas, lessons learned, and tips and tricks may not be new to those few remote work pioneers, they are, however, to the rest of us. The question hence is: What remote work problems are agile teams and organizations facing, and what has proven to be successful in the transition? Answering these two questions is the purpose of the Remote Agile Survey: Let us stop guessing but collect data instead to inspect and adapt the way we can work as an agile distributed team.
TL; DR: Scrum’s Essence, the New New Scrum Master—Food for Agile Thought #241
Welcome to the 241st edition of the Food for Agile Thought newsletter, shared with 26,408 peers. This week, we brush up our understanding of Scrum’s essence; we indulge ourselves in collective wisdom regarding Scrum’s first principles, and we embrace a state that nowadays is more important than ever—trust, leading to psychological safety.
We also analyze Product Owner roles—there are six of them—; we enjoy an inside view at Amazon’s culture, and we reflect about roadmaps, design problems, and testing assumptions within the Jobs-to-be-done framework.
Lastly, we come back to the Scrum Master role and learn how working with distributed teams requires to rethink it.
TL; DR: A Remote Daily Scrum with a Distributed Team
We started this series on remote agile with looking into practices and tools; we explored virtual Liberating Structures, and how to master Zoom. We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum.
TL; DR: Accurate Estimates, Remote Productivity—Food for Agile Thought #240
Welcome to the 240th edition of the Food for Agile Thought newsletter, shared with 26,317 peers. This week, we revisit the fallacy of accurate estimates; we delve into a study revealing massive increases in the cycle and release time metrics of development teams since going remote, and we enjoy a view at a different world of agile testing and quality.
We also learn about product management by nagging; we tackle feature request handling, and we analyze the essence of a decent Sprint Goal.
Lastly, we check the latest recommendations of the Dark Side of Agile; this time, they can ensure the productivity of your now remote workers. (Won’t we all want to be that confident?)
TL; DR: A Remote Sprint Review with a Distributed Team
We started this series on remote agile with looking into practices and tools; we explored virtual Liberating Structures, and how to master Zoom. We had a look at common remote agile anti-patterns, and we analyzed remote Retrospectives and Sprint Plannings based on Liberating Structures. This seventh article now looks into organizing a remote Sprint Review with a distributed team: How to practice the review with virtual Liberating Structures, including and giving a voice to team members, stakeholders, and customers.
TL; DR: Spotify Model Fallacy, Remote Discovery—Food for Agile Thought #239
Welcome to the 239th edition of the Food for Agile Thought newsletter, shared with 26,242 peers. This week, we point again at the Spotify Model fallacy; we understand the importance of empowered engineers to break out of the feature factory paradigm, and we put the org chart into the spotlight, the gateway to realizing change.
We also learn how to continue our product discovery efforts in today’s world of virtual communication; we look at the roots of innovation, and we are relieved that design sprints are open again for business—with a remote working guide from the maestro himself.
Lastly, we embrace an epic list of remote working resources, courtesy of InfoQ.
