The first insights are available from the Remote Agile Survey: What are good remote agile practices, and what are possible low-hanging fruits that haven’t yet been tried by a majority of participants? Moreover, we learn if new collaboration practices have been tested and if so what those are.
👉 Participate in the Remote Agile Survey now, too.
Welcome to the 242nd edition of the Food for Agile Thought newsletter, shared with 26,503 peers. This week, we thank Keith and Fisher for insight into how Liberating Structures foster creative adaptability; we apply NoEstimates techniques and philosophy in real life, and we understand critical issues of distributed team building.
We also applaud a new product discovery guide; we learn how OKRs propelled Gmail massive success, and we tackle remote design’s most significant issues.
Lastly, we learn how to remove organizational silos following a new mental model.
Did you miss last week’s Food for Agile Thought’s issue #241?
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.
👉 Participate in the Remote Agile Survey now.
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.
Did you miss last week’s Food for Agile Thought’s issue #240?
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.
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?)
Did you miss last week’s Food for Agile Thought’s issue #239?
