Craving some no-nonsense, framework-neutral agility, leadership and performance insights? My 2x month newsletter dive deeper into actionable tips for real issues agile leaders and coaches deal with when seeking more adaptability, growth, and overall better results, for themselves and for their teams. Be the first to know when events and masterclasses come up, get deals in courses and coaching, get access to toolkits and more. It's free and not spammy. 👉 allthingsagile.co/newsletter/
shifting from waterfall to agile is too broad and i dont think that really works. remember org needs to assess opportunities and projects if they really need to use scrum or agile,was thinking now, what is the ideal job description of agile coach, scrum masters? then, how about those with views on water-scrum-fall and agifall et al. - curious though.
Indeed you are right. Probably that first conversation with this company would be "tell me more about what you mean by shifting from waterfall to agile?" What's great about not assuming anything about that transition is you: 1 - help people see that usually there are easier wins accessible 2 - gain an opportunity to support that start of shifting their mindset (oh, that word) As for the ideal description of an agile coach job post, in my mind it would involve: 1 - Helping people to understand and manage their workflow, including improving it. There IS right and wrong in terms of agility. Not multitasking, working value-first, etc. 2 - Use influence and persuasion at some level to help people embark in the change, whatever the change is. 3 - Help people make sense of what are the steps required to move towards a more agile approach: customer-centric, value first, great technical development, fast feedback lops, etc. It involves a lot of technical knowledge such as knowing how to map workflows and value streams, how to spot issues in those, how to organize roadmaps, to more "soft" skills like coaching and facilitation, i.e, talking to people respecting their knowledge and agency and being able to rally them around collectively owned objectives. It's important to notice it's an ever evolving job. Your first team might be 6 people scrum-curious, while 5 years later you are then trying to help an organization with multiple locations of development improve their time-to-market and ROI. I hope this makes sense.
