Despite criticism from the product community regarding Scrum as a framework for effective product creation, namely Marty Cagan himself, I believe that it is worthwhile to compare the principles that help form successful product teams with those of Scrum. Let’s delve into an analysis of “Transformed” and how its principles align with Scrum’s.
For years, I have supported the Agile community with a wealth of free resources and opportunities for growth. From the Food for Agile Thought newsletter to the Scrum Master Salary Report to tools like the Scrum Master Job GPT, and from ebooks like the Scrum Master Interview Questions Guide to the Hands-on Agile Slack and Meetup groups, I’ve consistently provided value without asking for anything in return than your support and participation. As for all communities, there is a simple rule: the more, the merrier; the benefit of being a member increases with the size of the community and those who contribute themselves. Giving back to the community is a win-win proposition.
However, the landscape is changing. The recent economic downturn and a noticeable backlash against Scrum have presented new challenges. As a result, the business model that has sustained these efforts—financing by subsidies through my Professional Scrum classes—has become increasingly unsustainable. Consequently, my approach to continuing to support this incredible community will need to evolve, too.
Suppose you are a Scrum Master or Agile Coach. Have you recently been asked to explain your contribution to the organization’s value creation? In other words, does management want to know whether you are pulling your weight or if your salary is an expendable expenditure? This article points to ten quick Scrum gains you can pull off without asking for permission or budget to prove your contribution to your organization’s survival in these challenging times.
Are there agile regulated industries, or is that an oxymoron?
Recently, I received a project alert from an organization looking for a Scrum Master with “at least two years knowledge of information systems for rail and public transport travelers.”
Now, if you go through the job description, they do not seem to look for a Scrum Master but a project manager and glorified Jira clerk. If that is the case, why don’t they say so but pretend there is such a thing as agile regulated industries?
Imagine your team’s line manager insists that a successful team improves velocity regularly. How could you, as a team, satisfy this strange, unsuitable demand without working more? How can you make gaming velocity a reality?
I run this exercise with my students of entry-level Scrum Master and Product Owner classes to help them reflect on the tricky nature of measuring success, metrics, and, of course, Goodhart’s Law: “When a measure becomes a target, it ceases to be a good measure.”
For the following article, I aggregated suggestions from more than 50 classes on how to “best” game velocity.
Understanding and implementing the right alignment tools in agile product development can significantly enhance the effectiveness of your team and organization. Fostering better relationships between stakeholders and teams can ensure strategic clarity, improve adaptability, and maintain a user-centric focus.
This article provides actionable insights on leveraging these tools to build trust, enhance collaboration, navigate risks, and maximize value creation. This will ultimately lead to more successful product outcomes aligned with organizational goals.
