Stacia Heimgartner Viscardi

3.1K posts

Stacia Heimgartner Viscardi banner
Stacia Heimgartner Viscardi

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 Bergabung Temmuz 2011
1.6K Mengikuti1.7K Pengikut
Tweet Disematkan
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
Scrum is a system integration test to see if it's possible for an organization to deliver value in a Sprint. That test reveals the system's failures, or impediments, that we then must go and fix.
English
9
132
282
0
Todd Werth
Todd Werth@twerth·
How do you measure developer performance? Wrong answers only
English
274
25
192
0
Stacia Heimgartner Viscardi me-retweet
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
Retweet should be called Regurgitweet. Regurgitweet this.
English
0
2
2
0
John Miller
John Miller@agileschools·
Sometimes it is 2 steps back. Then half step forward. And other half step. And another. A few injuries hurt my progress. Inching back up, safely.
John Miller tweet media
English
1
0
4
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
0
0
0
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
1
0
3
0
Faye Thompson
Faye Thompson@AgileFaye·
@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
1
0
4
0
John Miller
John Miller@agileschools·
My grumpy tweet of the day: Conference sessions around someone reading a book they did not write and giving us a book summary of it should not exist.
English
6
2
17
0
John Miller
John Miller@agileschools·
Reflecting on a convo. I admit to having some major insecurities. Lots of reasons from my childhood. Not sure how, but, the pandemic helped me shed them. Perhaps a test of resilience? I am much more comfortable and accepting of myself today than 2 years ago.
English
4
0
12
0
Stacia Heimgartner Viscardi me-retweet
Matt Wallace
Matt Wallace@MattWallace888·
ELON MUSK JUST ENDED JEFF BEZOS’S ENTIRE CAREER WITH ONE EMOJI 😵
Matt Wallace tweet media
English
449
796
7.5K
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
0
0
2
0
Neil Killick
Neil Killick@neil_killick·
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
10
12
73
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
0
0
0
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
2
0
1
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
Give every component team a product owner and call it agile. Transformation done.
English
1
0
3
0
Stacia Heimgartner Viscardi
Stacia Heimgartner Viscardi@AgileEvolution_·
@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
0
0
1
0
John Miller
John Miller@agileschools·
Going to create the SBOCO - Scrum Book of Conflicting Opinions. Who wants to join me?
English
7
1
15
0