Save some money by using one ALM product

WIKI - Application lifecycle management (ALM) is the product lifecycle management (governance, development, and maintenance) of application software. It encompasses requirements management, software architecture, computer programming, software testing, software maintenance, change management, continuous integration, project management, and release management

And the best Application life Cycle Management According to Gartner Quadrant

           

And one of the best Documentation tool we can use with TFS is http://www.smartoffice4tfs.com/pages/smart-word-features

Cheers

Prabath Randy

Sales Force whoa whoa wow

Sales force wearable device support SDKs are amazing some of them are built by using HTML5 , JS and CSS.


     https://developer.salesforce.com/wear?language=en


Cheers

Prabath Randy

Managed and Unmanaged Solutions Best Practices

Hi All


        Following are some of the expert's information can be used when you try to use managed and unmanaged solutions.


reasons why I very much prefer to use managed solutions in all environments that are not development environments:

• Solutions can be installed into multiple layers.
• You can build solutions on top of other solutions (solution-level dependencies).
• Additional change management control.
• Option to turn on managed properties on solution components.
• Capability to uninstall a solution and roll-back to a previous customization state.
• Solution publisher can truly own solution components.

Extracted From - http://gonzaloruizcrm.blogspot.com.au/2012/01/managed-or-unmanaged-solutions-in-crm.html

Also how to update Managed Solutions

Create managed solution updates

There are two basic approaches to updating solutions:

• Release a new version of your managed solution
  
• Release an update for your managed solution
  

Release a new version of your managed solution

The preferred method is to release a new version of your managed solution. Using your original unmanaged source solution, you can make necessary changes and increase the version number of the solution before packaging it as a managed solution. When the organizations that use your solution install the new version, their capabilities will be upgraded to include your changes. If you want to go back to the behavior in a previous version, simply re-install the previous version. This overwrites any solution components with the definitions from the previous version but does not remove solution components added in the newer version. Those newer solution components remain in the system but have no effect because the older solution component definitions will not use them.

During the installation of a previous version of a solution Microsoft Dynamics CRM will confirm that the person installing the previous version wants to proceed.

Release an update for your managed solution

When only a small subset of solution components urgently requires a change you can release an update to address the issue. To release an update, create a new unmanaged solution and add any components from the original unmanaged source solution that you want to update. You must associate the new unmanaged solution with the same publisher record as was used for the original solution. After you finish with your changes, package the new solution as a managed solution.

When the update solution is installed in an organization where the original solution was installed the changes included in the update will be applied to the organization. If an organization needs to ‘roll back’ to the original version they can simply uninstall the update.

Any customizations applied to the solution components in the update will be overridden. When you uninstall the update they will return.

Cheers

Randy

It’s time to start thinking about SF – what do you think

I was wondering what was going with SF and Microsoft Deal and finally found the answer.

Hosk Final thoughts

It’s an odd day, I always thought of Salesforce as the natural competitor with Dynamics CRM and although Microsoft were behind (after starting late as usual) it felt to me like they were improving at a faster rate, Microsoft were applying the pressure on Salesforce and that perhaps Salesforce would have struggled with their finances and with Microsoft in the end winning the war.

I appreciate Salesforce are not the enemy but it’s good to have a common foe to rally against.

This partnership seems to give Salesforce a bit of renewed hope and has taken away some of the main competitive advantages Microsoft CRM had over Salesforce (e.g. compatibility with the Microsoft stack) but the actual integration won’t happen until 2015 which is quite a distance in the future

I guess Microsoft have bigger fish to fry and need to get as many people as possible using Microsoft Phones, Tablets and Office 365 but it’s not great news for Microsoft Dynamics CRM re-sellers.

In some ways I wonder with the introduction of CRM online and the new social listening and marketing functionality whether Microsoft are looking at selling Microsoft Dynamics CRM almost as off the shelf software (and not as the XRM tool).  The new helpdesk functionality also lends itself to customers using the system without having to do lots of customizations.

This doesn’t really fit in with big customers who take CRM because they like to have CRM on Premise (don’t get me started with the delayed roll out of features to on Premise) so they can keep their own data and these projects usually involve a lot of customizations.

It seems a bit sad that Microsoft is sacrificing the main advantages Microsoft Dynamics CRM has over it’s main competitor for the greater good of Microsoft’s operating system and mobile offerings.

We shouldn’t forget this maybe annoying Microsoft is also adding loads of new features and software into Microsoft Dynamics CRM at a rapid rate that I think Microsoft Dynamics CRM is still moving forward and will still be making ground on Salesforce but perhaps not at the rate it was previously.

I also don’t think this spells the end or slowing investment in Microsoft Dynamics CRM, it wouldn’t make sense for them to have invested in Microsoft Dynamics so heavily with the recent acquisitions if they were planning on slowing down investment.

You cannot deny that Satya Nadella the CEO Microsoft is certainly making some dramatic decisions and there seems to be a plan of some kind but at the moment it’s not quite clear what direction Microsoft is heading and how this is going to effect all the parts of the Microsoft organisation.

Extracted From - http://crmbusiness.wordpress.com/2014/06/03/understanding-the-microsoft-and-salesforce-partnership-why-and-what-now/

Cheers Boys

Start to Move. Now we are friends