This is my personal list of learnings from vtigercrm-5.0.0 release. Feel free to add to this.<\/p>\n
Should focus on usability<\/p>\n
Should focus on UI<\/p>\n
UI changes take time and time must be allocated towards this area much well in advance<\/p>\n
Entire UI revamp in a short time is a very very bad idea<\/p>\n
Do not let negative pressure to develop, defuse it asap. The release is not worth loss of team-spirit<\/p>\n
Good to have positive pressure for some duration only. Do not let it become an obsession.<\/p>\n
Get 5 minute meetings done if required to have a meeting in the first place.<\/p>\n
Observe each team member for pressure\/depression symptoms. If you have, you better act fast!<\/p>\n
Be maniacal about quality<\/p>\n
Break the rules if need be.<\/p>\n
Get the community to join in at the very outset. The community is not an after-thought, it is THE thought.<\/p>\n
Agree to disagree but make it known too.<\/p>\n
Agree if mistakes are made and rectify them. No need to burn energy in defending some crap.<\/p>\n
Stand and explain your ground if you feel that you are in the right ground, but be polite.<\/p>\n
Let not your frustration affect team spirit. Take it 1 on 1 and in a gentle manner. Remember, the team is more important than an individual.<\/p>\n
Keep advance information running 30×7 as things are very very fluid<\/p>\n
Development is not a fixed process. It is inherently dynamic. Accept that and b willing to backtrack if need be. Do not hold on to your words\/ego, not worth the heartburns caused.<\/p>\n
Own up for screw ups and fix them. This will lead to maturity and respect.<\/p>\n
Take risks eg Tag, Chat. You never know what will work as ppl do not themselves know what they need!<\/p>\n
Keep proper docs and have a clear physical and logical demarcation among them.<\/p>\n
Never assume that things will work out well. If things can go wrong, they will – relax that is one of the laws of nature. We are engineers, problem-solvers.<\/p>\n","protected":false},"excerpt":{"rendered":"