It baffles me how easy some people are to dismiss techniques and perspectives that are advocated by developers as "something for developers" and thus not for business or product management:
These are all concepts meant to improve delivering the right product and delivering the product right. Thinking it's merely developers doing their thing outside the realm or concern of product management is so detrimental to both.
Key to successfully complete a #DigitalTransformation initiative that generate real value is a proper definition and understanding of the requirements.
Asking to business people to define them in detail without knowing the Digital Opportunities you have may limit the benefits you could built.
You can overcome this risk by considering requirements definition as "High level wishes" (user story) a goal of the #Agile project exactly as their development.
It will be useful both for developers to enter properly into the topic and for the business resources that will "see" their needs from a completely different perspective.
This Is what I do as #scrummaster everytime i have that opportunity.
Do you follow a similar approach? Which suggestions do you have?
Yep - this seems like a good approach. The "high level wishes" sounds like getting the business people to set direction, without dictating the details, right?
Frankly, I see way too little of this inside large enterprises. "The business" is commonly too far removed from agile teams, and their role is represented by some senior employee in the same IT team. They are usually very skilled, but still not living the daily challenges of someone for whom we build a solution.
Mummy says SAFe isn't really agile, like when I try to run in my big boots n I can't go fast! 🥾🐢 I guess in compootah land, things aren't always what they seem! 😄💻 #KidCodes#SAFeNotAgile#CompootahSurprises#SAFe#agile
@airwhale
Fully agree with you. #SAFe is a process, #agile a mindest. If you feel that SAFe hinders you to some extend, what prevents you from adjusting it, e.g. by valueing Individuals and interactions a little bit more and processes and Tools a little bit less? Within a PI, you even may want to respond to change instead of following a plan.
I'm starting to think that agile is an unhelpful distraction. The only times "agile" had succeeded it's been common cause, not cause-and-effect... There's nothing inherently positive or negative in the philosophy, but it does (traditionally) go hand in hand with things like software crafting which ARE helpful.
@jocrossick lukewarm take: #agile is a term coined by corporations to try to shoehorn useful development practices into their bureaucratic reality. The two are inherently incompatible so this leads to ruin. I’ve been in meetings where I urged that we need to change our plans now since we set on the wrong path, and the response was essentially “we will consider this for the next sprint.” Incidentally “sprints” were also month-long. It was a disaster.
#ResponsibleAgility tip: it can be useful on #agile teams to have a rule that says the expert speaks last. It lets other points of view be explored without "anchoring" to the expert point of view. Experts should listen to the conversation with an open mind - they can learn!
#PDX#trimet#publicTransportation I 💚 the No. 6 bus line. Though this AM is my first time riding again since…well you know. It’s still here for me, just a few blocks walk from chez moi, goes straight to a lot of places I need to go. Today, it’s OR Conv Ctr for #GSG#GlobalScrumGathering#agile and my peeps.
@PavelASamsonov this gives me PTSD. I especially like how all the other departments are simply passing through on their journey through #Agile, and the #developers are the ones on the hamster wheel of death.
Next time someone preaches for something they claim is ✨ #agile ✨ and begins with the usual speech about "planning to build a car but beginning with a skateboard", ask them if this is an accepted methodology in the automotive industry.
Agile processes tend to use a LOT of post-it notes. A LOT of post-it notes. Why?
Mary Poppendieck is one of the originators of agile processes, coming up with lean software development. Before that she worked on lean manufacturing, a precursor to agile.
#ResponsibleAgility tip: most #agile teams would do well to act on the mantra "Stop starting and start finishing." Too many things in progress is a recipe for being slow and demoralizing to the team. Get things done. Repeat: Get things done. Stop starting - start finishing!
#ResponsibleAgility tip: strong facilitation skills are needed during a #agile retrospective. Facilitating is NOT the same as "leading". The facilitator needs to maintain a neutral stance and let things play out. Non-judgmental and neutral are keys to helping people engage.
#ResponsibleAgility tip: you strike gold during a #agile retrospective when an item appears on both the "good" and "bad" lists. This shows a misalignment of values among the team and deserves a discussion to gain alignment. Something shouldn't be good to some and bad to others.
#ResponsibleAgility tip: repeating the same #agile retrospective format can become less engaging over time. Switch the format. There are many ways besides "What went well? What didn't go well? What do we want to change?" Explore and have fun with retrospectives!
Creatives (including game developers) and engineers (including software developers) agree: get a minimal rough draft out there ASAP, then iterate.
The difference is in how stable each iteration has to be. This is what makes video game development so much harder than tabletop: changing a design idea is really expensive.
Agile was born with the #AgileManifestoOfSoftwareDevelopment, of course.
Soon afterwards, #agile became #scrum. From then on, it only got worse. #Agile became a ‘training’ thing.
But ‘agility’ (just as actual #lean or #quality) is and must be a different theory about how to design and organize work and value creation. It requires re-thinking organization – and put #management thinking on the garbage heap of history. #Training or #certification or #agilecoaching won’t help people rethink organizational theory.
The #Agile movement avoided the theory problem. That’s why it has been so popular and also why it failed, utterly and completely.
The joy of planning poker bingo from the first round. Is it that we're REALLY on the same page or did everyone vote with the number as a placeholder when things are unclear, but “we can figure it out within a 3”?