Yes.. Slowly but peacefully, The Application we are developing (at work) is getting stabler and more release-prone [Trademark :)]. I am getting an hour more in my day for myself.I would like to share some of my personal Lessons-learnt from the last two months.
I would consider we are more Agile a project than the ones I worked in before. However, we don't restrict much to methodology. The first noticeable lesson for me here was - No matter how much you want to avoid bureaucracy, There will be some. Even in the most Agile development. And I feel the easy way to put this situation in control is to standardize this bureaucracy. Leaving the loose ends open to bureaucracy will only keep your Agility down. When ever you see such kind of things, repetitive or inhibitive, wrap it into a standard routine. Bear in mind, don't make it into a process - you will only make it more bureaucratic - be open for changes, but establish a routine.
Terminology and Conventions - of all things, speed is accessed by communicating correctly. If two clever minds are not able to communicate - in code, in practice or in regular talk - they are no better than two not-so-clever minds.
Think about Scalability Early - If we are working on highly scalable apps, that notion needs to be on developers mind from the beginning. And Design has to abide by this hard-and-fast-rule. Look at more scalability principles.
And finally be prepared for change. This I leave this as very vague open point. There are so many places, we restrict ourselves for change. code, process, design. All this would be a lot different at migration time than where we started in design. The key is open-ness and changability.
I would consider we are more Agile a project than the ones I worked in before. However, we don't restrict much to methodology. The first noticeable lesson for me here was - No matter how much you want to avoid bureaucracy, There will be some. Even in the most Agile development. And I feel the easy way to put this situation in control is to standardize this bureaucracy. Leaving the loose ends open to bureaucracy will only keep your Agility down. When ever you see such kind of things, repetitive or inhibitive, wrap it into a standard routine. Bear in mind, don't make it into a process - you will only make it more bureaucratic - be open for changes, but establish a routine.
Terminology and Conventions - of all things, speed is accessed by communicating correctly. If two clever minds are not able to communicate - in code, in practice or in regular talk - they are no better than two not-so-clever minds.
Think about Scalability Early - If we are working on highly scalable apps, that notion needs to be on developers mind from the beginning. And Design has to abide by this hard-and-fast-rule. Look at more scalability principles.
And finally be prepared for change. This I leave this as very vague open point. There are so many places, we restrict ourselves for change. code, process, design. All this would be a lot different at migration time than where we started in design. The key is open-ness and changability.