Frameworks are standard practice in every other language, yet plenty of SAS projects are still built without one. Below are the reasons teams adopt a framework, the symptoms that suggest your project is running without one, and - if you’re a project manager or sponsor - what you should expect to see in your developers’ git repo.
Reasons to use a framework:
- Faster on-boarding of new developers
- Project Documentation & Testing
- Support for multiple platforms
- Pre-configured linting rules
- CI/CD, out of the box
- Faster development
- Maintainability
- Build tooling
- Community
If your #SAS project is running late, costing more than expected, or failing to deliver - it’s very possible that far too much time is being spent on:
- The HOW rather than WHAT should be done
- Investigations / debugging
- Fixing regressions
- Manual re-runs
- Deployment
As a project manager or sponsor of a SAS project, you should absolutely expect your developers to push the following to your GIT repo(s):
- Updates to documentation with every sprint
- Updates to tests with every sprint
- Linting rules / lint fixes
- CI/CD pipelines