TL;DR: App Prototyping with Absolute Beginners
Yes, even absolute beginners can prototype an app. And learn a lot about agile product management, Scrum, empiricism, product design, and user experience along the way.
If you intend to live up to Scrum and agile product development’s full potential, creating a shared understanding of how empiricism works among all co-workers in your organization is essential. This low-cost exercise of creating clickable prototypes will significantly improve your organization’s agile transformation.
TL; DR: Product Backlog Defense
Make no mistake: Your Product Backlog is the last line of defense preventing your Scrum Team from becoming a feature factory; hence Product Backlog defense is vital: Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
TL; DR: 11 Proven Stakeholder Communication Tactics
Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. It would help if you also talked about it, particularly at the beginning of your endeavor to becoming a learning organization. Marketing your journey to the rest of the organization—and thus securing their support, collaboration, and buy-in—is a critical success factor to step up the transformation game: You want to become agile, not “do agile.”
Learn more about eleven proven stakeholder communications tactics that contribute to making this happen.
TL; DR: Agile Management Anti-Patterns
Learn more about agile management anti-patterns the aspiring servant leader should avoid during the organization’s transition: From applying the Stage-Gate® approach through the back door to the ‘where is my report’ attitude to other beloved signs of applied Taylorism.
TL; DR: Scrum Stakeholder Anti-Patterns
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition.
TL; DR: The Meta-Retrospective
A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items. It comprises of the team members of one or several product teams—or a representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers.
Meta-retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product. Read more on how to organize such a meta-retrospective.