Here's something I drew during one of the sessions showing the dichotomy we face when trying to build and deliver solutions to a business whose key drivers are less cost, more value.
- Value can be delivered quickly but only if its done in increments. Plan to deliver something quick (within a financial quarter) but not dirty.
- Create a hassle map and focus on the big and nasty hassles first.
- Don't throw out everything you've learnt about architectural integrity but instead learn to focus on what matters for the short term. For example architecting for every possible change case may not be relevant if the entire nature of the business is likely to change within the lifetime of the system. Maybe throwing out and staring again is actually an option.
- Adopt a "bring you own" rather than "build your own" philosophy. Learn how to prove the business value of bringing rather than building.
- Do build for scaleability. Be optimistic that the business will flourish and require more not less of your solution. Take advantage of cloud technology to smooth temporary blips in workload.