The catalogue of best practices is a collection of recommendations for software development teams, concerning all aspects of the software lifecycle and the team organization.
The practices have been captured based on the the survey and interviews with the GEANT teams, supported by the Geant Software Maturity Model (GSMM). There are currently 24 Best Practices, split across 5 areas, as listed below:
- A template of a best practice
- BP-A.1: Identify stakeholders
- BP-A.2: Establish communications with stakeholders
- BP-A.3: Collect requirements
- BP-B.1: Assess available technologies
- BP-B.2: Set up documentation
- BP-B.3: Manage artifacts
- BP-B.4: Automate build & delivery
- BP-B.5: Manage product issues
- BP-B.6: Manage sideground IPR
- BP-C.1: Manage risks
- BP-C.2: Identify product success criteria
- BP-C.3: Implement a quality plan
- BP-C.4: Verify outcomes
- BP-C.5: Monitor quality
- BP-C.6: Validate the product with stakeholders
- BP-C.7: Refine the quality assurance process
- BP-D.1: Manage team skills
- BP-D.2: Establish internal comms
- BP-D.3: Implement a decision-making process
- BP-D.4: Manage team assignments
- BP-E.1: Design for maintainability
- BP-E.2: Manage maintenance issues
- BP-E.3: Implement a change request process
- BP-E.4: Define a change implementation procedure
- Catalogue of Common Best Practices with outcomes
- Common Best Practices from the PLM perspective