Offline boards lift a team’s level of collaboration significantly. They are great information radiators for stakeholders, and they massively benefit from the psychology of getting haptic. Learn the best practices of getting started with your own offline boards in this third post of our series on how to kick-off an agile transition.
Age of Product’s Food for Thought of September 25th, 2016—shared with 4,698 peers—asks: Where does agile coaching start and end? In addition, we explore proven tactics to work with remote agile teams, and question the “stable team” dogma.
We then dive deep into an important engineering question for agile teams: Is there something like an agile architecture? We also remind us of typical agile failure patters in organizations, and we learn more about the future of agile delivery.
We also understand how to become better at product management, picking up some tricks from Ellen Chisa and John Cutler. Drift is so kind to share their customer-centric product creation framework with us, and Barry O’Reilly provides great insights in how to transition a large organization to a lean enterprise.
Last, but not least, we learn from The Economist why companies make their products deliberately worse—microeconomics is great, just saying—, and that we should dump the secrecy that surrounds remuneration.
Age of Product’s Food for Thought of September 18th, 2016—shared with 4,585 peers— turns to Dark Scrum, and how the agile revolution is falling victim to its own success. We learn why leadership is overrated, and how self-organization requires to rethink its role.
We then dive deep into how to navigate the dangerous waters of office and project politics, and we learn how to say “No” without killing ourselves in the process.
We also understand the importance of playing to improve your life & work, and we check out mental models for product managers, including the lastest “CynAgileanUXanbanicrumify” trend.
Last, but not least, we learn how to avoid building bad features by keeping our customer-centricity mojo and prioritizing in the right way, and we pick up Elon Musk’s inspiring view of future, and what we should be working on.
Where to start when kicking-off an agile transition?
Usually, tools and processes are smallest the common denominator among all participants, as they are at the core of the grand scheme of agile things.
It is a rare occasion that you start from scratch with a brand-new team without an existing product, probably even in a more or less nascent organization, for example a startup.
In most cases, an existing product delivery organization with available products, and services will go “agile“. In this case, turning attention to the available product backlog is a pragmatic first step. The following process describes what aspects need to be attended to to optimize the outcome.
Age of Product’s Food for Thought of September 11th, 2016—shared with 4,435 peers—again turns to the question: What is Agile, agile, or probably “Agile”. With 70+ agile practices, we have a look at meaningful agile metrics, and how Scrum helps the FBI to track the bad guys. Nevertheless, we need to ask: What’s wrong with Scrum?
We then dive deep into product managers fooling themselves prior to burning out, and what you can do about it.
We also learn, what features a “good” team at Google—spoiler alert: being smart doesn’t suffice—, and why zero bullsh*t Lean is good product management. (If your backlog feels like a black hole, you want to listen to that podcast.)
Last, but not least, we deconstruct Theranos’ precocious “founder” in an epic story. And we learn that the former Apple engineer who led the transition of the Mac to Intel processors, wasn’t consider a match for a Genius Bar job in an Apple store—at the age 54.
Welcome to the era of ageism and enjoy a great Sunday!
Age of Product’s Food for Thought of September 4th, 2016—shared with 4,331 peers—explains the two agile camps—Manifesto-based agile mindset vs. selling packaged “Agile”, so to speak—, ventures out into hostile territories, and brushes up your framework knowledge with a handy cheat-sheet.
We then dive deep into learnings from Fortune 500 product teams running lean experiments, and what the modern product designer role covers. We enjoy the 100+ cognitive biases cheat-sheet—no more fooling yourself—, and finally have to ask: Do we really need Product Managers?
Last, but not least, we learn how Trello builds & scales its fabulous tool, and why management is too important to be left up to managers alone. Enjoy a great Sunday!