Pages
Wednesday, December 31, 2008
Happy new year
It is giving us another 365 days to dream, achieve and enjoy the life. Are we ready for this?
I am sure we are. We are so lucky; our mother nature always opens up a day or year afresh.
We just need to dream and put a plan to execute and enjoy fruits.
Don’t we get our subconscious mind reminds us very often the old saying “you reap, what you sow”?
It’s time again to sow new seeds in our mind and grow them deep rooted to harvest very often.
I am sure you are ready with such seeds for your future.
Wish you a happy and prosperous new year.
Let’s create happiness and prosperity by being innovative and having fun.
Monday, December 29, 2008
Defining and predicting the project success
Of-course the project success depends on many factors like skills, tools, process, scope and timelines.
When it comes to resources, project success predictability can be measured by resources competency, process adherence and metrics collected over the process.
Metrics which are being collected must be useful in determining the project health in terms of the following
1. Is there any risk in the project?
2. Is there any risk at resources capacities?
3. Is there any risk of meeting delivery time lines?
4. Is all stakes holders getting right information during project execution?
5. Is project in predictable state?
This makes the leaders to have right environment to develop and use factors of competency, process and metrics based on process.
In this lines, I have come up with a program or tool to use and improve competency, productivity and predictability. I called this as mentoring program to make everyone powerful and able contribute on proactive manner.
My mentoring program is concentrated on the following items
1. Increasing Technical capability
2. Defining and adhering to suitable process as per the project environment
3. Leadership
1. thinking as whole release or project
2. building trust
3. Ownership or entrepreneurship
4. maintaining relationship
I will talk about these details in next blog
Thursday, December 18, 2008
Importance of code reivew in agile development
Code review has a great potential to reduces bugs count and increases the productivity on long run.
It provides quality code in terms of
1. following coding standard to make sure everyone understands your coding.
2. identifying bugs development stage reduces the number cycles between dev, qa or even from production to development.
3. catching performance bottle necks like loops, memory leaks, reducing unnecessary costly calls to db and so on
Code review will really gives you more learning and it multiplies your knowledge as you become aware on how other person think and code.
You must feel great to get your code reviewed to make sure you're strong in your delivery by using another pair of eye to catch any unwanted things that you don't want to put in to code base.
When you get comments on your code, your confidence level on your coding style increases and you become quality coder.
Sunday, October 26, 2008
SAAS : Challenges
- Data security
- Scalability for growing customer base
- Customer specific demands
- Customer support on functional and technical
- Changing customer needs
- Dynamism in the market
- Performance
SAAS Design principles
SAAS Design Principles
- Meta data driven
- Configurable
- Multi-tenant
- extendable design to suit to changing markets
- Internationalization
- Service Oriention architecture
- Asychronus request
- Data handling - archiving and purging data
- Easy to integrate with other applications
- Scalablity
- Availablity and reliablity
- Security
- Performance
- Monitoring and auditing
- Techincal and business support
Tuesday, October 21, 2008
SAAS
There is no limit for human mind to think beyond umimaginable thoughts to provide a change in industry. Industry is in such a situation where lot of money is going on operational cost of IT enabled services. This invloves initial purchasing of software solutions and its supporting hardware. Apart from initial investment there has been always a maintance cost. This has become more than anticipated. Other side ever changing requriments and new technologies also put companies on trememdous pressure to keep them upto date.
Once the IT services were more of boon to reduce operational cost and now IT services maintanence has become a gaint expenditure. Problem alwasy demands a solution. It is to put IT industry in new dimentions with more creative and innovate ideas. Here came a concept SAAS to reduce IT operatoinal and maintainance cost.
SAAS denotes software as a service. Another name for this is on demand. Concept is not very new in terms of application, but it is new interms of using it for the benifit of consumers.
This makes the IT enabled software provided as servie and consumers just subscribe it and start using it. It removes all hurdles of initial purchasing of hardware, software and its operational cost. It has become a great boon across industry as they don't need to commit for unforseen benefits for future. Now IT services is available as service, try it and if you like to continue you can subscribe for required period. As there was no commitment of procuring all hardware and maintiance setup, It is easy to either discontinue or continue with service. There is no lump some investment. It is steady investment year after year. It is very easy for customer to move on to next generation products based on changing market needs.
In next blog we will see design principles of SAAS and other supporting information for SAAS
Saturday, October 18, 2008
Focus
I strongly believe that every one has value. It is just that they need to focus on what they are doing. If a person focus is on building muscles, he certainly spend more hours in exercise hall. It makes him happy and finally he achieves a great shape of muscles body structure. Similarly, if he focuses on what is he working on, he certainly achieves it irrespective of any problems.
Focus builds capacity
Focus builds capability
Focus creates concentration
Focus motivates for achievement
Focus creates interest
Focus generates unusual results
If focus is only on output, you certainly work on outcome irrespective of how you did it.
If focus is on output, but you need quality out put, then out come is quality output