This is a lesson we made almost two years ago. Being mostly software centric, we refer to this as the "patch a day principle". We even push it further than the author of the post by targetting deliverables on a "almost daily basis".
- Amongst developers, the code is an awesome communiation tools.
- You cannot catch an error much sooner than the next day it is commited.
- In distributed contexts, the time zones often plays in your advantages and review happens over nights.
As you can see by the name of the "principle" this is something very software engineering centric. There is no reason to not apply this accross all roles involved in a project though: Documentation, QA and UX.
This is about predictability and this is a requirement common to all activities on a project. Make your project lead and your customer happy through a predictable team using frequent micro-deliverables!
No comments:
Post a Comment