These are the opinions of individuals and do not represent the views of the Dojo Consortium or the members' employers.
So, you hired an “Agile Transformation” consulting company to advise executive leadership and you’re “Agile” now. Leadership attended a week-long class on “Agile”, teams took a two day class about Scrum being The Way. The new methodology with story points, daily standup, and sprints now reigns, but outcomes haven’t changed. Next, you talk about the “agile mindset” while Scrum Masters report monthly on how much “velocity” has increased. At the team level, the labels have changed, but the processes are the same. Possibly there is less design, but you don’t design solutions in “Agile”. They just “emerge”, right?
We are creating an innovative environment and a strong corporate culture, and that is living the dream.
The DevOps community provides sage advice to focus on outcomes. Outcomes in this context serve as the “North Star” to guide our improvement journey.
I was asked recently about the best practice for using GitFlow with continuous integration. For those who do not know, this is GitFlow: