Write a comment...
0/9000
WarningTechnical Debt Event 6/25/2020 was archived. To reactivate, contact the group owner Dylan Wall.
Group
Technical Debt Event 6/25/2020
Suggestions from this post:
- Start a list of technical debts. (This includes all instances where the developers know the code isn’t as clean as it should or needs to be for future development.)
- List and group deferred tasks into workable units.
- Note the consequences of ignoring each unit.
- Keep the list visible.
- Inform teams that rely on delivery releases – like marketing, sales, etc. – that you’re working on technical debt, so that each new release cannot include only new features.
- Schedule regular and frequent time to pay off technical debt.
As an admin, you can use Health Check to identify and fix potential vulnerabilities in your security settings, all from a single page. A summary score shows how your org measures against a security baseline, like the Salesforce Baseline Standard. You can upload up to five custom baselines to use instead of the Salesforce Baseline Standard.
The Salesforce Optimizer app covers most of the same features analyzed in the existing PDF report in a more interactive and actionable format. Quickly identify issues that require immediate attention by using the sortable list view. Read through expert Salesforce recommendations to plan next steps.
Our friends at Traction on Demand do an amazing job here highlighting the process of addressing CPQ Tech Debt........ Feels good to be free!
No one likes a black hole..... well maybe astronomers. Great read on losing tech debt and keeping it off.