Food for Agile Thought’s issue #177—shared with 20,568 peers—covers Scrum limits, the brand-new Scrum Master Trends Report 2019—a joined venture of Age-of-Product with Scrum.org—and the fallacy of wanting to scale ‘agile’ throughout an organization.
We also learn from the Puppet founder that we are not alone in our skepticism regarding enterprise sales, what the author of ‘The Innovator’s Dilemma’ has learned about innovation for the last 25 years, and how we can achieve a better understanding for product management among stakeholders.
Lastly, we have a look at what creates an exemplary agile workspace; if only more organizations would join ING in this respect.
Food for Agile Thought’s issue #176—shared with 20,343 peers—covers a study on personality traits suited for agile team building; we go through the stages of adopting self-management as an organization, and we listen to the professor who coined the term “psychological safety” to realize why it has become an essential building block for organizational success.
Also, we ask whether the rush to ship a new product as soon as possible to gather feedback has become untenable; we dive into determining product value, and we understand the particularities of product management from a new viewpoint.
Lastly, we learn more about the educational challenges agile coaches face themselves.
Food for Agile Thought’s issue #175—shared with 20,249 peers—focuses on agile pipe dreams: from the absence of complexity in software development to the management-free organization to abundant team capacity.
We also identify more product management problem areas, how to create a shared understanding about your product within your organization, and how you can engage your engineers beyond churning out code.
Lastly, we can put the fuzziness of the #NoEstimates concept to rest once and for all—there is a new animation explaining everything in merely six minutes.
Food for Agile Thought’s issue #174—shared with 20,147 peers—focuses on making sense of feedback with the epic new EPIQ model; we talk about a Scrum value that also applies to managers, and we reflect on the prime directive and the magic it provides.
We also address the importance of product design principles; we add systems thinking to our product management toolbox, and we learn how best exploit the opportunity of a rewrite.
Lastly, we appeal to efficiency freaks to finally realize that slowing down speeds up everything in software development.
Team building has always been a challenge, not just since the advent of agile frameworks and the resulting emphasis on self-organization, engagement, and achieving a valuable objective. This post covers four team building mental models — or concepts — that have proven useful in understanding the context of creating agile teams: from Taylorism to Tuckman to Lencioni to Dan Pink.
Food for Agile Thought’s issue #173—shared with 20,138 peers—focuses on agile common sense as we learn more about the history of ‘agile’ and what defines the learning space that makes it successful.
We also get better at cycle time scatterplot diagrams, what conditions product teams require to support hypergrowth, and why leadership is not always about having a plan.
Lastly, we learn five encouraging ways how to engage the engineers in creating the product beyond its mere coding.
