Stefano Petracca

How to transition from Scrum Master to Agile Coach? Ready for the Next Step? For Scrum Masters looking to expand their impact and grow professionally, becoming an Agile Coach is the next logical step. This transition opens up new opportunities and allows you to influence Agile transformations at a higher level: - Work across multiple teams and influence organisational culture. - Develop strategic leadership skills and guide Agile transformations. - Increase your career opportunities and become a key player in Agile adoption. Becoming an Agile Coach is an opportunity to: - Learn to mentor teams and individuals in Agile practices. - Lead Agile transformations and navigate resistance. - Align Agile practices with business goals. Pursuing Agile Coach certifications enhances your skills, boosts your confidence, and opens doors to exciting new roles. Ready to take your Agile career to the next level? The next Registered Agile Coach course: Dates: 19 - 23 August, Mon-Fri Time: 6 PM - 10 PM ASCT Format: Online, ZOOM The link with more details about the course is in the comments.

13

9 commentaren

🚀 Ready to Level Up Your Agile Career? 🚀 ScrumCraft's Agile Coach course is perfect for Scrum Masters looking to expand their impact! Why Join? Learn about how to: > Influence multiple teams and organizational culture. > Develop strategic leadership skills. > Boost your career opportunities. > Lead Agile transformations and mentor teams. #AgileCoach #ScrumMaster #CareerGrowth #AgileEducation

5

I’ve been running Certified Scrum Master ‘style’ courses for a while now as part of my CST journey (and since I recently passed I’ll soon be running them for real !https://lnkd.in/e_BN98jN) and as such you meet people with different levels on understanding of Agile and experience of Scrum. Or at least what they think is Scrum. Let me explain. When I’m teaching Scrum I tend to let people have a stab at what they are trying to learn before debriefing it. And the answers given for one of the events in particular tends to make my teeth itch a bit. The Daily Scrum. Oft people forgot that the timeboxes for Scrum events are the maximum amount of time that should be utilised, not the amount of time that you have to spend. The Daily scrum in theory could be thirty seconds long. Because...well, I’ll get to that. What tends to happen is that teams utilise the ‘what I did yesterday, what I’m going to do today and are there any impediments’ round robin style interaction. This is more like a status update which does not achieve the purpose of this event. The chance to inspect and adapt. Hang on what was this thirty second thing you mentioned earlier ? The purpose of the Daily Scrum is to check whether the plan you constructed in Sprint Planning is still viable in order to deliver the value you committed to as a team. Hence if you are on target to complete the sprint goal, it should take teams a few seconds to check said plan and say, ‘yes we are’. Or of course, to realise they are not and then spend the remaining time changing their plan accordingly. In my experience teams tend not to execute the Daily Scrum properly, because they haven’t executed Sprint Planning properly. The ‘how’ part has been neglected. This is often because Scrum teams wont have a daily plan that shows which tasks they will be undertaking to complete Product backlog items and hence increments. Instead they will often go for a leaner approach and use a Kanban style ‘Sprint Board’ and move PBIs across the various To Do, In Progress, Done, style stages. And this is great if you are a super mature team who know whether or not they are going to complete their sprint goal. But if you’re not, then construct a Daily Plan, ironically, in Sprint planning. And then your Daily Scrums might be shorter and more effective. And then maybe one day my teeth won’t itch as much..... #scrum #csm #cst #scrumalliance #agile

14

1 commentaar

Agile Coaches, do you often feel caught in the cycle of sprint after sprint, while struggling to showcase the real business impact of your agile methods? Aligning agile practices with the long-term strategic objectives of your organization is no small feat. This misalignment can lead to significant challenges, such as difficulty in demonstrating value to stakeholders and maintaining team motivation beyond mere task completion.🔄 At OKR Institute, we understand these frustrations. That's why we've designed solutions specifically to help Agile Coaches like you overcome these obstacles and turn agile execution into strategic triumphs. Connect your agile practices to tangible business results with our expert-led courses. Sign up👉 https://lnkd.in/ggZixwGU #okr #okrs #okrinstitute #objectives #keyresults #strategies #agile #softwaredevelopment #businessalignment

14

Curious about what the 𝑷𝒊𝒛𝒛𝒂-𝒕𝒉𝒆𝒎𝒆𝒅 𝑻𝑫𝑫 𝒔𝒆𝒔𝒔𝒊𝒐𝒏 is really about? 🍕 Think of a scenario: you order a pizza, but something’s off—maybe too much cheese, or it’s not the thin crust you expected. This is exactly like writing unit tests to validate software! 𝑾𝒂𝒏𝒕 𝒕𝒐 𝒌𝒏𝒐𝒘 𝒎𝒐𝒓𝒆?  Join me to discover how TDD principles fit right into our favorite foods! Learn more at Agile Day 2024—save your spot now! 👉 https://lnkd.in/gJFbtNJU #AgileDayMalaysia2024 #TestDrivenDevelopment #UnitTest

13

1 commentaar

🎓 𝗪𝗵𝗮𝘁 𝘁𝘆𝗽𝗲 𝗼𝗳 𝘁𝗿𝗮𝗶𝗻𝗲𝗿 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝗱𝗼 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝗻𝘆? 🎓 At Scrum Facilitators we want to make it as easy as possible to register for a training with us. However we do not know a lot about how people in companies can register for training and if we are part of that system. We are already registered at some parties, but probably not all. Maybe you book a training directly through our website, or you use Archipel Academy or Springest or another training provider? 👇Please let us know in the comments, so we can make our training more easily accessible for everyone!👇 #scrum #agile #training #workshop #noppt  

9

9 commentaren

Two days Creating/Designing Agile Organisations certification training behind and my mind is full of thoughts. I really need to digest all the new information, but there is something I would like to share with you right away. Why SCALING agile is not working? (Should we even talk about scaling?) 🖨️ It’s because organisations are trying to copy paste what works for one team to all teams or they are trying to copy of some other organisations model to their organisation which simply has a completely different system than the other has. 👓 It’s because organisations are optimising different parts of the organisation but not the whole system - or even not trying to understand the whole system. 💥 It’s because organisation design and structures simply conflict with the mindset of adaptability and the values of agility. Thank you Wolfgang Steffens ☀️ for the inspirational two days’ training!

9

Thanks everyone for all the discussion around Scrum Guide (LeSS version). I want to share and highlight an article created by Gunther Verheyen. The article puts the Scrum Guide (LeSS Version) in the historical Scrum perspective. Gunther has outlined the changes in Scrum over the year in this article: (https://lnkd.in/ercYmnHp) If you put this in the context of LeSS evolution, LeSS started out (2005) using Scrum terminology and concepts as they were common Scrum then. Unfortunately, Scrum changed and many of these changes were not useful in LeSS. In the SG2020 the difference became so big that, in LeSS, we stated that we will not use the SG2020 guide (see: https://lnkd.in/e6dTYNcj). This often led to confusion and questions. The Scrum Guide (LeSS Version) will hopefully bring more visibility and clarity to this difference. Thanks Gunther Verheyen for the article and your work on Scrum history. #lessworks #scrum

55

3 commentaren