45 docs tagged with "Practice"

Demonstrating the software to stakeholders.

Creating documentation to describe the software and its use.

Conducting regular reviews to discuss what went well, what didn't, and how to improve.

Conducting systematic reviews of work done.

Providing guidance on how to use the software to users or developers.

Using machines to perform repetitive tasks.

Managing and maintaining configuration settings of the software.

The practice of forecasting, planning, and managing the demand for resources to ensure that the best use is made of them.

Continuous observation and tracking of a system, team or person, perhaps with respect to performance, security or availability.

Ensuring backup systems are in place to prevent failure.

Deploying the software to production.

Writing software to meet a required feature.

Identifying and fixing defects in the software.

Two developers working together on the same code.

Creating early models of the software to test concepts and ideas.

Revising code to improve its structure without changing its behavior.

Implementing and adhering to specific standards and libraries.

The practice of establishing and adhering to standards to ensure consistency, compatibility, and quality in software development.

Implementing and utilising specific tools in the development process.

Using version control systems to manage changes to the codebase.

Examining systems to understand how they work and how they should change.

Defining contractual obligations and agreements.

The practice of securing funding from investors to support the growth and development of a startup.

Managing communication strategies to promote the software and engage with the target audience.

Hiring external resources or companies to handle parts of the project.

Managing the sales strategy to drive software adoption and revenue generation.

Getting formal approval for various project stages.

Managing changes to systems and organisations in a systematic way.

The practice of assigning responsibility and authority to others to carry out specific activities or tasks.

Designing the high-level structure of the software.

Estimating the time and resources needed for tasks.

Logging support issues and tracking their resolution.

The practice of gathering team members to discuss project progress, address issues, and make decisions.

The practice of exerting influence on team members to ensure tasks are completed on time and to a high standard.

Defining the Minimum Viable Product and planning development priorities.

Gathering and documenting the requirements for the software.

Managing relationships and communications with stakeholders.

Defining the scope and objectives of the project.

Writing and running tests for individual units or components of the software.

Testing combined parts of the software to ensure they work together.

Quantitatively evaluating the software against benchmarks along some defined dimension.

Testing to ensure the software performs well under expected workloads.

Testing to ensure new changes do not adversely affect existing functionality.

Ensuring the application is secure by identifying vulnerabilities.

Having a customer representative available onsite for feedback.