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).
- Best practices in software process
- BP-A.1: Identify an initial group of stakeholders and iteratively refine it
- BP-A.2: Elaborate a communication strategy for stakeholders
- BP-A.3: Identify, analyze and manage requirements
- BP-B.1: Monitor and assess available technologies
- BP-B.2: Elaborate an approach for documenting processes and artifacts
- BP-B.3: Track the changes in relevant artifacts
- BP-B.4: Support the build&delivery process with automation
- BP-B.5: Record and manage issues encountered with the product
- BP-B.6: Verify licenses of the used libraries
- BP-C.1: Identify and manage risk factors that could negatively affect the product
- BP-C.2: Identify relevant quality characteristics and test conditions, and provide verification criteria for them
- BP-C.3: Elaborate and maintain a quality plan for the project
- BP-C.4: Apply adequate methods to verify the outcome of development activities
- BP-C.5: Monitor relevant quality parameters
- BP-C.6: Periodically validate the product with project stakeholders
- BP-C.7: Refine the quality assurance process based on retrospection
- BP-D.1: Manage skills of the team members and skills required in the project
- BP-D.2: Provide effective, adequate and reliable means for communication within the team
- BP-D.3: Define and implement an effective decision making process
- BP-D.4: Manage the schedules and assignments of the team members
- BP-E.1: Plan early and implement adequate maintainability-related activities
- BP-E.2: Elaborate a strategy for managing maintenance issues
- BP-E.3: Identify and evaluate available options for implementing a change request
- BP-E.4: Define a procedure for deploying changes to running services