to content
  Contact us now

You are here: Have a web application
programmed
> Agile WorkingMethod

Author: (with the help of ChatGPT)  |   Reading time approximately: 4 min  |   last modified: 29.07.2026

Have your website expanded individually – this is how the programming process works

Custom features expand your website exactly where standard solutions are not sufficient. To ensure that implementation is efficient, predictable, and transparent, the programming process follows a clear structure.

There are basically two established ways to implement custom expansions for a website: the classic approach with requirements and specifications documents or the agile approach with a streamlined requirements definition.

Option 1: Programming with Requirements and Specification Documents

This approach makes sense when the requirements for the website enhancement are already clearly defined.

Process of Classic Programming

  1. Request and Preliminary Offer
    You describe the desired feature or enhancement for your website. Based on this, you receive an initial assessment.
  2. Creating the Requirements Document
    All requirements are described fully and in a structured way – from a business perspective.
  3. Specification Document Development
    The technical implementation is defined in concrete terms. The specification document details how the programming will be carried out.
  4. Implementation of the Website Enhancement
    Development takes place exactly according to the specifications – structured, documented, and transparent.
  5. Acceptance of the Programmed Function
    You review the finished enhancement based on the defined requirements.

Advantages of this method

  • Clear definition of deliverables
  • High planning security
  • Reliable project scope

Limitations

  • Changes during implementation are more labor-intensive
  • Less flexibility for new requirements

Option 2: Agile Programming with a Simplified Requirements Document

This option is suitable if the requirements for the website enhancement are not yet fully defined or are intentionally kept flexible.

Process of Agile Implementation

  1. Defining the Goal of the Feature
    Joint clarification: What task should the enhancement fulfill?
  2. Lean Requirements Document
    Focused description of the key requirements without unnecessary detail.
  3. Iterative Programming
    Implementation takes place step-by-step. Results are reviewed regularly and immediately further developed.
  4. Continuous Optimization
    New requirements and insights are immediately incorporated into further development.

Advantages of this method

  • High flexibility
  • Quick adjustments possible
  • Early visible results

Limitations

  • Scope and effort develop dynamically
  • Lower predictability at the start

Which kind of programming suits your project?

The choice depends on how concrete your requirements for the website enhancement are:

Clear requirements → Requirements & Specification Documents
Open or evolving requirements → Agile programming

In many cases, a combination is effective: a structured start, followed by flexible further development.


Costs for custom programming

The effort for custom website enhancements depends heavily on scope of functions, complexity, and integrations.

We explain how programming costs are generally structured on the page “Programming Costs”.


Requirements for software or a website with long-term operation:

  1. Functionality
    The software does what it is supposed to. Technical updates are necessary from time to time and are applied as needed.
  2. User guidance and usability:
    The user understands the processes and can apply them. Modernizations become necessary from time to time and are carried out.
  3. Comprehensibility and traceability:
    Both the client and we as developers can, even after years, understand what was solved how and why. We keep the project lean and understandable. Functions that have become unnecessary over time are removed.

What we do to meet these requirements:

  • Actively and responsibly manage and document projects and customer communications
  • Set milestones and carry out intermediate approvals
  • Plan and process steps with checklists
  • Document the project in a wiki
  • Use a version control system
  • Manage tasks in a ticket system
  • Develop a test version in a development environment parallel to live operations

Mehr zum Thema "Have a web application
programmed":