17: If possible, buy instead of build

Interstingly, I just went through this. We had to replace an collection of bought solutions that were duct-taped together. I was part of the team proposing that we build it. Competing with some vendors of SaaS tools and a couple outside consulting teams that would go from either a full…

16: Change during development is Inevitable

Yep. Change happens. We NEVER know everything up front. Even if we THINK we do - Things change over time. The priorities change over time. UX Changes over time. Everything is open for change. Trying to pretend otherwise is to reject the reality of the world. We have to prepare…

15: The More Seen, the More Needed

... I'm not even sure what this one means. I gotta jump straight to the book... OK - Users want more. Keep your documentation. Plan your configuration Procedures. I agree with the intent of this. It shows it's age though. With the bandwidth and web centric nature…

14: Grow Systems Incrementally

Yes. Again, based on the past few principles; I think I'll be in agreement with the book. This is largely recognized as emergent design; thin vertical slices; tracer bullet; walking skeleton... lots of names witih slight variations in their emphasis. All of these are about producing something that…

13: Build Throwaway Prototypes Quickly

I touched on this in Principle 12 - All prototypes should be throwaway, or else you're just doing emergent design. And build them for low effort/cost. It's about quickly integrating feedback. If we spend a long time building the prototype, we'll not get…

Burn out

3 Months ago... That's how long my last post was... bleh... Sorry. Anyway - I burnt out in a few ways. I needed to drop some stuff and the blog got hit. I've got a few posts written that were never scheduled... More of the 201…

12: Build the Right Features into a Prototype

Yes. My take on this is that we're building a prototype to be able to provide users something tangible to get feedback on. Maybe even a proto-prototype to explore internally with the team. "Right Features" is a bit nebulous. It's "Build the features…

11: Build the right kind of prototype

Umm... sure? Tracer bullet? Walking Skeleton? I don't know where this one is really going. As a practitioner of Emergent Design and Evolutionary Architecture... I'll just start coding and refactor the hell out of the system as I go. Practically always functional, definitely always deployable. It&…