Can you tell me what American Express, Apple, Google, and Spotify have in common? They are all leaders in their industry and all promote a learning culture. Research by Edward Hess at the University of Virginia Darden School of Business wrote “companies that learn fastest and adapt well to changing environments perform best of over time.” These organization create a learning culture from top to bottom. Below are three strategies to help implement a learning culture in your IT department.
Traditional development practices had precise roles and responsibilities. Team members were confined to those roles and were not supposed to think outside of them. The belief was that specialized roles allowed people to work faster by focusing on their work only.
We have been preaching agile and DevOps for the past few weeks as ways to improve productivity and speed of your Salesforce development. Today, I would like to present a recent survey demonstrating results organizations have witnessed by implementing agile. Sort of a State of the Union on agile.
Last week I discussed the necessity for speed in Salesforce development. But speed is great only if it is matched with the same level of quality.
Salesforce is an interesting development platform when it comes to release management. They provided a multitude of ways to manipulate metadata on the platform. Part of the reason why there are so many ways to deploy metadata stems from the overall maturity models Salesforce has undergone over the past (almost) 20 years.
There are multiple ways to develop on the Salesforce platform. There is easy point and click development or elaborate apex code and Visualforce page development. Point and click development can quickly be tested and implemented into Production for users. Large complex developments require passing through multiple development and testingsandboxes before being deployed to reduce business risk. These large development undertakings require a release management plan establishing sandboxes for development and testing, providing a pathway to Production.
Tom DeMarco said in his book PeopleWare Productive Projects and Teams that “Quality is free, but only to those who are willing to pay heavily for it”. My interpretation is that quality is not given but earned. In the stress of budgets and deadlines, quality is an after thought. Software quality is earned by taking the time to properly test code before deploying it into Production.
Have you heard of the 80% wall? It is a theory when developers feel like they are 80% complete with a project only to realize that they still have 80% to finish. This feeling typically hits programmers during the re-write stage after seeing a long list of errors. Major re-writes can be reduced or even eliminated with introducing Test Driven Development (TDD) to your development processes.