I really agree with the keep it simple approach. When scoping out a software project, I try to scope the minimum functionality that will meet the customers needs. I find this hard sometimes, so when I feel myself wanting to add a function or feature that I believe is good, but possibly beyond the basics I write it down (just to get it out of my system) but place it in a list of ‘Potential Enhancements’ that are for consideration beyond the initial project. This is because I can’t afford to complicate the project beyond what is needed.
I came across a blog post that also embodied this philosophy within the software development phase:
- Simple Things Should be Simple, Complex Things Should be Possible … – Oct 4, 2009 … Project Management · Tips · Windows · RSS Feed. Blogs to Visit. Joel on Software · Coding Horror · Rintrah Roars by Giovanni · Rocco Savella …
It’s important to bear in mind the ‘Keep it simple’ philosophy throughout a project, if you stick to the minimum required to meet the customer deliverables you’ll be much more likely to deliver. If you try to get fancy, you can come unstuck!
