Israel Alcazar

Agile Manifesto Retrospectives Questions Cards on @leanpub buff.ly/4anOoQp Powerful questions to inspire your agile retrospectives and keep them valuable and effective! For retrospective facilitators, Scrum masters, Agile Coaches, and consultants.

Game Changing approach from Harry Narang - if you can catch this course with this elite trainer, you win! #valuestream #LPM #LeanPortfolioManagement #ValueStreamWhisperer.

4

Has Agile become "too popular for its own good?" Join the conversation with Simon Reindl, Maarten Dalmijn, and I on 👉 https://lnkd.in/emBWJUWS

7

"The best performance improvement is the transition from the nonworking state to the working state." - J. Osterhout John Osterhout's quote elegantly captures a profound truth in software development and, indeed, any form of learning: the most significant leap occurs when moving from inaction to action. For beginners in coding, the idea of writing code that runs successfully can seem daunting. Yet, the transition from not coding at all to writing your first functional line of code is where the most dramatic growth happens. It’s not about perfecting the code from the start but about overcoming the barrier of beginning. This transition underscores an important lesson in coding and in mastering any skill: the value of incremental progress. Each step forward, no matter how small, transforms your understanding and competence. In coding, every error corrected and every function perfected contributes to your development as a programmer. Beginning coders should focus on making consistent, small improvements. It’s about evolving from a nonworking state, not only in terms of your code but also your coding habits. Establish a routine, practice regularly, and tackle problems step-by-step. Moreover, this philosophy applies to debugging—a crucial skill in programming. Moving a piece of code from a nonworking state to a working state often involves identifying and fixing bugs, which in itself is a learning opportunity. The journey from a non-coder to an adept programmer is filled with many small, yet significant, transitions. Each line of code that runs today builds a foundation for more complex projects tomorrow. P.S. What was the first piece of code you wrote that worked? How did it feel to see it run successfully? ******* I am Manish. I help beginners learn coding. Follow me here: https://lnkd.in/d8EXqDsW 🔄 Repost this post

8

"The best performance improvement is the transition from the nonworking state to the working state." - J. Osterhout John Osterhout's quote elegantly captures a profound truth in software development and, indeed, any form of learning: the most significant leap occurs when moving from inaction to action. For beginners in coding, the idea of writing code that runs successfully can seem daunting. Yet, the transition from not coding at all to writing your first functional line of code is where the most dramatic growth happens. It’s not about perfecting the code from the start but about overcoming the barrier of beginning. This transition underscores an important lesson in coding and in mastering any skill: the value of incremental progress. Each step forward, no matter how small, transforms your understanding and competence. In coding, every error corrected and every function perfected contributes to your development as a programmer. Beginning coders should focus on making consistent, small improvements. It’s about evolving from a nonworking state, not only in terms of your code but also your coding habits. Establish a routine, practice regularly, and tackle problems step-by-step. Moreover, this philosophy applies to debugging—a crucial skill in programming. Moving a piece of code from a nonworking state to a working state often involves identifying and fixing bugs, which in itself is a learning opportunity. The journey from a non-coder to an adept programmer is filled with many small, yet significant, transitions. Each line of code that runs today builds a foundation for more complex projects tomorrow. P.S. What was the first piece of code you wrote that worked? How did it feel to see it run successfully? ******* Are you a beginner who wants to learn coding? Follow me here: https://lnkd.in/d8EXqDsW 🔄 Repost this post

14

