In this energizing 45th Hands-on Agile session, James Shore shared his experiences with scaling “agile:” first with traditional approaches and, more recently, with FAST scaling. Learn in this deep-dive what works, what doesn’t, and how you can try FAST in your organization.
📺 Watch the video now: James Shore: FAST: An Innovative Way to Scale — Hands-on Agile #45.
SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. The result back then was -52. Four and a half years later, I reran the poll: SAFe® has been through several iterations, and many more agile practitioners have experienced working with it. However, the question still is: Would you recommend SAFe ®?
Executive Summary: SAFe®’s NPS® score based on the 2022 sample equals -56. (For details, see the data below.)
SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. The result back then was -52. Four and a half years later, I believe it is time to rerun the poll: SAFe® has been through several iterations, and many more agile practitioners have experienced working with it. Moreover, the question still is: Would you recommend SAFe ®?
If you can spare five minutes of your time, please join the community effort and participate in the 2022 SAFe® survey.
For years, I worked in several Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on making ‘agile’ — including Scrum as a framework — work in a fast-growing startup. Also, let me introduce you to the anti-patterns agile startups shall avoid at all costs.
Master autonomy purpose — in this article, I present a slightly different way of viewing agile maturity, through Dan Pink’s lens of Mastery, Autonomy, and Purpose; as a simple and useful way of fostering conversations and ensuring all relevant perspectives are considered.
After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendations the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
