Divya Anbalagan’s Post

Scrum Framework Visualization.. #Scrum #ScrumFramework #Agile

simple explanation of scrum process #scrum #scrum_process #agile #agile_methodology

Definitely a better choice than buying into the “AI can estimate better than your team” snake oil. Why yes, I did just demonstrate that OpenAI could write Ruby code better and faster than I could, and it passed all my carefully worded tests! But all I can conclude is that the proof of concept was successful and one day we developers might write test scenarios TDD-style and our AI ‘bots might write all the implementation. Might. Someday. Maybe. That’s empiricism, folks. Accept no substitutes, even from—especially from?—the Scrum Lords.

Just wrapped up an awesome online course on Agile and Scrum Fundamentals with JIRA 🎉  #Agile #Scrum #JIRA #AlwaysLearning #NewSkills #OnlineLearning #ProfessionalDevelopment 🚀📚

The 3 SCRUM roles and 3 artifacts

This was hilarious! However, I'm definitely tempted to take the momentum on this and recognize that there is truth in this. The original manifesto was written over 20 years ago. It was a different time and within a different work culture to say the least. The Agile Manifesto hasn't changed, but the manner we conduct business has. I will do here as I always do to many of my clients, and that is to pose a question: What in your opinion (needs to / should) change in order to reflect the current state? Original Manifesto: https://lnkd.in/erCXmXMG #skibidi #rizz #nocap

Link in comments #scrum #scruminc #agile #classroomagile #projectmanagement

This template for creating sprint goals will ease the process for writing sprint goals as well as writing PI objectives.

This is so Sigma. It’s a little behind the times though. How about this grace a ChatGPT.,. Here’s the Agile Manifesto reimagined through the lens of Gen Alpha with a “Skibidi brainrot” twist: Skibidi Agile Manifesto 1. Dance battles over documentation: Why write it down when we can just vibe it out with a dance-off? 2. Working beats over boring meetings: If the tune slaps, the work slaps. Deadlines? More like drop the basslines! 3. Collab squad over solo streaks: More lit when the crew rolls deep. Squad up, throw ideas, and sync like a viral dance move. 4. Freestyling over rigid routines: Plans are cool but sometimes you’ve gotta bust a random move. Adjust, remix, and keep the energy up! Feel free to vibe with that or remix it further!

One provocative though regarding software deliveries in companies... "If we had one common goal (the most valuable problem to solve) and the mindset of moving together in very small incremental steps that we'd plan, implement and validate together before agreeing on the next step in line... Wouldn't it all be cheaper, faster, valuable?" It just occurred to me after reading the "Gen Z version of Agile Manifesto" (see https://lnkd.in/eaw7Gjtk ) and revalidating my experience of the last months... Isn't just the support required / coordination / project management / specialised roles / management ... ("overhead") an direct consequence of: - too many goals/priorities over narrow focus on the most valuable thing - too big moonshots expecting it all over accepting the uncertainty of the real world and receiving smaller value (or learning) continuously while investment makes sense - too many meetings / calls to aggregate, filter and proxy tons of information over just interacting directly p2p at once (engineers <-> clients/users) - too many people with free time hard trying to be perceived as useful pretending or making themselves (and everyone around) busy We see and hear it all over the last 25+ years in different forms, rewording everything every few years, but the principles stay the same (and related frustrations of not adhering to them). I'm a strong believer in #xp, #scrum and in the recent years #LeSS as they are just the bare minimum and simple things based on the elementary principles letting you build the simplest approach possible around them tailored to your needs. Let me tell you your opinion on this...