OKRs are widespread but often implemented wrong. Here's 5 first principles when implementing OKRs: 1️⃣ OKRs should align, not cascade The most prolific mistake I see when implementing OKRs is making them cascade in a top-down fashion. This not only remove autonomy, it reduces flexibility as KRs get inherited meaning that pivoting or adapting requires moving back 'up the chain' and to change higher level OKRs. Instead you should think of aligning your OKRs like a constellation of stars, not a linear ladder. 2️⃣ Outcomes over outputs OKRs should describe outcomes not outputs. Avoid having KRs or Objectives that says something like; “Launch app X” 3️⃣ OKRs are a model of you Strategy OKRs don't exist in a vacuum. They should represent the strategic levers you are choosing to pull in order to forward and measure progress towards your strategy. Therefore you must have a strategy first before you set your OKRs. 4️⃣ Customer AND Business impact A common mistake with OKRs are they can become too internally (business) focused. I see companies describe OKRs which state things like "Grow DAU by x% YoY" and "Reach $20M in ARR" etc. And whilst all appropriate goals to strive towards we can easily become too internally focused on forwarding our own agenda and neglect the customer. OKRs should balance our goals as a business as well as outcomes for the customer. If we do want to reach a certain ARR then we should be asking ourselves - what customer outcomes might help us get there? These must also become part of our OKRs. 5️⃣ OKRs ≠ KPIs You need both. OKRs = the things we want to change. KPIs = measures of health KPIs are key indicators of performance, they represent the measures that would indicate a performing and healthy product or business. For example, we may want to monitor 'churn', 'conversion' our CAC and costs base, revenue, etc. However we may only want to reduce 'churn' for example. This would then become your OKR. Whilst the other metrics are still important and therefore remain as your KPIs. ===== More on OKRs: 📺 Best Practices on Implementing OKRs (https://lnkd.in/gT2rRjYm)

34

6 comentarios

7 amazing things you can check off your bucket list at Facilitators Connect:   1.      Network with Top facilitators 2.      Practice new facilitation techniques 3.      Learn from expert speakers 4.      Create lifelong connections 5.      Relax and recharge in a beautiful location in France 6.      Host a workshop in a castle 7.      Master the art of perfect post-it placement   If you need more good reasons to attend the event, comment YOLO and I’ll provide you with some more! #Workshop #retreat #facilitator Katrien Schepers 🏰

25

14 comentarios

Agile is not a methodology. It is a set of values and principles. It’s a way of thinking and working that puts the customer at the center of product development. https://lnkd.in/em4v87Mt #agile #agileMindset #agileCoach #agileCoachingToolbox #agileYoda

1

Learning Systemic modelling from Caitlin Walker (PhD) was one of the most impactful things I've done. The course gives you practical tools to help build self-managing teams and start understanding your patterns.

26

4 comentarios

💡 Today's Featured Best Practice: Five Pillars of Agile Organizations (30-slide PPT) -- https://lnkd.in/eXGg7EaQ Traditional organizations are often static, siloed, and comprised of a bureaucratic rigid hierarchical structure where control and decisions flow top-down. Such structures are strong but lack agility. Agile organizations, on the other hand, execute quickly, empower their teams to act nimbly, have quick decision cycles, based on a shared purpose to create value for shareholders. This presentation describes how traditional organizations can become agile by understanding and incorporating the 5 foundational pillars of Agile organizations: 🗎 Full details and download here: https://lnkd.in/eXGg7EaQ #bestpractice #organizationaldesign #agile #organizationaldevelopment #organizationalalignment #management #strategy #consulting #leadership

4

#SAFe, #DisciplinedAgile, #ScrumAtScale, and #LeSS: What do they have in common? These frameworks all borrow the foundations of #Scrum and #Kanban. Join my upcoming sessions to deepen your understanding of these core #Agile practices. https://lnkd.in/gvs_jBmU

4

groCTO Newsletter #15 is here! This week, we had a wonderful curation, thanks Denis Čahuk 🔊 In Conversation with Sergio Visinoni: Maslow's Hierarchy for Tech Teams 🧑‍🏫 Coaching Tips by Dr. Milan: Navigating the Change Curve 💡 Rethinking Technical Tasks: Define All Tasks As User Value by Alvaro Jose Lorente Perez ⚙️ Engineer Self-Check: 12 Ways To Tell If You’re A Difficult Engineer (And What To Do About It) John Crickett 📚 groCTO recommended Reads: 3 Essential Non-Tech Books for Software Engineers 👉 Read the full newsletter in the comment section below! #groCTO #SoftwareEngineering #TechTeams #MaslowsHierarchy #ChangeCurve #TechCoaching #UserValue #TechnicalTasks #DifficultEngineer #SelfImprovement #NonTechBooks #EssentialReading #SoftwareDevelopers #TechCommunity #groCTONewsletter #EngineeringExcellence #TeamCollaboration #CareerGrowth #TechInsights #TechCurators #TechPodcast #EngineerTips #ContinuousLearning #LeadershipDevelopment #TechMindset #Innovation #DeveloperLife #TechCulture

21

3 comentarios

17 Years of Agility: The Elephant in the Room is Still Change Resistance The latest State of Agile report was out in 2023, and after 17 years of tracking the trends and challenges in Agile adoption, one thing remains constant: change resistance is still the biggest obstacle to successful transformation. In fact in today's fast paced world of constant disruption, resistance is on the rise. Burnout and disengagement are at record levels. Despite the many advances in Agile methodologies and tools, the human element of change remains the most significant hurdle to overcome. It's not about the frameworks, the processes, or the technology - it's about people's state to have the ability to adapt to new ways. So, what can we do to overcome this resistance to change? Here are a few strategies that have worked for me: and is now available to you in NeuroStarter™   Take the time to scan and check in on the team and individuals Identify the root cause. Remembering Often the problem is not the problem, identify the Neuromodulators that are out of balance. Create and plan interventions that are scientifically proven for the area of neuromodualtion required Regularly Monitor and Check in on the impact of the change Once you understand the underlying reasons, you can develop targeted interventions to address them.   Let's face it, change is hard. But with the right approach, NeuroStarter™ we can overcome resistance and achieve successful transformation. Check out this video and discover the one off deal Dr. Justin James Kennedy and Greg Pitcher (P.npn) have put together for you. Make change resistance and other forms of resistance a thing of the past and with NeuroStarter™ Discovery , resistance can now be a thing of the past. Dr. Justin James Kennedy npnHub | Uniting Experts and Learners in Applied Neuroscience   #StateOfAgile #ChangeResistance #AgileTransformation #Leadership #ChangeManagement

11

Breaking News - The Era of Copy-Paste Agile is Over! Maarten Dalmijn highlights a seismic shift in the Agile job market, urging organizations to abandon generic frameworks. It's time we embrace Agnostic Agile and tailor practices to meet the unique challenges of our organizations for true effectiveness.

9

1 comentario

[These are *great* frameworks. But never forget if you interpolate scoring into your process, that these are "quantitative" tools for a *higher quality conversation*.] Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions: https://lnkd.in/eunV7G3t?

4

OKRs are not the only thing that occupies my head :-) A new version of the EBM (Evidence-Based Management) Guide was published today. Since I first read it in 2019, I have pursued the goal of gradually introducing it as part of the tool we are creating. Here is a post by Patricia Kong and Kurt Bittner describing the guide update: https://lnkd.in/dUCktPzX #scrum #ebm #goals

13

3 comentarios

Ultimate Agile Leadership I (PAL I) Practice Assessment. Prepare and practice for the Scrum.org Professional Agile Leadership (PAL I) Assessment. https://lnkd.in/dkrxs-vZ #scrum #agile #scrummaster #productowner #training #kanban @Scrumdotorg

2