تغريدة مثبتة
Stacia Heimgartner Viscardi
3.1K posts

Stacia Heimgartner Viscardi
@AgileEvolution_
Open PatternsMaster helping teams and orgs create bespoke business agility solutions since 2003. Freeing worms from cans everywhere. CEO AgileEvolution.
New Jersey, USA انضم Temmuz 2011
1.6K يتبع1.7K المتابعون

LMAO... and quite impressed with Open AI chatbot
Jonathan Stray@jonathanstray
Open AI chatbot prompt: "Rewrite Baby Got Back in the Style of the Canterbury Tales." Once upon a time in the land of Canterbury A lady fair with a behind so hearty Walked in the room with a waist so small And a round thing in front of us all ...
English
Stacia Heimgartner Viscardi أُعيد تغريده

@agileschools progress is still progress, no matter how many twists and turns!
English

@mstine matt, this is great! this is by and large how my brain works but i could never quite put it into words. thank you!
English

@AgileFaye @agileschools agreed .. “here’s a concept i read about, applied, and learned x/y/z” is very useful and inspiring. Or “here’s how i connected it to something else i was doing already and what i learned as a result”… the creation of a new pattern or thing is always exciting!’
English

@agileschools To be clear, reading a book and relying on its content to try something new where you work or live, and your preso is about what YOU learned = what everyone wants
English

@agileschools getting off airplanes for awhile did me a world of good.
English
Stacia Heimgartner Viscardi أُعيد تغريده

@neil_killick i utilize an outcome-based prioritization model for complicated stakeholder wrangling. Get them in a room and score their requests against a common set of outcomes together and discuss. This reveals the squeaky wheels and lower value items very quickly.
English

MoSCoW is supremely dangerous. Capabilities a system "must have" are not something a group of stakeholders should decide. Plus you will always end up with over 80% homogenously prioritised "musts". If you must ask stakeholders to prioritise, use a pure sequencing method instead.
Jason Pursey@jason_pursey
@duarte_vasco Must: we do not negotiate on these Should: we negotiate on these but I always win Could: we negotiate on these and you always win Would like: these are only here so I can say I've compromised on something
English

@agileschools … but to just create component teams and call it a day… seems like a choice amongst other possibilities. Cost, time, etc all factor into these decisions. In some cases it may be the right decision. i think that politics and turf sometimes fuel these decisions.
English

@agileschools I found myself internally debating this one. depends, like most things - how big the product gets, how many other uses a component of a system grows to satisfy. The question that remains in my mind: keeping a system small and easily changeable, even when it grows,…
English

@agileschools … i suspect that’s the real hard work. I think of basic architectural principles and good coding and testing practices which in theory aim to keep things small and flexible…. and when things get too big and unwieldy rearchitecting to rein it in….
English

@RonJeffries 🤣 I was worried there for a minute, Ron!
English

@RonJeffries omfg. looked at the publish date - was hoping it was April 1. Nope. *wipes tears*
English

@agileschools @michelesliger Thank you, John! Michele wrote all the hard chapters! ;)
English

I recommend @michelesliger @AgileEvolution_ book in every CSM class for those in the traditional pm world. amazon.com/Software-Proje…
English

John gets it, pretty much every "agile" shop I see doesn't.
John Miller@agileschools
Epics are not meant to be completed.
English



