If you aren’t familiar with the Widgets of Wisdom feature, see the explanation and disclaimer here.
- Address the unknown that the team identifies. If they don’t understand something in planning, clear it up before execution begins.
- Some architectural decision must be big and early. These are often based on business requirements, not technology. Java vs. .Net, as an example.
- If metrics are prescribed to a team, explain how they will be used. Metrics cause fear, mitigate that fear.
- You can prescribe Agility, but not hyper-performance.
- Part of the maturation process of Agile is the tendency for people to over-analyze the holy heck out of it. This is relly a reaction to the cost of software development and the incredible amounts of historical waste in the industry.
- CEOs do not care about code coverage. Speak to them appropriately about quality.
- Earned value reporting is ridiculous.
- “Don’t wait until the customer is screaming to optimize for performance.” — Thanks, Kevin.
- Deliver less, but sooner and more often.
- “Daddy, is that your new OOBE?” – My kid when I opened my new MacBook. “Yes, it is, son. Yes, it is.”