Today we’re going to talk statistics and semantics. I’m going to do so via the medium of one of Twitter’s favourite stats 1.7% (aka “intersex is as common as red heads.”). The statistic comes from Fausto-Sterling’s work, which you can see a review of
https://t.co/fze95pGwN2
Do intersex women have penises? I\u2019m seeing this thrown around a lot, so let\u2019s address it. Firstly, as ever, let\u2019s all remember that intersex =/= trans, and he conflation is harmful and ignorant. Now let\u2019s get on with some science\u2026
— Mrkhtake2 (@mrkhtake2) August 25, 2018
More from Tech
A common misunderstanding about Agile and “Big Design Up Front”:
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
You May Also Like
Ivor Cummins has been wrong (or lying) almost entirely throughout this pandemic and got paid handsomly for it.
He has been wrong (or lying) so often that it will be nearly impossible for me to track every grift, lie, deceit, manipulation he has pulled. I will use...
... other sources who have been trying to shine on light on this grifter (as I have tried to do, time and again:
Example #1: "Still not seeing Sweden signal versus Denmark really"... There it was (Images attached).
19 to 80 is an over 300% difference.
Tweet: https://t.co/36FnYnsRT9
Example #2 - "Yes, I'm comparing the Noridcs / No, you cannot compare the Nordics."
I wonder why...
Tweets: https://t.co/XLfoX4rpck / https://t.co/vjE1ctLU5x
Example #3 - "I'm only looking at what makes the data fit in my favour" a.k.a moving the goalposts.
Tweets: https://t.co/vcDpTu3qyj / https://t.co/CA3N6hC2Lq
He has been wrong (or lying) so often that it will be nearly impossible for me to track every grift, lie, deceit, manipulation he has pulled. I will use...
... other sources who have been trying to shine on light on this grifter (as I have tried to do, time and again:
Ivor Cummins BE (Chem) is a former R&D Manager at HP (sourcre: https://t.co/Wbf5scf7gn), turned Content Creator/Podcast Host/YouTube personality. (Call it what you will.)
— Steve (@braidedmanga) November 17, 2020
Example #1: "Still not seeing Sweden signal versus Denmark really"... There it was (Images attached).
19 to 80 is an over 300% difference.
Tweet: https://t.co/36FnYnsRT9
Example #2 - "Yes, I'm comparing the Noridcs / No, you cannot compare the Nordics."
I wonder why...
Tweets: https://t.co/XLfoX4rpck / https://t.co/vjE1ctLU5x
Example #3 - "I'm only looking at what makes the data fit in my favour" a.k.a moving the goalposts.
Tweets: https://t.co/vcDpTu3qyj / https://t.co/CA3N6hC2Lq