5S (methodology) - Wikipedia, the free encyclopedia
John V (?) asked me what 5S was, since I have a picture of it early in the deck, regarding “GTD isn’t the only personal productivity system on the planet.” I told him I didn’t know, but here’s the link to it if you’re interested.
My slides.
This deck probably isn’t fantastically useful to the rest of you, but in case there was a reference you missed, you can maybe find it here.
I tell this story to illustrate the truth of the statement I heard long ago in the Army: Plans are worthless, but planning is everything. There is a very great distinction because when you are planning for an emergency you must start with this one thing: the very definition of ‘emergency’ is that it is unexpected, therefore it is not going to happen the way you are planning.
Agile involves (among other things) cross-functional teams, high-bandwidth communication, and adaptive planning. We know the best ways of achieving these things. The details vary, but when it comes to broad strategy, I don’t think there’s even any debate any more.
- We know that the most effective way for business experts, programmers, and testers to collaborate is to put them on a single team that shares responsibility and authority for success.
- We know that the most productive way for teams to work together is to sit together in a shared workspace and communicate primarily via ad-hoc face-to-face discussion.
- We know that the most successful way for teams to meet market needs is to adjust their plans as they go, forgoing detailed long-term plans in favor of rapid feedback and maximizing throughput and value.
We know this, and yet it rarely happens.