Some people wonder what dates we really wrote the agile manifesto... I just found the hotel contract, those should reflect the dates accurately :)
Feb 12-14, 2001
(I don't recall what we did on the 14th, if we met all day, half day or what)
This is the sort of historical revisionism and weak reporting that seriously pisses me off. Sutherland did not invent Scrum in the 80s, Scrum is not the founder of agile, there were 17 people involved, etc etc. That HBR is passing this along is seriously bad history/reporting
Check it out, the Defense Innovation Board has come up with 6 questions to see whether a project fits the term agile or is "agile BS" ! I'm personally pretty happy with these questions: If you had to change one or more, what would you choose?
Possibly the most important thing to think about when looking at Scrum, XP and "Agile" now is that, as they started, they were very anti-management.
so when you say, Scrum/XP/Agile helps "management" oppress the workers, recognize that is how bad management coopted the ideas
1/
A: How long is a story point in real time?
B: How many did you do in your last sprint?
A: 23
B: Then, for you, it's a 23rd of a sprint
A: But the time before that it was 19
B: Then for you at the time it was 1/19th of a sprint.
A: But how long is it really?
B: We answered that.
Trying to find a web site designer local here. Found one says they do agile. I say I need to be able to talk w the designer & programmer. He goes, no, we use an acct rep so designers can work without disturbance.
I'm thinking, Read 3rd value of the agile manifesto?
no doubt hazardous to post this here but:
for most change initiatives, I find my flowchart predicts the future accurately ... imho the core reason being, they are based on Person A deciding that Person B should change. Net result:
* I would LOVE to see counterexamples
Use cases resurface periodically when business people need to work out what's going on.
Here's the use case crib sheet - just copy this as closely as you can and you're probably safe.
I don't normally post on these topics, but this is a really important story for men to read. Incl/Especially the thoughtless "helpful" comments from men
I recall how surprised I was the first time a woman told me how frightening situations are. Now I practice spotting them.
A quick reminder for men: Common events for you can turn into really scary situations for women in a snap.
Case in point: This week I listed a clothes dryer on the Letgo app. Because it was a dryer, a neutral meeting location was impractical. I needed it taken out of my house.
i totally do not know how anyone does a distributed team project- how on earth do they have real design discussions?????
(yes I know some of you claim to be experts at this. I've been trying for 20 years, never can make it work, it just sucks every time)
what fun! I just found a slide on
#HexagonalArchitecture
from 1999 (a talk I gave in South Africa, June 22, 1999). I thought it was pre-2000, but couldn't find when.
Agile elevator pitch (literally).
(exec enters elevator)
exec: what's agile?
me: early delivery of business value.
exec: what else?
me: reduced bureaucracy
exec: sounds good
(exits)
Note from a friend: "Got frustrated with waterfall. I organized a switch just within the team doing the work - including myself- to a kanban board on our glass wall with sticky notes. Already have more done in the last 3.5 hours than the prior 3 days."
#AgileRocks
Dear people: About use cases
Ivar Jacobson, the inventor of use cases and co-creator of component-based development, UML and RUP, and Alistair Cockburn, author of a popular book on use cases and also co-author of the Agile Manifesto, got together to unify, simplify and
finally got driven to write a little article on Agile is Not Dead, Quite the Contrary. Got tired of all the nonsense. Waiting for it to settle down a moment before I post.
(Some settling of contents may occur, this package sold by weight not by volume)
the electricians bid 3 days a large but normal job, we are now at two weeks, with an unknown "2-3 days" left.
so don't give me any more of that "software people can't hit estimates" stuff. Electricians just install wires, and they can't do better, even on a 3-day job.
#HexagonalArchitecture
@JuanMGarridoPaz
offered this pic I was looking for, showing the Configurator putting the system together. Haven't seen this pic before, was missing to my mind.
Any others with similar /different variation?
Both of my new books are now available in epub off my Ecwid store.
For the desperate:
User stories - Use cases - Story maps
Hexagonal Architecture Explained
we just refined one sentence in the
#hexagonalarchitecture
definition:
Intent
Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases. ...
regarding measuring programmer productivity. My IBM boss in 1992 said he'd been looking for 20 yrs and found nothing useful, nothing that wasn't easy to hack. Since then I've looked for 30 more yrs and found same. Many stories, but this cartoon says it all:
happy triple firsts at CrossFit, 1st time doing the whole Level 1 (beginner's level) without cheating or cutting corners, first 5x5 dumbbell bench press w 50 lb dumbbells, first time getting these kip-chinups to work :)
Atlantic did a lovely review of the agile manifesto meeting. Caroline Nyce recorded everything and came back a few times w more questions. Carefully researched, neatly written:
i have a question - i've tried explaining
#hexagonalarchitecture
various times & ways. Still, ppl keep writing articles to explain it, & others go, I'm trying to understand it.
so: where's the sticking point? what needs clarification, or what isn't clear?
thx for help
Just read this great sentence :
"The Agile certification industry has developed a commodification machine, which cannot recover to deliver differentiated approaches for businesses."
I think that is true, and quite thought provoking
(agile bubble)
from
@engineering_bae
i was once running 8 initiatives. To keep focus, this was my work board. Project > Theme > section > task. Outermost tasks moved close in for most important.
Never more than 2 hot tasks / initiative; then selecting the top initiative/top task. Constant attention to priorities.
@sbellware
Here is a far more eloquent and accurate description of the problem presented in a far less self-righteous way years ago. The insight is not new
Note it comes from Ron Jeffries, one of "Agile’s own leaders," which shows the premise is objectively wrong