transparency is undeniably more efficient. Developing products on your own with inadequate checks and balances for long stretches of time might seem acceptable, or even cool, for a while -- if you're inexperienced or a cowboy. But in reality, it's a burdensome and buggy process. It's rife with questionable decisions, bad habits, and shortcuts. Egos get tied too closely with methods and products. Change causes pain. Troubleshooting and maintenance becomes a real killer. And pity those who inherit the lone wolf's pile of work later on. Lean-Agile's systematic approach helps ensure that the entire team is aware of what is being worked on and how the work is progressing. Tracking tools (we use FogBugz to good effect), Kanban boards, incremental unit- and acceptance-testing, daily standups, iteration planning sessions, retrospectives, and vigilant facilitation at each point in the process help to keep team members from straying off course or going underground.