Glossary of Practices
Analysis
Examining systems to understand how they work and how they should change.
Approvals
Getting formal approval for various project stages.
Automated Testing
Writing and running tests for individual units or components of the software.
Automation
Using machines to perform repetitive tasks.
Change Management
Managing changes to systems and organisations in a systematic way.
Coding
Writing software to meet a required feature.
Configuration Management
Managing and maintaining configuration settings of the software.
Contracts
Defining contractual obligations and agreements.
Debugging
Identifying and fixing defects in the software.
Delegation
The practice of assigning responsibility and authority to others to carry out specific activities or tasks.
Demand Management
The practice of forecasting, planning, and managing the demand for resources to ensure that the best use is made of them.
Demo
Demonstrating the software to stakeholders.
Design
Designing the high-level structure of the software.
Documentation
Creating documentation to describe the software and its use.
Estimating
Estimating the time and resources needed for tasks.
Fundraising
The practice of securing funding from investors to support the growth and development of a startup.
Integration Testing
Testing combined parts of the software to ensure they work together.
Issue Management
Logging support issues and tracking their resolution.
Marketing
Managing communication strategies to promote the software and engage with the target audience.
Measurement
Quantitatively evaluating the software against benchmarks along some defined dimension.
Meeting
The practice of gathering team members to discuss project progress, address issues, and make decisions.
Monitoring
Continuous observation and tracking of a system, team or person, perhaps with respect to performance, security or availability.
Outsourcing
Hiring external resources or companies to handle parts of the project.
Pair Programming
Two developers working together on the same code.
Performance Testing
Testing to ensure the software performs well under expected workloads.
Pressure
The practice of exerting influence on team members to ensure tasks are completed on time and to a high standard.
Prioritising
Defining the Minimum Viable Product and planning development priorities.
Prototyping
Creating early models of the software to test concepts and ideas.
Redundancy
Ensuring backup systems are in place to prevent failure.
Refactoring
Revising code to improve its structure without changing its behavior.
Regression Testing
Testing to ensure new changes do not adversely affect existing functionality.
Release
Deploying the software to production.
Requirements Capture
Gathering and documenting the requirements for the software.
Retrospectives
Conducting regular reviews to discuss what went well, what didn't, and how to improve.
Review
Conducting systematic reviews of work done.
Runtime Adoption
Implementing and adhering to specific standards and libraries.
Sales
Managing the sales strategy to drive software adoption and revenue generation.
Security Testing
Ensuring the application is secure by identifying vulnerabilities.
Stakeholder Management
Managing relationships and communications with stakeholders.
Standardisation
The practice of establishing and adhering to standards to ensure consistency, compatibility, and quality in software development.
Terms Of Reference
Defining the scope and objectives of the project.
Tool Adoption
Implementing and utilising specific tools in the development process.
Training
Providing guidance on how to use the software to users or developers.
User Acceptance Testing
Having a customer representative available onsite for feedback.
Version Control
Using version control systems to manage changes to the codebase.