I once heard a story, that I cannot corroborate; but sounds too true in general, and with our approach on so many things.
Russia had an immense work force in the earlier 1900’s, but lacked the mechanization to take them to the next level in terms of production, especially for export and their financial security. They also lacked the cash to import any measurable amount of equipment to reverse that position. It’s a catch .22 if I’ve ever heard of one.
Their solution? Buy (or procure) one of what they needed, reverse engineer it, and make their own. The story I heard was of a Japanese tractor. The Russians had copied it exactly, but failed to understand that the cracked engine block was a flaw, not part of the design. You can imagine where it goes from here. I did a little research and stumbled on a thread about a B-29 that crashed in Russia in WWII, and they appeared with an exact replica, called the TU-4, patched hole in the fuselage and all!!
This is still true of us today! We adopt a process or approach, and seem to follow it, flaws and all, without question. Agile methods and their supporting frameworks are GUIDELINES, not the rule or etched in stone!
A very simplified example of this is the retrospective. I find a lot of teams in a room, staring at a projected screen, and one guy asking, what worked, what didn’t? It’s quiet, only one or two folks are contributing, and it’s an overall, rather lackluster experience- without much value. When I ask, “why do you conduct your retro that way?” The response invariably is “That’s how we always do them.” </shakinghead>
You have to do what makes sense, and you have to make the process work for you! Embrace change, and innovate your process!
This is a very complicated case, Maude. You know, a lotta ins, lotta outs, lotta what-have-you’s.